After reviewing the proposed CoC, I wonder if its good intent might
boom-a-rang and have an opposite, chilling effect. I would respectfully
suggest re-thinking the notion of a CoC for the PHP project. Some questions
to consider:
1. Who is the CoC for, i.e. who should be its beneficiaries? Users, core
contributors and maintainers? All of the above?
2. What should a CoC seek? Is it the elevation of PHP culture so that
whether on the internals list or another forum there is less vulgarity and
crudity and more respect? Or, is the purpose of the CoC really a device to
control perceptions, i.e. protect the image of the PHP project and its
citizens?
If a CoC were to use language such as "guidelines" rather than the anonymous
authoritative language contained in the current proposal, I think it would
be more beneficial for encouraging productive discussions .
We can have a more welcoming community and one in which people can feel free
to share their technical thoughts even if they are far beyound the perimeter
of the box if we emphasize the importance of each person taking personal
responsibility for their deportment rather than attempting to dictate
behavior.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
