Thank you for the votes and discussion so far.
Follow ups:
- Restrict assignment before a ticket is accepted · Issue #316 · django/code.djangoproject.com · GitHub
- Restrict the total number of "Accepted" Trac tickets allowed to be assigned to a contributor · Issue #317 · django/code.djangoproject.com · GitHub (note that the concern is included in the issue description and exact numbers and limits can be tweaked, we were all in favor of imposing some limit)
- The low severity has been implemented and is live. New tickets now default with severity “Low”.
Regarding #4, I think we are in favor providing we find the appropriate name. I am going to suggest: “Deep dive required”. We could document what we use this flag for here: Triaging tickets | Django documentation | Django
Deep dive required
This flag is used for tickets that require extensive investigation, analysis, and testing. A DEP may be needed before work can proceed. These tickets are unsuitable as a first contribution unless the contributor already has expertise in the relevant area.
We could also be explicit that throwing an LLM at this ticket and asking the community to review would be considered a breach of the code of conduct: Django Code of Conduct | Django and you will be reported.
Consensus around number 5 is not strong. I am happy to put this on ice for now. I may re-propose this at a later date incorporating feedback and providing examples and frequency of bad actors.