User:Kparal/Idea:Fedora Hall of Fame
Currently lots of people participate in the Fedora Project. Some of them devote an incredible amount of their personal time to it. But although they are known amongst people related to their area of interest, some of them might feel lack of urge to push forward and improve over time. We would like to motivate them continuously, increase their satisfaction from their work and reward them. We believe that one of the pieces of this puzzle could be a Hall of Fame, that is further described by this proposal.
Hall of Fame proposal
Hall of Fame should be a collection of ladders that display top Fedora contributors in certain areas over a certain period of time and give them credit. The suggested areas of tracked participation may include (just ideas, not everything must be implememted):
- Fedora Wiki - # of edits, # of new pages created
- Fedora Mailing Lists - # of replies, # of new threads created
- Fedora Forum - # of replies, # of new threads, new ranks achieved
- Red Hat Bugzilla - # of comments, # of new bugs reported, # of bugs triaged, # of bugs fixed
- Fedora Package Maintenance - # of packages owned/maintained, # of new builds, overall activity, # of new updates
- Fedora Source Code - # of commits, activity in Fedora applications
- Fedora Translations - # of translations
- Fedora Package Review - # of reviews done
- Fedora Testing - # of new updates tested, # of installation testing done, # of Test Days test cases done
- Fedora Planet - # of blogposts
These statistics should be probably displayed in the form of ladders and graphs on a separate web page, that would encompass the whole Hall of Fame. This page could be part of Fedora Community website and the UI could be similar to reports present there. Basically it could look similar to the graphs currently available on Fedora Community website, but we would like to have many many more of them and prettier :-)
The statistics should be updated regularly. It doesn't have to be real-time, but at least once a day would serve the purpose well.
We foresee that the "top contributors list" and a link to Hall of Fame would be included in the Fedora Weekly News or other magazines and that could be a big motivator and a reward for some people to be listed there.
Possible future enhancements
- A nice feature would be support for certain time snapshots (e.g. "wiki edits for the end of May") that could be linked from other sources. That way hyperlinks in newsletters/blogpost would link to the same content even after several months.
- Although the first task is to have this working for general metrics (e.g. all wiki edits regardless of user memberships or wiki sections), an optional feature in some later stage of this project could be tailoring the statistics for different teams/audiences. For example QA team would love to restrict the graph of wiki edits only to people with qa group membership, or just to wiki pages with QA: and Test_Results: namespaces.
- Time scope: start of June 2010 - end of August 2010
- plans - folder with project management plans, etc
- ALL: Think out the proposal thoroughly, raise questions and concerns, post them here (use Discussion page)
- jtluka: Sort out with your managers how much time you can spend on this task
- jtluka: Try out EKG and see how it works
- kparal: Consult this idea with Fedora Community authors. Those are probably the same people as standing behind Statistics 2.0 project.
- kparal: Find public machine suitable for development
- kparal: Find out where the documentation (photos, etc) is stored for our past project management training, it wasn't provided to us
- jhutar: Write "Hello World" page for Fedora Community portal, inspect the code standing behind it
- mganisin: Set wiki to watch this page for you and inform you on every change
- mganisin: Find out how hard it is to extract data from different web portals and development tools (as listed in the proposal). Provide some summary which portals are easy to work with and which are not.
- Consult idea for watching fedoraforum with Fedora Forum Community - from a quick search, it looks like they are not using CMS which have some RPC and it looks like there is no such plug-in on the CMS webpages