Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: added CODE_OF_CONDUCT.md #4143

Merged
merged 1 commit into from
Apr 7, 2020
Merged

docs: added CODE_OF_CONDUCT.md #4143

merged 1 commit into from
Apr 7, 2020

Conversation

wesleytodd
Copy link
Member

As a member of the Open JS Foundation, we need to add the code of conduct to all project repos. To get started I wanted to at least get it on the main repo, and then if we are good with this we can automate adding it to the rest.

This is part of the project onboarding: openjs-foundation/project-status#15

@wesleytodd wesleytodd requested a review from a team December 31, 2019 23:09
@wesleytodd
Copy link
Member Author

Ok, reading through this I see we are supposed to add an email for reports to go to. What do we want to list there?

@fed135
Copy link

fed135 commented Jan 3, 2020

@wesleytodd I think the contact is the "officer(s)" in charge of enforcing the code of conduct. IE: Who should people report issue to.

For those to be actionable, ideally the officers should have owner/admin role in the org

@mhdawson
Copy link

mhdawson commented Jan 6, 2020

Made a couple of suggestions but generally looks good to me.

@dougwilson
Copy link
Contributor

We could set up a simple email list if we wanted that would simply forward to a list of emails. The expressjs.com domain has the MX records set to 1and1.com which I use for personal hosting, and I could add an email list there for free, but the down side to that is no one else could manage anything about it besides myself. I'm not sure if there is a better solution.

@mhdawson
Copy link

mhdawson commented Jan 7, 2020

Depending on how you want the email to be, getting the foundation to provide something like [email protected] might be an option. Adding @brianwarner as he can comment on what is possible.

@niftylettuce
Copy link

@dougwilson @mhdawson feel free to use my email forwarding service, https://forwardemail.net

@palanik
Copy link

palanik commented Jan 8, 2020

Typo: [coppied directly from here]

Fix: [copied directly from here]

@wesleytodd
Copy link
Member Author

wesleytodd commented Jan 12, 2020

@niftylettuce Thanks, but personally I would prefer the foundation provide the email since it is where all the other infrastructure will live. @brianwarner, if you can get us that email, maybe shared over lastpass like the zoom credentials I can get this updated.

I will wait to do all the rest of the updates once we get the email sorted out.

@dougwilson
Copy link
Contributor

I would love to get all these docs-type PRs landed. Are we any closer to having an email from OpenJS or should we update the wording (for now) to not make reference to needing one and then revisit once there is one?

@mhdawson
Copy link

I pinged @brianwarner on slack today to see if we can get an email this this week.

@brianwarner
Copy link

We can even get it today :-)

How about "[email protected]"?

@dougwilson
Copy link
Contributor

That address is as good as any to me :)

@brianwarner
Copy link

Awesome, thanks @dougwilson!

I wrote a github action that allows projects to manage membership in Groups.io lists via a yml file in https://github.com/openjs-foundation/directory. This provides transparency as to who is on the team, but also allows you to keep it up to date via PRs. I'm going to configure this list that way, so that it's in your hands. (A bonus, it generates a nicely formatted directory for each team)

I'll ping you on Slack to get the list of CoC team members. It would be great to do the same for the express maintainers, as well.

@mhdawson
Copy link

@brianwarner thanks !

@dougwilson
Copy link
Contributor

Thanks @brianwarner ! I just replied with the list of the people and their emails of our active TC members (http://expressjs.com/en/resources/community.html) for the list 👍

@dougwilson
Copy link
Contributor

dougwilson commented Apr 4, 2020

Thanks @LinusU :)

Copy link
Member

@jonchurch jonchurch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit: LGTM

@dougwilson
Copy link
Contributor

Thank you everyone for reviewing it and getting eyes on our official code of conduct 🎉

@dougwilson dougwilson closed this in 67e64ca Apr 7, 2020
@dougwilson dougwilson merged commit 67e64ca into master Apr 7, 2020
@dougwilson dougwilson deleted the code-of-conduct branch April 7, 2020 06:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants