bugs.python.org, job status, and contributors (aka not core devs)
Question: I noticed a couple issues on b.p.o that were being closed by contributors (not core-devs, not their own issues).
Should non-core-devs be closing issues that do not belong to them?
-- ~Ethan~
Some non-core devs have elevated privileges on the tracker to help with issue triage.
On Mon, Jun 6, 2016, 09:40 Ethan Furman <ethan@stoneleaf.us> wrote:
Question: I noticed a couple issues on b.p.o that were being closed by contributors (not core-devs, not their own issues).
Should non-core-devs be closing issues that do not belong to them?
-- ~Ethan~
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
On Mon, Jun 6, 2016 at 7:41 PM, Ethan Furman <ethan@stoneleaf.us> wrote:
Question: I noticed a couple issues on b.p.o that were being closed by contributors (not core-devs, not their own issues).
Should non-core-devs be closing issues that do not belong to them?
Yes, but they should provide enough information (commit hash, issue number etc.) about their reasons to close those issues.
Also slightly off-topic, but we should be more transparent about giving people triage rights on the tracker. I'm seeing some unknown people (at least they are unknown to me) who assign issues to themselves without knowing what the field is about.
--Berker
On Mon, Jun 6, 2016, 09:40 Ethan Furman <ethan@stoneleaf.us <mailto:ethan@stoneleaf.us>> wrote:
Question: I noticed a couple issues on b.p.o that were being closed by contributors (not core-devs, not their own issues).
Should non-core-devs be closing issues that do not belong to them?
On 6/6/2016 1:17 PM, Brett Cannon wrote:
Some non-core devs have elevated privileges on the tracker to help with issue triage.
I believe that only originators, coredevs, and triagers can close, but not random others. I was a triager before being promoted.
I have wondered whether triagers should have a symbol after their name -- perhaps &.
tjr
On Mon, 06 Jun 2016 20:25:22 +0300, =?UTF-8?Q?Berker_Peksa=C4=9F?= <berker.peksag@gmail.com> wrote:
On Mon, Jun 6, 2016 at 7:41 PM, Ethan Furman <ethan@stoneleaf.us> wrote:
Question: I noticed a couple issues on b.p.o that were being closed by contributors (not core-devs, not their own issues).
Should non-core-devs be closing issues that do not belong to them?
Yes, but they should provide enough information (commit hash, issue number etc.) about their reasons to close those issues.
Right. In general though when one is closing an issue there isn't a commit hash to note unless that has already been noted by the commit bot, in which case it is likely to be a core dev doing the close since they did the commit. An issue number would be cited in the case of a duplicate, yes. There are other reasons to do a close, and those reasons should be stated clearly in an accompanying comment. That goes for core devs as well as triage people, obviously :)
I'm assuming here that you are amplifying that non-committers can close, not that you are saying that there are some who are not commenting on why they are doing the close.
Also slightly off-topic, but we should be more transparent about giving people triage rights on the tracker. I'm seeing some unknown people (at least they are unknown to me) who assign issues to themselves without knowing what the field is about.
Some while back we made the decision to be fairly liberal in handing out tracker privs for triage. If there are people who are not following the devguide with regards to triage, let us know here and we can discuss it and mentor them. Triage privs can only be given out by some core devs, so you can find out who and why by posting here. Well, unless it is someone from long enough ago that we've all forgotten about them :)
We've talked about having a 'triage capable' symbol to go with our core dev and contributer agreement symbols, but no one has implemented it yet.
--David
On 6 June 2016 at 12:00, R. David Murray <rdmurray@bitdance.com> wrote:
On Mon, 06 Jun 2016 20:25:22 +0300, =?UTF-8?Q?Berker_Peksa=C4=9F?= <berker.peksag@gmail.com> wrote:
Also slightly off-topic, but we should be more transparent about giving people triage rights on the tracker. I'm seeing some unknown people (at least they are unknown to me) who assign issues to themselves without knowing what the field is about.
Some while back we made the decision to be fairly liberal in handing out tracker privs for triage. If there are people who are not following the devguide with regards to triage, let us know here and we can discuss it and mentor them. Triage privs can only be given out by some core devs, so you can find out who and why by posting here. Well, unless it is someone from long enough ago that we've all forgotten about them :)
In the early days of the developer log, elevated issue tracker permissions were recorded in addition to CVS commit access: https://docs.python.org/devguide/developers.html
Perhaps it would make sense to start doing that again, including backfilling the list of current triagers? (even if we don't have precise dates)
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Mon, Jun 6, 2016 at 10:00 PM, R. David Murray <rdmurray@bitdance.com> wrote:
We've talked about having a 'triage capable' symbol to go with our core dev and contributer agreement symbols, but no one has implemented it yet.
I'm a complete Roundup newbie but I have attached a patch at http://psf.upfronthosting.co.za/roundup/meta/issue593 :)
--Berker
On 6/12/2016 8:24 PM, Larry Hastings wrote:
On 06/06/2016 10:56 AM, Terry Reedy wrote:
I have wondered whether triagers should have a symbol after their name -- perhaps &.
I smell an assumption of ASCII,
Unconscious, but yes.
when presumably all of Unicode lay open at our feet.
Agree. There is a green snake. Not sure if all the main browsers can display it, but easy enough to check. The bugs maintainers can decide.
tjr
participants (7)
-
Berker Peksağ -
Brett Cannon -
Ethan Furman -
Larry Hastings -
Nick Coghlan -
R. David Murray -
Terry Reedy