# [RFC] [Re-proposed] Adopt Code of Conduct

- Thread: https://externals.io/message/90891
- Original archive: https://news-web.php.net/php.internals/90891
- Started by Sharon Levy on 2016-01-24T20:45:58+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · RFCs at https://externals.io/rfc.md · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #90891 — Sharon Levy — 2016-01-24T20:45:58+00:00

URL: https://externals.io/message/90891#90891

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.

---

## #90893 — Andrea Faulds — 2016-01-24T21:22:57+00:00

URL: https://externals.io/message/90891#90893 · In reply to: #90891

Hi Sharon,

Sharon Levy wrote:
> 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?

I'd say that a code of conduct would be for whole community. Its purpose 
is to keep the community a friendly and inviting place. That goal is 
surely one beneficial to everyone.

> 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?

That would be the idea, yes.

> 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?

Well, that would also be a benefit. I don't think these are exclusive 
goals. If PHP isn't inviting, people won't want to contribute.

> 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.

The idea of "taking personal responsibility for their deportment" 
reminds me a little too much of Soviet-era jokes about how the KGB would 
function once communism was achieved.

Mostly-irrelevant musings aside, I don't think that simply asking people 
to be nice, on its own, is necessarily sufficient. At the very least, 
having people tasked with moderation means people get warned if they 
step over the line, rather than them doing it unaware. If you put up 
rules, not everyone will read them, or at least remember them in full.

Thanks.
-- 
Andrea Faulds
https://ajf.me/
