Chris Bannister writes ("Re: [Debconf-discuss] Code of Conduct violations
handling process"):
> On Thu, Sep 04, 2014 at 01:13:23PM +0100, Ian Jackson wrote:
> > If a CoC complaint is made, and the decisionmakers consider the
> > complaint unjustified, the complai
also sprach Ian Jackson [2014-09-04 05:15
-0700]:
> I am not angry or upset with the performance of Debconf organisers
> or the antiharassment team. Rather, I feel that they were not
> provided with the tools and support required to do their job.
Right, and we are also new to this. We should no
On Thu, Sep 04, 2014 at 01:13:23PM +0100, Ian Jackson wrote:
>
> If a CoC complaint is made, and the decisionmakers consider the
> complaint unjustified, the complaint should not be referred elsewhere
> or escalated. Instead, the decision (complaint considered not
> justified, no action will be t
martin f krafft writes ("Re: [Debconf-discuss] Code of Conduct violations
handling process"):
> also sprach Patty Langasek [2014-09-03 16:57 -0700]:
> > The way this particular Code of Conduct Violation Complaint was
> > handled was entirely my fault.
>
> I do
Steve Langasek writes ("Re: [Debconf-discuss] Code of Conduct violations
handling process"):
> In the particular incident prompting this thread, [...]
I started writing a response to this. But I found that my response,
no matter how carefully phrased, read like an attack on the peo
On Thu, Sep 4, 2014 at 12:20 AM, Steve Langasek wrote:
> It's also possible that, as a matter of course, we should ensure that the
> antiharassment team responds timely in writing to all complaints, even if
> there is an out-of-band follow-up.
Following up in the same media used for a complaint i
also sprach Patty Langasek [2014-09-03 16:57 -0700]:
> The way this particular Code of Conduct Violation Complaint was
> handled was entirely my fault.
I don't think there is any point in thinking about fault here. Go
ahead and disagree with me, but the more important thing for me is
that we lear
On 9/4/14, Russ Allbery wrote:
> Zenaan Harkness writes:
>
>> More facts trickle out. Thank you for stepping up to the plate.
>
>> Any chance someone could crush an egg shell already and just post a link
>> to the brouhaha? Or summarise the events?
>
>> Are we that timid, that dominated by the al
Zenaan Harkness writes:
> More facts trickle out. Thank you for stepping up to the plate.
> Any chance someone could crush an egg shell already and just post a link
> to the brouhaha? Or summarise the events?
> Are we that timid, that dominated by the almighty COC, that facts are no
> longer po
On 9/4/14, Patty Langasek wrote:
> On Wed, Sep 03, 2014 at 12:29:36PM +0100, Ian Jackson wrote:
>> I think more guidance for the teams involved would be helpful. The
>> Debconf and Debian CoC statements are too difficult to amend. The DC
>> and Debian teams should develop a process document whic
On Wed, Sep 03, 2014 at 12:29:36PM +0100, Ian Jackson wrote:
> I think more guidance for the teams involved would be helpful. The
> Debconf and Debian CoC statements are too difficult to amend. The DC
> and Debian teams should develop a process document which those
> responsible would use to guid
On Wed, Sep 03 2014, Steve Langasek wrote:
> The stated purpose of the CoC is to ensure that our conference is a safe
> space for all members of the Debian community. In what way would a change
> in approach to dealing with a violation after the fact, where the offender
> is no longer at the con
On Wed, Sep 03, 2014 at 12:29:36PM +0100, Ian Jackson wrote:
> I think more guidance for the teams involved would be helpful. The
> Debconf and Debian CoC statements are too difficult to amend. The DC
> and Debian teams should develop a process document which those
> responsible would use to guid
13 matches
Mail list logo
