search

Build-a-binder / build-a-binder.github.io

Increase the number of people publishing educational, journalistic, and scientific materials that enable readers to read, edit, re-run and re-use that content. Using mybinder.org
https://build-a-binder.github.io/
BSD 3-Clause "New" or "Revised" License
39 stars 20 forks source link

Add code of conduct #24

Closed trallard closed 6 years ago

trallard commented 6 years ago

This PR adds:

Note we might want to add a legend in the main page about the CoC and its enforcement.

trallard commented 6 years ago

Note that I added both the CoC and participation guidelines (see #7 ). Also, I used eLife's innovation sprint CoC as the guide and added the appropriate acknowledgements

betatim commented 6 years ago

I'd be happy with both the guidelines and the CoC.

What should we think about in terms of picking contacts for the COC? I think ideally we'd have both on site, mix of gender, at least one of them isn't involved in the organisation.

We should merge this before #25.

trallard commented 6 years ago

I like the suggestion of the mix of genders. I think since you are going to have facilitators/helpers in the tree sites you should nominate one as an incident handler. In that case, we could just state something like

contact your local incident handler (or a better wording, code of conduct officer?)

and have the contact details (name, email) on each site's page

betatim commented 6 years ago

Maybe we write "At each event there will be two points of contact who are onsite. They will introduce themselves and their contact details at the start of the workshop day."?

gedankenstuecke commented 6 years ago

That sounds like a good solution. Maybe have that plus one person for remote contact before/after the event?

betatim commented 6 years ago

Are you volunteering to be the remote? I also reached out to someone who would also be a good fit.

gedankenstuecke commented 6 years ago

Yep, volunteering for that 👍

betatim commented 6 years ago

Cool beans.

I had asked Abbey in parallel so we now have all the bases covered :)

betatim commented 6 years ago

Let's make that edit, merge this, then double check #25, and get ready to advertise the heck out of this for signups ;)

betatim commented 6 years ago

@trallard do you have time to finish this or could I do it? It would be great if we could get this announced today. (I don't like swooping in :-/)

trallard commented 6 years ago

Hi! I am swamped at the moment, so feel free to go ahead and add the missing edits

betatim commented 6 years ago

Ready to be merged. cc @RaoOfPhysics