Code

Opened 7 years ago

Closed 6 years ago

#6320 closed (fixed)

contributing.txt is not specific enought about Triaging

Reported by: telenieko Owned by: telenieko
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

There are some points missed in the triaging section of contributing.txt, those points can lead to things like:

  • #2415, when a ticket was closed as wontfix.
  • #689, comment 22
  • #399, which even added a discusion.

We have threads asking for clarification also like this one.

So I'm trying to take some bits out of this thread and clarify contributing.txt a bit.

I just opened this ticket so anybody knows I'm working on it! ;)

Attachments (3)

6320.diff (2.9 KB) - added by telenieko 7 years ago.
The third role
djangotickets.png (57.3 KB) - added by telenieko 7 years ago.
not perfect but should give a visual idea of the patch.
6320_remix.diff (2.8 KB) - added by telenieko 6 years ago.
New patch

Download all attachments as: .zip

Change History (9)

Changed 7 years ago by telenieko

The third role

comment:1 Changed 7 years ago by telenieko

  • Has patch set
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

Done it, I took most of the things from django-developers group.

mostly I've created a "third role" making a clear distinction between a Trusted Triager (one officially recognised) and a Community Triager (one that helps out triaging sometimes to keep the tracker clean).

On this new role I added the points in which those should be careful, stating the differences between being a triager with a "proven criteria" and one "still proving criteria".

Hope this helps out volunteers who want to triage bugs.

Changed 7 years ago by telenieko

not perfect but should give a visual idea of the patch.

comment:2 Changed 6 years ago by SmileyChris

  • Triage Stage changed from Unreviewed to Design decision needed

Thanks for the work telenieko - this is a necessary clarification. Perhaps just "community members" rather than "community triagers"

I'd like to get some opinions on this from the core crew, so could you bring this up in django-dev please?

(for example, I'm not sure community members should ever be pushing the triage stage past a design decision)

Changed 6 years ago by telenieko

New patch

comment:3 Changed 6 years ago by telenieko

  • Owner changed from nobody to telenieko
  • Status changed from new to assigned

Brought in some changes recommended by SmileyChris and Russell Keith-Magee, that makes unnecessary the change of djangotickets.png.

Also, discussion has been brought to django-developers in this thread

comment:4 follow-up: Changed 6 years ago by edgarsj

  • Triage Stage changed from Design decision needed to Ready for checkin

Marking ready for checkin as discussed at the end of this django-developers thread.

comment:5 in reply to: ↑ 4 Changed 6 years ago by telenieko

Replying to edgarsj:

Marking ready for checkin as discussed at the end of this django-developers thread.

Nice!!!!!!!
Commiter: NOTE that the attached .png image does not need to be commited, the latest patch made it unnecesary.

comment:6 Changed 6 years ago by russellm

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [7632]) Fixed #6320 -- Clarified a few issues in the contribution docs surrounding the triage process. Thanks to telenieko, Edgars Jekabsons and Marc Fargas for their input.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.