Morning Derick,
I know you're asking about another document right now, but I still find
the language of the CoC jarring.
This: "Coercing other members to vote for a particular option on an
RFC, or to change or withdraw an RFC".
That's too vague: https://twitter.com/krakjoe/status/685368852268593152
There is surely nothing wrong with that tweet, but it seems to violate
the CoC in current form. Others have done the same kind of thing for past
RFC's.
Once again, I want to bring attention to this paragraph:
"Project maintainers have the right and responsibility to remove, edit,
or reject comments, commits, code, wiki edits, issues, and other
contributions that are not aligned to this Code of Conduct, or to ban
temporarily or permanently any contributor for other behaviours that they
deem threatening, offensive, or harmful."
That would also seem obviously too vague. It doesn't make sense to try
to limit offence, elsewhere in these documents you try to espouse the
attitude that people will disagree, and "so what". I think it better to
stick with that line of reasoning, rather than giving people the idea that
simply being offended is a thing anyone else should care about.
In addition the word harmful is missing context, and should either be
clarified or removed, with offence.
All the rest of it is good, I think ...
Cheers
Joe
On Tue, Feb 9, 2016 at 12:33 PM, Derick Rethans <der...@php.net> wrote:
> Hello!
>
> Things have quieted down around the Code of Conduct and Contributor
> Guidelines process, but I have not been sitting still. In the last week,
> the following things happened:
>
> - I had a call with the Drupal Community Working Group - as suggested by
> Larry Garfield. Stanislav was on the call as well.
>
> Take aways:
>
> - Texts should be void from ambiguity.
>
> - Although their CWG dealt with plenty of cases, no punitive action
> has occured as parties would often step back themselves. In most
> cases, a gently reminder was all that was necessary.
>
> - We should be reluctant to limit the scope of the Code of Conduct and
> Contributor Guidelines.
>
> - A Code of Conduct without *any* 'teeth' would not be beneficial.
>
> - We should start with suggesting/nominating people for the Mediation
> Team *before* deciding on the procedures and guidelines that
> they should mediate around. The underlaying reason is that if the
> team is known upfront, there ought to be more understanding for the
> general developer community. Or in other words, there should be no
> reason that "I would only put my friends on it".
>
> I do however have a few people in mind that I will reach out to
> privately, to see whether they are interested. If you have any
> suggestions for people that you consider reliable, considerate, and
> empathic, please reach out to them yourself, or let me know and I
> will.
>
> - The RFC text has seen a few updates as well.
>
> - @jessamynwest improved some of the text for "encouraged behaviour"
>
> https://github.com/derickr/php-community-health/commit/134670974b000483c2a179a02fc05a6d2de85d97
> - @hnrysmth imported some new phrases from the Contributor Covenant
> 1.4 over
>
> https://github.com/derickr/php-community-health/commit/8ca9fe70538b036a938acbafa5f5f27f91228602
> - @connerbw added a more general blurb about PHP and the commitment of
> the PHP team to be inclusive
>
> https://github.com/derickr/php-community-health/commit/e6c33f4b81975f2b2f27919e37c585322f829a1c
> - I combined the three bits of text around mailinglist posting
> guidelines into the Contributor Guidelines
>
> https://github.com/derickr/php-community-health/commit/7c55d1dd407524cdab593b885e6b3101bf590769
>
> I feel that the "Contributor Guidelines" are now in a reasonable shape
> to do a quick poll to gauge acceptability. As this is not a formal RFC
> vote, it's simply done through an online poll:
> http://twtpoll.com/y6hs4ndsfiki485
>
> Voting is non-binding, and will end at Friday February 12th, at noon
> UTC.
>
> Feel free to reply here with suggestions, comments, etc.
>
> cheers,
> Derick
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
