Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

2016-06-06 Thread R. David Murray
On Mon, 06 Jun 2016 20:25:22 +0300, =?UTF-8?Q?Berker_Peksa=C4=9F?= wrote: > On Mon, Jun 6, 2016 at 7:41 PM, Ethan Furman wrote: > > Question: I noticed a couple issues on b.p.o that were being closed by > > contributors (not core-devs, not their own

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

2016-06-06 Thread Terry Reedy
> On Mon, Jun 6, 2016, 09:40 Ethan Furman > 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

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

2016-06-06 Thread Ethan Furman
On 06/06/2016 10:17 AM, Brett Cannon wrote: Some non-core devs have elevated privileges on the tracker to help with issue triage. So if they can, they've been granted the privilege? Cool. -- ~Ethan~ ___ python-committers mailing list

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

2016-06-06 Thread Berker Peksağ
On Mon, Jun 6, 2016 at 7:41 PM, Ethan Furman 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

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

2016-06-06 Thread Brett Cannon
Some non-core devs have elevated privileges on the tracker to help with issue triage. On Mon, Jun 6, 2016, 09:40 Ethan Furman 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

[python-committers] bugs.python.org, job status, and contributors (aka not core devs)

2016-06-06 Thread Ethan Furman
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