On 07/20/2016 06:19 AM, Johan S via oi-dev wrote:
On Wed, 20 Jul 2016 01:44:00 +0200
Nikola M <minik...@gmail.com> wrote:

On 07/19/16 02:26 PM, Aurélien Larcher wrote:


    As part of a larger effort at providing a more formal governance
    structure for the OpenIndiana project, I’d like to announce on the
    behalf of OI developers the adoption of an OpenIndiana Code of
    Conduct. The draft text for this new document can be found
    at http://www.openindiana.org/community/code-of-conduct/.


Looks reasonable to me.

That's because you are not seeing enough in the future.

and the future will certainly go this way rule #3137 violates rule #2169
you're right , i fork from now...
unsubscribe



Hello Johan,

I'm sorry you view the adoption of a Code of Conduct as a slippery slope leading to an endless set of rules and regulations. And to anyone else feeling this way you have my sympathies as well.

In my view I see the project is at a turning point and as Adam recently pointed out, the current situation is untenable and problematic.

On many occasions I have heard people vocalize their frustrations regarding the inability to get anything done in a public venue. As a relatively new member of this community I have often felt that way myself.

I have also seen individual community members try to single handily address problematic behaviors by pointing them out in the hope that by doing so, the problematic behaviors would cease.

Each time this occurred, the individual community members gave up in frustration. In fact, in a most recent incident, the individual community member characterized the remedial exercise as 'rolling a large rock up the hill".

As a community, we shouldn't expect each individual community member to have to fight this battle themselves, rather I think it should be done collectively. The adoption of a sensible CoC helps to achieve that.

I am sure what everyone wants here is a supportive and inclusive work environment where collectively we can do some really neat things.

But if the work environment is hostile or dysfunctional, and we as a community ignore the issues by allowing the behavioral problems to continue without any collective action, then it seems to me we are effectively telling the community:

"Yes, we have some problems, just try ignore them the best you can and not become discouraged and leave as a result of them".

Frankly I get enough of that in my day job. And I don't feel I should have to deal with it while volunteering for an open source project.

In light of this, it's pretty clear we're not going to please everyone no matter what direction the project takes. The community may loose members either way.

Therefore, I see the adoption of a code of conduct as a sensible step towards sound project governance, which will in the end produce a well managed and supportive work environment for all community members.

I do hope you'll reconsider and remain with the community.

Best Regards,

Michael

_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev

Reply via email to