Let's start with a rhetorical question: When you are adding unit tests to a
legacy code base, where do you start?
...
Typically, you start at the extremes and work your way to the core of the
application, refactoring as you need to go.
I think many people agree that a Code of Conduct, in the abstract (not a
particular one!), would be a good thing to have. So why don't we apply the
same methodology with the CoC initiative?
I propose we start with the most extreme elements of the PHP community and
field test a CoC proposal there. If we can improve the quality of
communication and contributions there, then we know it will have a positive
impact on the core.
And my most extreme, I am of course talking about OpenCart[1], arguably the
most toxic open source software project on the Internet.
Please, fellow PHP community members, join me in proposing a Code of
Conduct (i.e. the Contributors' Covenant) to the OpenCart team, explicitly
stating that it applies to Daniel Kerr and James Allsup too.
[1] http://www.openwall.com/lists/oss-security/2016/01/19/16
[2] https://github.com/opencart/opencart/issues
Let's start with a rhetorical question: When you are adding unit
tests to a legacy code base, where do you start?...
Typically, you start at the extremes and work your way to the core of
the application, refactoring as you need to go.I think many people agree that a Code of Conduct, in the abstract
(not a particular one!), would be a good thing to have. So why don't
we apply the same methodology with the CoC initiative?I propose we start with the most extreme elements of the PHP
community and field test a CoC proposal there. If we can improve the
quality of communication and contributions there, then we know it
will have a positive impact on the core.And my most extreme, I am of course talking about OpenCart[1],
arguably the most toxic open source software project on the
Internet.
Please, fellow PHP community members, join me in proposing a Code of
Conduct (i.e. the Contributors' Covenant) to the OpenCart team,
explicitly stating that it applies to Daniel Kerr and James Allsup
too.[1] http://www.openwall.com/lists/oss-security/2016/01/19/16 [2]
https://github.com/opencart/opencart/issues
I would perceive it as toxic, to make such a try there. It would
probably being seen as direct attack against the maintainers, even
without explicitly stating this out.
Analysing the currently (and from you linked) public handling of
problematic cases, such a try is likely to get directly put down.
Followed from even more negative publicity and attracting of trolls and
angry MOBs.
To make such an appeal successful, you need the support of the
maintainers, especially if they are small in number. And you need to
show them, how it is advantage. I think that would work best in a
private mediation. But not everyone is accepting such a private
mediation from everyone, especially from outside their community.
So it has to come from inside their community, from someone they really
trust in a personal way.
I assume its very unlikely, that we can initiate such a process from
here, so a failing is likely.
So we would already fail in the requirements, what would be the
conclusion for the core?
Probably nothing, as we have a very different precondition with a lot
more regular core contributors instead of 2 people doing all the stuff.
Also we have the goal to increase the number of core contributors, that
may not be true for opencart, which we should respect as understanding
community.
Lets go a step further, the main place for the community of opencart,
the forum. Most forums today have an Netiquette or Etiquette somewhere.
Opencart is no exception here, including:
Keep all commentary civil, and be courteous at all times.
Constructive criticism is welcome, but insults directed towards other
users or the site admins will not be tolerated. Coarse/insulting
language will not be tolerated.
But first it would be needed a prove, that the environment there is also
toxic.