Adding a code of conduct for contributors

[gvwilson]

This PR adds a code of conduct for contributors taken from taken from https://github.com/Bantik/contributor_covenant.

[rgaiacs]

+1.

[jiffyclub]

Nice, should have thought of this when I added it to my projects. :100:

[wking]

On Fri, Jul 04, 2014 at 06:54:23PM -0700, Greg Wilson wrote:

• Adding a code of conduct for contributors taken from https://github.com/Bantik/contributor_covenant.

Sounds reasonable. Perhaps we need to mention the license in the file though though, since this is under the MIT license 1, but we only license software under the MIT 2. Metadata like this doesn't fall clearly under either “Instructional Material” or “Software”. Perhaps a better solution would be to add a catch-all section in our license to handle stuff like this, or to list these special-case files separately in our LICENSE.md?

[gvwilson]

PR updated - please let me know what you think.

[jiffyclub]

@gvwilson I don't see a new commit. Need to push?

[gvwilson]

D'oh.

[jiffyclub]

:+1:

[wking]

On Mon, Jul 07, 2014 at 02:27:09PM -0700, Greg Wilson wrote:

PR updated - please let me know what you think.

The MIT license says:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

So I think you need to include the MIT text with “Copyright (c) 2014 Coraline Ada Ehmke” somewhere in the bc repo. Perhaps just quoting it in LICENSE.md?

Our code of conduct come's from Bantik's contributor covenant repository and is made available under the same MIT License as our software:

The MIT License (MIT)

Copyright (c) 2014 Coraline Ada Ehmke

Permission is hereby granted, …

[wking]

On Tue, Jul 08, 2014 at 10:07:42AM -0700, W. Trevor King wrote:

Perhaps just quoting it in LICENSE.md?

Alternatively, we could follow AngularJS and

• Mirror Bantik's repository into the swcarpentry namespace 1.
• Reference the code-of-conduct from our other repositories 2.

That avoids copy-pasting across repositories, which is nice because:

• It preserves the version control history of the referenced material.
• It doesn't complicate the licensing of our material.
• It makes merging subsequent upstream updates to the referenced material easy.

I doubt we need legal weight here, but if you want to get really serious, it might be best to link to a particular release hash when referencing. For example 3.