Proposed changes to Trac to address problematic contribution patterns - please vote

Almost! I mentioned my concerns with the “easy pickings” flag being useless, and repeated my proposal about a flag for “mentoring opportunity” instead. A relative beginner could be involved in tickets marked as such, as long as a mentor was in the loop early enough and had the opportunity to scaffold any prerequisite tickets. When self-assigning a “mentoring opportunity” ticket, someone monitoring Trac activity (me) could ask, “who is your mentor?” and deassign if not answered.

The idea being that for these tickets a relative beginner is welcome but should not present a finished product at the start. I think I like that better than a straight “complexity indicator”, but we didn’t evaluate this much nuance on the call.

This was the intent, I think – naming is hard!

In spirit I agree – historically open triage has been a huge benefit for Django, and honestly I don’t think I would have become involved in the community otherwise.

I’d prefer to see a more granular anti-poaching policy, like “don’t accept a ticket and set yourself to the owner immediately” where the “waiting period” could scale with the number of commits. Someone with 0 commits needs to wait six weeks before poaching a ticket they accepted themselves (“insincere triage”) etc. Someone with 1 commit waits two; 2 commits, no waiting period etc.

If we have trouble with too many “LGTM” reviews setting Ready for Checkin let’s just re-evaluate when that happens.

My votes:
1 - Restrict assignment before a ticket is accepted. +1
2 - Limit contributors to 3 open, accepted tickets assigned to them at once. +1
3 - Add a “Low” severity level. + 1
4 - Add an “experienced contributor required” flag. +1 with caveats, naming problem
5 - Restrict changes to the “Triage Stage” to Triage and Review team members. -1 as described, +1 if we do a more targeted no-poaching policy

I disagree that there’s nothing they can do – they can get a colleague to review their work and mark it ready for checkin, which floats to the top of the merger’s priority list (just below release blockers & security). They can arrange a review swap with another contributor, which we explicitly suggest on the forum threads announcing upcoming feature freezes. If you have 3 tickets “stuck” I don’t think it helps anyone to have 13 tickets “stuck”.

2 Likes