Opened 17 years ago

Closed 16 years ago

#6320 closed (fixed)

contributing.txt is not specific enought about Triaging

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

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 Marc Fargas 17 years ago.
The third role
djangotickets.png​ (57.3 KB ) - added by Marc Fargas 17 years ago.
not perfect but should give a visual idea of the patch.
6320_remix.diff​ (2.8 KB ) - added by Marc Fargas 17 years ago.
New patch

Download all attachments as: .zip

Change History (9)

by Marc Fargas, 17 years ago

Attachment: 6320.diff​ added

The third role

comment:1 by Marc Fargas, 17 years ago

Has patch: set

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.

by Marc Fargas, 17 years ago

Attachment: djangotickets.png​ added

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

comment:2 by Chris Beaven, 17 years ago

Triage Stage: Unreviewed → 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)

by Marc Fargas, 17 years ago

Attachment: 6320_remix.diff​ added

New patch

comment:3 by Marc Fargas, 17 years ago

Owner: changed from nobody to Marc Fargas
Status: new → 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 by edgarsj, 16 years ago

Triage Stage: Design decision needed → Ready for checkin

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

in reply to:  4 comment:5 by Marc Fargas, 16 years ago

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 by Russell Keith-Magee, 16 years ago

Resolution: → fixed
Status: assigned → 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.

Note: See TracTickets for help on using tickets.
Back to Top