The idea for this was presented at Wikimania where it received a very positive reception. Most of what I was going to say about it has already been covered by Frances, so I'll just add that I support it as well.
On Fri, Aug 7, 2015 at 10:01 AM, Oliver Keyes <[email protected]> wrote: > Excellent! I'm a strong supporter too, although I think it should be > (as you say) very explicit about the consequences, the processes and > the types of behaviour that are inappropriate - I'd previously added > some commentary on the talk page that pointed to a particularly > detailed CoC I like (it's the jQuery one; gnarf drafts good stuff). > > Thanks again to Matt and Frances and everyone else for kicking this > off; this is something we desperately need. > > (Kudos specifically for handling Tim L's comment so nicely) > > On 7 August 2015 at 12:57, Frances Hocutt <[email protected]> wrote: > > I was also at the Wikimania session where we worked on this draft. I > > strongly support this effort. Best practices for codes of conduct include > > clearly defined consequences for breaches, as well as named behaviors > that > > are unacceptable (as not everyone shares the same "common sense", and > people > > interested in behaving badly tend to rules-lawyer as well). Our > Phabricator > > etiquette is lacking both of these, and it does not cover the rest of our > > technical spaces. An effective code of conduct has been shown to be > > effective at bringing people from underrepresented groups--and their > > contributions!--to events and projects. Screening technical contributors > by > > their willingness to take a risk of poor treatment is a terrible idea if > we > > want to get as many good contributions as we can. > > > > -Frances > > > > On Fri, Aug 7, 2015 at 8:43 AM, Oliver Keyes <[email protected]> > wrote: > >> > >> Thank you for drafting this up, Matt. Who's "we" here? > >> > >> On 6 August 2015 at 20:19, Matthew Flaschen <[email protected]> > >> wrote: > >> > On 08/06/2015 08:17 PM, Matthew Flaschen wrote: > >> >> > >> >> We're in the process of developing a code of conduct for technical > >> >> spaces. This will be binding, and apply to all Wikimedia-related > >> >> technical spaces (including but not limited to MediaWiki.org, > >> >> Phabricator, Gerrit, technical IRC channels, and Etherpad). > >> > > >> > > >> > I forgot to mention (but this is in the draft), it also applies to > >> > physical > >> > spaces, including but not limited to hackathons. > >> > > >> > > >> > Matt Flaschen > >> > > >> > > >> > _______________________________________________ > >> > Engineering mailing list > >> > [email protected] > >> > https://lists.wikimedia.org/mailman/listinfo/engineering > >> > >> > >> > >> -- > >> Oliver Keyes > >> Count Logula > >> Wikimedia Foundation > >> > >> _______________________________________________ > >> Engineering mailing list > >> [email protected] > >> https://lists.wikimedia.org/mailman/listinfo/engineering > > > > > > > > -- > Oliver Keyes > Count Logula > Wikimedia Foundation > > _______________________________________________ > Engineering mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/engineering > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
