Hi David, Thanks for taking the time to write this up.
Aside from some small concerns, for example around auto-closing tickets, which others have already voiced, I just wanted to say that I'm enthusiastic about this outline. In particular, I'm enthusiastic about making it clearer what tasks are available for new contributors, triagers, and committers. I think this will have a big impact on getting and retaining contributors. > 'easy' of course has to be set manually. The system for listing easy > issues should list the issues only when there is an action that someone > could take on the issue (clarify issue, write patch, review patch). > (NB: it might be possible to come up with a better name for this tag.) Some folks get discouraged by "easy" tickets not seeming that easy. A common alternative tag is "bitesized". Straying off topic to talk about workflow documentation: The easy tag is often not set consistently by projects (or it's forgotten until a dash to comb through tickets before sprints to add it). Making the easy tag a triage checklist item could help with that. I think new contributors would also appreciate the clarity of a patch submission checklist. I am in general a big fan of checklists. :) I also volunteer myself to help update the devguide as the workflow gets updated. -Jessica _______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
