From: | Ian Jackson <ijackson(at)chiark(dot)greenend(dot)org(dot)uk> |
---|---|
To: | Bill Allombert <Bill(dot)Allombert(at)math(dot)u-bordeaux1(dot)fr> |
Cc: | spi-general(at)lists(dot)spi-inc(dot)org |
Subject: | Re: Code of Conduct at events |
Date: | 2010-11-11 13:37:41 |
Message-ID: | 19675.61861.582183.798438@chiark.greenend.org.uk |
Views: | Raw Message | Whole Thread | Download mbox |
Thread: | |
Lists: | spi-general |
Bill Allombert writes ("Re: Code of Conduct at events"):
> What happened was the opposite: two developpers manhandled a third
> one. The third one get expelled from Debconf. The two did not get
> real sanction beyond being sermoned. But of course the public memory
> of the event is different.
That's unfortunate, if true. I wasn't there so I can't comment.
> This is the problem with your proposal: your proposal is more about
> defining a set of rules that events organizers have to follow than
> rules that participants have to follow.
It's not about "rules that organisers have to follow". When an event
organiser writes "this is our policy about XYZ" in the README, that
means that they are /choosing/ to set out these rules and /promising/
to follow them.
> But how the organizers will be held accountable ? What information
> will be used to make the decisions ?
In the usual ways that project organisers are held accountable.
(Or, are not, in some contexts.)
Ian.
From | Date | Subject | |
---|---|---|---|
Next Message | Barak A. Pearlmutter | 2010-11-11 13:51:56 | Re: Code of Conduct at events |
Previous Message | Ian Jackson | 2010-11-11 13:35:10 | Re: Code of Conduct at events |