ironprogrammer
commented
10 months ago Thank you for starting this discussion, @ankitguptaindia 🙌🏻 I agree that the current process imposes undue responsibility on team reps, where contributions can be easily overlooked.
Badge Requests
With regards to requesting a badge, I recently learned that there is already a self-request team association form on wp.org for the Test Contributor badge. I found this while researching how the Training Team handles badge assignment (and feel we can learn a lot from how they've improved on contributor recognition for their team).
Perhaps this form could be utilized instead, though it may first require some follow-up in #meta to confirm the intended workflow and to have some additional admins assigned to distribute the work (it appears only Tonya is an admin today). Using this tool would remove dependence on a separate system/form.
Qualification Criteria
Regarding the test criteria, I've started drafting a PR to address https://github.com/WordPress/test-handbook/issues/5, but here are the items I've got so far:
- Submit a test report for testing instructions, issue reproduction, or patch testing.
- Submit unit or e2e tests that get merged.
- Contribute toward a Test handbook PR that gets merged.
- Participate in ZIP package builds or default theme tests during a
#core<release-party>. - Wrangle at a Contributor Day (table lead, technical support, onboarding).
These criteria and the request process could be included on the proposed handbook page (#5).
Badge Request Response Time
IMHO, confirming and processing requests every 2 to 4 weeks seems prompt enough for recognition, yet gives some leeway to team reps to account for holidays and time off (life happens). The Training Team does a monthly review, which still seems fair, and perhaps some consistency between teams would be preferable.
ankitguptaindia
Test Contribution Badge Process:
Information Source from Brian: Link to Slack Conversation
Current Status:
As per the information received from Brian, the Test Team is utilizing the script mentioned here to determine whether a contributor has a badge. The script proves to be very helpful in this regard. However, the challenge lies in creating a list of users to whom badges will be assigned.
We can collect the names of contributors from the following sources:
core-test triage participants conducting repro or patch testing
core events
Manually searching for contributors would not only be time-consuming but also increases the risk of overlooking deserving contributors, especially when searching Test Reports/contributions on each Trac Ticket is challenging.
Proposed Idea:
The idea is to create a system for requesting a badge using a Google sheet. When any contributor contributes to the test team and wishes to earn a badge, they can fill in their details on the sheet. Test Team Reps members will periodically check the sheet (every one or two weeks) and compile a list of contributors based on their contribution history.
We can put the Google sheet link in bookmark items in Slack #core-test and also share a blog post so all interested contributors request to get a badge.
Other Items to Discuss:
Benefits of this approach: