Code of Conduct

[Erik Michaels-Ober]

During Luís Ferreira’s talk about Crystal at eurucamp, someone asked a question about the gender diversity of the core team and whether the language has a code of conduct. Unfortunately, there is not much gender diversity among contributors. I think adding a code of conduct to the project would be a good first step toward improving this.

In the Ruby community, Bundler has started prompting users to add a code of conduct to new projects created with the ‘bundle gem‘ command. Here is the template that Bundler uses: https://github.com/bundler/bundler/blob/master/lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt

Could we add something similar for this project? If there are no objections, I will open a pull request.

Erik

[Sergio Gil Pérez de la Manga]

This is a great idea. I was also at the talk and felt Luís' pain at not having an answer about the topic. We sure can make some work in the community about this.

Thanks, Erik, +1

--
You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at http://groups.google.com/group/crystal-lang.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/D71BBDBF-717C-4ED9-8B8B-D366119AEB5F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jmascis]

Bundler doesn't force package authors to actually have a code of conduct, it's a suggestion.

[Sergio Gil Pérez de la Manga]

Hi jmascis,

I think the link Erik posted is for people to read the text, not because he's proposing that all projects done in Crystal are forced to it. He's proposing that Crystal itself adopts it (and I second that), for the development of the language itself. Packages authors would not be forced to adopt it (although setting the example is important IMHO).

On 1 Aug 2015 13:12, "jmascis" <parais...@gmail.com> wrote:

Bundler doesn't force package authors to actually have a code of conduct, it's a suggestion.

--
You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at http://groups.google.com/group/crystal-lang.

To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/ec03ac55-0afd-4ae0-939e-4fdb2d3be715%40googlegroups.com.

[Ary Borenszweig]

We agree with both Erik and Sergio.

Maybe we can do the same as Rust? Have a page of Code of Conduct and add a link to it in Contributing.md?

To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/CAFBTLcg7s%3DnSAu7mpoAsB6RmZE_A3OcApnDV2gT7rSqV14259g%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Ary Borenszweig         Manas Technology Solutions
[ar.phone]                      5258.5240       #ARY(279)
[us.phone]                      312.612.1050    #ARY(279)
[email]                         aboren...@manas.com.ar
[web]                           www.manas.com.ar

[jmascis]

Please, you don't even have a CLA yet AFAIK ( https://en.wikipedia.org/wiki/Contributor_License_Agreement ) . That's what you should worry about at first place, not a code of conduct. If you want to put politics in before code at least do it in a way that will protect the project itself. A code of conduct doesn't.

[Erik Michaels-Ober]

On Sun, Aug 2, 2015 at 8:41 AM, jmascis <parais...@gmail.com> wrote:

Please, you don't even have a CLA yet AFAIK ( https://en.wikipedia.org/wiki/Contributor_License_Agreement ) . That's what you should worry about at first place, not a code of conduct. If you want to put politics in before code at least do it in a way that will protect the project itself. A code of conduct doesn't.

A code of conduct is not about politics. It’s about creating a welcoming environment, where anyone feels safe to contribute to the project without fearing the threat of harassment.

Crystal already has a license[0] to protect itself.

[0]: https://github.com/manastech/crystal/blob/master/LICENSE

[jmascis]

And that's the exact definition of politics. Who got harassed when contributing to Crystal or attending a Crystal event ? nobody.

And a project license for the project has nothing to do with a CLA contributors should be required to sign before contributing to an open source project.

[Erik Michaels-Ober]

> On Aug 2, 2015, at 9:10 AM, jmascis <parais...@gmail.com> wrote:
>
> Who got harassed when contributing to Crystal or attending a Crystal event ? nobody.

How many people considered contributing to this project but decided not to because they feared harassment? Nobody knows!

If you feel strongly that this project should have a CLA, please start a separate thread to discuss that topic.

[Sergio Gil Pérez de la Manga]

I don't see the relation between a COC and a CLA, can't they? Both can be good ideas independently. More specifically, I don't see the absence of a CLA as a reason to oppose the adoption of a COC. If anything, it's a reason to propose a CLA.

Also, the absence of any previous harassment incident is not a valid reason to oppose the adoption of a COC. A COC doesn't (unfortunately) avoid harassment because they're not magic. They signal to current and potential contributors that there will be a specific way to respond to them when/if they happen. The mere absence of previous incidents doesn't signal that.

--

You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at http://groups.google.com/group/crystal-lang.

To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/146bad7d-2eb2-4fae-b893-c007666a455f%40googlegroups.com.

[Kris Leech]

I have proposed some changes to `crystal init` which would include generating a CoC for new lib's / app's.

https://github.com/manastech/crystal/issues/1147

[chc...@gmail.com]

There's a pretty big difference between having a Code of Conduct for the main Crystal repo and developer group, and insisting that all projects that use Crystal have a Code of Conduct. To me, the first one is perfectly fine while the latter is instrusive and shouldn't be done.

I'm also against having a Contributor Liscense Agreement, at least until there is a concrete legal reason to have one. They rise the barrier of entry for open-source projects like Crystal by a lot and scare away new contributors by requiring they sign away the rights to their code, even if that's what they wanted to do.

[Kris Leech]

With `bundle gem <lib_name>` you get the option of adding a CoC. Maybe this is the ultimate goal, but I was thinking small steps. If we added a CoC by default it can just be be deleted if the user doesn't agree with it.

[Erik Michaels-Ober]

On Tue, Aug 11, 2015 at 10:41 AM, Kris Leech <kris....@gmail.com> wrote:

With `bundle gem <lib_name>` you get the option of adding a CoC. Maybe this is the ultimate goal, but I was thinking small steps. If we added a CoC by default it can just be be deleted if the user doesn't agree with it.

I think having the library author explicitly opt-in to the code of conduct is important. A code of conduct that is not enforced by a project's maintainers is potentially worse than that project not having a code of conduct at all. See the discussion at https://github.com/bundler/bundler/pull/3305.

Erik

[Kris Leech]

There are good points on both sides, opt-in versus opt-out. Bundler side on opt-in with good reasoning and after reading the points I'd be inclined to agree.

I will update my proposed pull request to reflect this. Thanks.

 

Erik

[Rishav Sharan]

Some of us are triggered by many other infractions than those listed in bundler CoC.

Us transcopters feel any non-rotory aviation related text should also be censored as they are known triggers.

Sexual imagery is a-ok for us though.

Jokes aside, i like the opt-in idea. If people want it in their project, then they can.