On Wednesday 11 December 2013 14:52:52 Will Stephenson wrote:
On 11/12/13 13:10, Michal Hrusecky wrote:
just a little suggestion, when I was discussing the Karma idea during the GSoC the conclusion we came up with was to not have one overall karma for everything as it is hard to compare/weight organizing presence on event with fixing the bugs. So the think we did was to collect separate karma for marketing, development or documentation. Advantage of that is that you also clearly see, what are people most active/good at.
I believe that this is still a good idea as if we want to make it in use somewhere, being superambasador still doesn't say much about being good developer and vice versa.
I don't see karma as a good metric of being a developer or an event organiser anyway - isn't the idea of karma to give recognition for contributions and thereby motivation to contributors?
As I wrote, there are several elements to the Karma, potential benefits we can try to get (or not). One of them is motivation, another is making work people do more visible (of course these two are closely related). And a third is to direct effort in a certain direction, essentially again combining the two above: if issues in an area are very visible and contributions are so, too, people are more motivated to fix them and thus they DO get fixed. Hopefully. This is rather pie-in-the-sky, of course, on a realistic level we're mostly talking about down to earth changes like showing the number of users of an OBS project or package; showing who maintains it; having a top-ten bug fixers of the last week on the OBS site. Stuff like that. /J
To use the Stackoverflow example, you can earn 100s of points answering questions about openSUSE but it doesn't say anything about your LISP skills, it just shows you are a contributor of useful answers.
True. Part of the thing is you can't judge anything by some rough numbers ;-) But numbers can give you hints about what somebody does, of course. Somebody with 100s of points on StackOverflow is indeed a contributor of useful answers. Having tens of patches accepted and upstreamed into to the Linux kernel probably says something about your hacking skills, so does being a subsystem maintainer. Knowing somebody is maintaining a few core packages and contributing a lot to base system means his/her opinion about adopting systemd or not is more interesting than the opinion of Anditosan (who does great artwork) on the subject. This is meritocracy and do-ocracy, right? Information helps that process, just like an informed public is crucial for a democracy.
Will
-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org