Dear Launchpad: Please stop arbitrarily blowing away my KARAMAAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Stuart Bishop |
Bug Description
affects /products/launchpad
Okay, this is getting slightly annoying. I do an enormous amount of
bug triage in Malone and for that, I receive a lot of karma. I might
not otherwise give two wanks about karma, but since it's there and
I'm human, I can't help but have at least a few brain cells now that
care about karma.
But I just noticed today that I've lost at least ~300 karma points,
for no apparent reason.
I propose the following two options to explore and ask questions
about as alternatives for solving this problem:
1. If you're not going to have the idea of "negative karma" presented
in Launchpad (e.g. from spammy bug comments or whatever), then the
policy should be that my karma can *never* diminish.
OR
2. I can understand that karma may be weighted somewhat by one's more
"recent activity", i.e. if you haven't used Launchpad for six months,
your karma will go down. However, if I'm actively using LP day-to-
day, I *shouldn't* just suddenly see a drop of 300 karma points in
one day. If I'm currently rampantly active in my Launchpad usage, my
karma should *never* drop, and certainly not by 300 points.
Okay, a third one:
3. Keep it simple: never drop karma, no matter how long it's been
since a person last logged in. This is how, for example, http://
www.perlmonks.org works. The work you've contributed is valuable, no
matter whether you did it ten minutes ago or ten months ago.
Cheers,
--
Brad Bollenbach
Attachment: PGP.sig
Type: application/
name=PGP.sig
URL: http://
Changed in launchpad: | |
assignee: | nobody → salgado |
status: | New → Accepted |
Changed in launchpad: | |
status: | New → Accepted |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
The current behaviour is what's in the https:/ /wiki.launchpad .canonical. com/KarmaImplem entation spec, and I don't think it's a problem.
Also, this behaviour is something that was explicitly requested by Mark, so I think you'll need to discuss this change with him.