> -----Original Message----- > From: Derick Rethans [mailto:der...@php.net] > Sent: Friday, January 08, 2016 7:18 PM > To: Sara Golemon <poll...@php.net> > Cc: Zeev Suraski <z...@zend.com>; Anthony Ferrara > <ircmax...@gmail.com>; internals@lists.php.net > Subject: Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct > > On Thu, 7 Jan 2016, Sara Golemon wrote: > > > On Thu, Jan 7, 2016 at 2:51 PM, Zeev Suraski <z...@zend.com> wrote: > > > > > Having a CoC which is wider in scope and ratified by a voted RFC > > > rather than an email on some mailing list sends a strong message. > > > Having it in our contributor guidelines would also go a long way. > > > > > > I guess here we fundamentally disagree - it seems that sending the > > > message that 'we take this seriously' - by placing strong emphasis > > > on reporting and penalties - is more important to some than agreeing > > > about the values themselves. For me, the values themselves and > > > communicating them properly and prominently are infinitely more > > > important than the policing mechanism, as I believe that stating > > > them clearly would go a very long way and is anything but useless. > > > > > And maybe this RFC is trying to do too much at once. Code diffs > > should be scoped to "one change per diff", and RFCs should as well. > > > > Anthony, would you be amenable to reducing this first RFC to just a > > code of conduct. This is; Define expectations from members of the > > community. > > <snip> > > > Further evolution of that can come in later RFCs. > > I don't think it is a good idea to split things up. The value of a CoC is to show > that you are trying to make a "community" a safe space. It's all fair and dandy > to write down a set of rules/guidelines that a community should abide to, but > IMO, the *real* values is in documenting the procedures to following - initial > report, medition, etc - when something does go against the agreed upon > "rules".
Two things: 1. The key point here is 'etc'. Reporting & mediation is hardly controversial. It's the executive part that's very controversial - and by nature, once you add it, reporting & mediation become complicated too (as they're just step one). If we stop at mediation, which I strongly believe we should at this point, it's probably fine to have a single RFC. 2. If 'etc' involves jotting down the mechanisms and jurisdiction for a CoC team that's not at all a mediation team but the equivalent of a judicial entity, then I strongly believe we must separate the RFCs. If you think the 'etc' part is needed, that's fine - but realize there are other schools of thought that disagree, and passionately so - but at the same time are supportive of adopting a Code of Conduct, the way CoCs are (and as I mentioned before, CoC pretty but by definition don't include penalties or mechanism to deal with violations - emphasis is on the Code itself). Why force people who are supportive of the concept but not the executive parts vote against the RFC, instead of making it possible for them to vote in favor of the CoC adoption (incl. mediation) and against punitive and other executive conflict resolution mechanisms? Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
