Comment 7 for bug 333421

Karma isn't a generic audit trail. If you need an audit trail on branch events, you need to implement one rather than shoe horn one in to a system that wasn't designed for it. You already have all the information in the database to present a recent revisions screen for a person, avoiding the need for them to abuse the karma page for this.

There are currently over 15 million karma events in the database, and the growth rate is exponential because Launchpad gets busier and because the code is updated to generate more karma events. If karma is to scale, we have to summarize and rollup karma events, and remove them entirely when they are no longer relevant. Tying individual karma events to context will make it much harder to decouple and do the refactoring we know has to occur.