Ticket #93 (closed enhancement: wontfix)

Opened 4 years ago

Last modified 2 years ago

Review options to reward key QA contributors

Reported by: jlaska Owned by: jlaska
Priority: major Milestone: Fedora 14
Component: Wiki Version:
Keywords: retrospective Cc: maxamillion
Blocked By: Blocking:

Description

problem

During Fedora 13, a small amount was available to reward several key QA contributors for their efforts.

analysis

If possible, I'd like to repeat this in Fedora 14.

enhancement recommendation

What's the best way to say thanks?

  1. Request and secure QA budget to reward key contributors
  2. Researching reward options (maxamillion has discussed t-shirt ideas with the design team)

Change History

comment:1 follow-up: ↓ 2 Changed 3 years ago by jlaska

This is a large task ... and I haven't done a great job of actively updating this ticket with progress. The bad news is that I don't have tons of time to develop scripts and automation to support this task. The good news though, is that there are some rough tools to get a basic idea.

My current understanding of the Fedora QA metrics landscape is listed below. Anyone is welcome to grab a topic and expand/correct as needed.

  1. Lists - The EKG project is pretty straight forward. It scrubs the mailing lists and provides information on the list contributors. I'd love to adjust this a bit, first into something I'm more comfortable with (python), and second to adjust the output slightly. Perhaps listing top 15 contributors, then top 15 contributor domains. Finally, maybe also listing top 15 most active threads? Anyone interested in helping?
    • Next steps ... adjust the EKG reporting to break down the contributors according to the criteria above.
  2. For wiki contributions, I blogged about a way to scrub text out of our wiki test matrices. Since then, I've also discovered that mediawiki as an API that can be used to query for additional data. I've written a few sample scripts that grab data from the fedoraproject.org wike (thanks to python-simplemediawiki and the mediawiki API docs).
    • Next steps ... I did find a limitation with some of the API. I'd like to ask mediawiki for a list of recent contributors in different namespaces (e.g. QA:, Test_Results: etc...). Unfortunately, the mediawiki method (see recentchanges) only provides the last 500 wiki changes. We'd need to lobby for increasing the default configuration value to record more than the previous 500, and likely implementing some local EKG-like caching of data for later review.
  3. Bugzilla ... I have some old scripts I use to provide data about how many bugs are reported, VERIFIED, CLOSED. I'd love to extend this to provide another top-15 list of most active components, most active triagers, most active reporters, most duplicated bugs. Some of this information already exists, or is presented by bugzilla. So it may just be a matter of directing folks to the right places.
    • Next steps ... My scripts currently rely on direct database access to bugzilla. That won't fly for folks outside the firewall. Some of what I'm doing will need to be explored using python-bugzilla. Again, anyone interested? I'll be happy to provide the outline of the data I'm grabbing now.
  4. Bodhi ... I have no way to discover+recognize who our most active proventesters are. This needs to be addressed.
    • Next steps ... I understand that the next major release of bodhi will have support for extracting this type of information. Is there a staging instance we can explore the query options against now? Is the upcoming support available for review?
  5. TRAC ... I don't currently keep track of TRAC contributions. I'm aware there is a tool called offtrac that can query a TRAC instance for details.
    • Next steps ... more exploration using offtrac is needed.

comment:2 in reply to: ↑ 1 Changed 3 years ago by kparal

Replying to jlaska:

  1. Lists - The EKG project is pretty straight forward. It scrubs the mailing lists and provides information on the list contributors. I'd love to adjust this a bit, first into something I'm more comfortable with (python), and second to adjust the output slightly. Perhaps listing top 15 contributors, then top 15 contributor domains. Finally, maybe also listing top 15 most active threads? Anyone interested in helping?
    • Next steps ... adjust the EKG reporting to break down the contributors according to the criteria above.

This is closely related to the work jtluka has done as part of our fhof project. His script uses EKG to parse interesting data out of the mailing lists. It is currently available at fedoracommunity git.

comment:3 Changed 2 years ago by adamwill

  • Resolution set to wontfix
  • Status changed from new to closed

This is pretty dead now, as it was specific to the F14 release. The topic of rewarding contributors comes up quite often, but I don't think there's a lot of value in keeping this specific ticket open.

Note: See TracTickets for help on using tickets.