ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-02-20 17:52:50 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add newsfragment description and edit details

Browse Source
This commit is contained in:
May-Lee Sia 2021-04-13 16:01:50 +02:00
parent 8cbff377e3
commit e386a1e705
2 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/ticket-triage.rst
View File

@ -11,16 +11,17 @@ milestones.
Process
-------
- The role of Ticket Triager rotates weekly
- The Triager needs admin status on ``Trac``
- The Triager looks at all the tickets that have been created in the last week
- The role of Ticket Triager rotates regularly-ish, and is assigned ad hoc
- The Triager needs a ``Trac`` account
- The Triager looks at all the tickets that have been created in the last week (or month, etc.)
- They can use a custom query or do this as the week progresses
- BONUS ROUND: Dig up a stale ticket from the past
- Assign each ticket to a milestone on the Roadmap
- The following situations merit discussion:
- A ticket doesn't have an appropriate milestone and we should create one
- A ticket, in vanishingly rare circumstances, should be deleted
- The ticket is spam
- The ticket contains sensitive information and harm will come to one or more people if it continues to be distributed
- A ticket could be assigned to multiple milestones
- There is another question about a ticket
- These tickets will be brought to a weekly meeting (currently Tuesdays) for discussion
- Ticket Triager role is also assigned at this meeting
- These tickets will be brought as necessary to one of our meetings (currently Tuesdays) for discussion

1
newsfragments/3651.minor
View File

@ -0,0 +1 @@
We added documentation detailing the project's ticket triage process