Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Latest commit

 

History

History
101 lines (72 loc) · 3.33 KB

CONTRIBUTING.md

File metadata and controls

101 lines (72 loc) · 3.33 KB

Contributing

✨ Hi! ✨ Welcome to the Node Inclusivity Working Group. We're excited that you'd like to contribute :)

First Steps

  1. Read our charter

Think of it like a statement of purpose. Our charter gives a top-level view of what we'd like to accomplish with this WG.

  1. Read the latest meeting notes

Every 2 weeks, the WG members get together to discuss current issues and PRs, goals, and other related news. This is a great way to figure out what's happening at the moment.

  1. Read our docs

We have an interesting history, some rules around filing issues, and other ideas. You can find all this info in the /docs directory.

Getting Involved

This WG focuses on 2 types of deliverables:

  • Policies
  • Programs

Policies

Policies that we have created live in the /policies directory. We also consider our Code of Conduct a policy :)

If you wish to file an issue to change a policy for this WG, change a policy in Node.js generally, or propose a new policy, please read this document.

Programs

Programs that we run and support are documented in /programs directory.

You can check out proposed programs using the program label.

We are currently working on documentation for the process of proposing programs. For more information see issue/91.

Discussions

We try to keep as much discussion as possible in public to maximize transparency and community participation. Most of our discussions occur in Slack or GitHub issues. Participating in Slack discussions requires joining the node-inclusivity Slack team. To do so, please use the Node.js Inclusivity Slack Inviter.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

  • (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

  • (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

  • (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

  • (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

License

Copyright Node.js Inclusivity Contributors SPDX-License-Identifier: MIT