Re: GR proposal: code of conduct

2014-02-12 Thread Chris Knadle
On Wednesday, February 12, 2014 21:39:47 Russ Allbery wrote: > Chris Knadle writes: > > On Wednesday, February 12, 2014 16:27:52 Russ Allbery wrote: > >> Ean Schuessler writes: > >>> I am actually for the CoC. My complaint is that the GR does not > >&g

Re: GR proposal: code of conduct

2014-02-12 Thread Chris Knadle
ntentionally short and simple. The specific process to use concerning consequences as well as the specific consequences are a related but separate matter. For the CoC it's enough to simply say that there are consequences and a hint about what could realistically be done. -- Chris -- Chris Knadle chris.kna...@coredump.us signature.asc Description: This is a digitally signed message part.

Re: [all candidates] Removing or limiting DD rights?

2013-04-03 Thread Chris Knadle
On Wednesday, April 03, 2013 09:40:50, Ian Jackson wrote: > Chris Knadle writes ("Re: [all candidates] Removing or limiting DD rights?"): > > On Tuesday, April 02, 2013 13:53:24, Ian Jackson wrote: > > > The purpose of a bug report is not to help solve t

Re: [all candidates] Removing or limiting DD rights?

2013-04-02 Thread Chris Knadle
On Tuesday, April 02, 2013 20:34:28, Russ Allbery wrote: > Chris Knadle writes: > > Seriously, what I'm trying to do is lower the number of cases which > > cause frustration and which don't get any traction. Between the " > > *close* " problem, the mai

Re: [all candidates] Removing or limiting DD rights?

2013-04-02 Thread Chris Knadle
I'm on the -project list, so no need to CC me directly. (Fine if you do, though.) On Tuesday, April 02, 2013 13:53:24, Ian Jackson wrote: > Chris Knadle writes ("Re: [all candidates] Removing or limiting DD rights?"): > > The #1 kind of bug reports that become proble

Re: [all candidates] Removing or limiting DD rights?

2013-03-31 Thread Chris Knadle
On Thursday, March 28, 2013 18:35:40, Don Armstrong wrote: > On Thu, 28 Mar 2013, Chris Knadle wrote: > > As a bug reporter dealing with a misbehaving maintainer, this is > > > > what I would want: > > 1. A clear place to report the misbehavior > > ow...@

Re: [all candidates] Removing or limiting DD rights?

2013-03-29 Thread Chris Knadle
n-candidate responses, please follow up there. Okay, I've just signed up for [debian-project]. I'm in a bit of a rush at the moment, but will respond tomorrow. -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-vote-requ...@lists.debian.org with a su

Re: [all candidates] Removing or limiting DD rights?

2013-03-29 Thread Chris Knadle
On Friday, March 29, 2013 13:46:56, Stefano Zacchiroli wrote: > On Fri, Mar 29, 2013 at 01:35:59PM -0400, Chris Knadle wrote: > > As such, there's an issue of "public perception" that may need > > consideration. > > […] > > > I simultaneously ackn

Re: [all candidates] Removing or limiting DD rights?

2013-03-29 Thread Chris Knadle
On Friday, March 29, 2013 09:41:23, Stefano Zacchiroli wrote: > On Thu, Mar 28, 2013 at 05:37:18PM -0400, Chris Knadle wrote: > > Technically the DAM has the ability to act to remove a DD (per Debian > > Constitution 8.1 item 2), but the information I can gather so far seems >

Re: [all candidates] Removing or limiting DD rights?

2013-03-28 Thread Chris Knadle
orted to go up, not steadily down. As a bug reporter dealing with a misbehaving maintainer, this is what I would want: 1. A clear place to report the misbehavior 2. A set of guidelines maintainers should follow 3. A public dialog about the misbehavior with some Debian authority along