Blueprint work earns much more karma than other activity

Bug #315469 reported by Roman Friesen on 2009-01-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

In the "quit-applet-plus" project I have 38957 points for Specification Tracking Karma (23 blueprints) and 1492 points for the Bazaar Branches Karma (115 commits). I could imagine that creation of blueprints may produce more karma than the code commits, but in every case the difference is too big here...

The problem could be, that blueprints changing (after creation) produces to much karma.

P.S. I have 85 points for Translations, but I think, it's OK, in comparison to the Bazaar Branches karma points (1492).

See also the related question:

Ursula Junque (ursinha) wrote :

I'm marking it as invalid, since it's the expected behavior as explained on, "How Launchpad calculates the score for each type of work".

Changed in launchpad:
status: New → Invalid
Roman Friesen (krokosjablik) wrote :

The quote from
> "Karma is Launchpad's way of showing how active a person is in Launchpad."

I was by programming (commits) at least as active as when writing the documentation (blueprints). The difference between both karmas is still too big...

You have probably right, the Launchpad calculates karma as expected, but the current logic doesn't represent the quote above...

Matthew Paul Thomas (mpt) wrote :

Having behavior described on a help page does not excuse it from being wrong.

Matthew Revell (matthew.revell) wrote :

Sure. I didn't say it did :) I just wanted to document the situation as it stands.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions