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

Add CONTRIBUTING.md #16

Open
chasenlehara opened this issue Feb 13, 2017 · 2 comments
Open

Add CONTRIBUTING.md #16

chasenlehara opened this issue Feb 13, 2017 · 2 comments

Comments

@chasenlehara
Copy link
Member

chasenlehara commented Feb 13, 2017

Add a CONTRIBUTING.md file to each repo that links to either the DoneJS contribution guide (coming soon!) or a more specific one (e.g. the CanJS contribution guide for a CanJS project).

If there’s already a contribution guide in a repo’s README, then move it to CONTRIBUTING.md and format it similarly to the DoneJS contribution guide.

Otherwise, you can use the DoneJS contribution guide as an outline for what should be included. You can look at related projects to see how their templates were customized and here are some example commits that show updating a project to meet these guidelines:

Of course, if you’re unsure, please reach out to ask questions or open a PR anyway and we’ll fix it in the review process. Thank you for your help!

Below is a list of all the repos. Check off the repo once you’ve submitted a PR for it.

@chasenlehara chasenlehara self-assigned this Feb 13, 2017
@chasenlehara chasenlehara changed the title Add contributing.md documentation Add CONTRIBUTING.md documentation Feb 16, 2017
@chasenlehara chasenlehara changed the title Add CONTRIBUTING.md documentation Add CONTRIBUTING.md Feb 16, 2017
chasenlehara added a commit to bitovi/syn that referenced this issue Feb 22, 2017
@chasenlehara chasenlehara removed their assignment Feb 25, 2017
@leoj3n
Copy link

leoj3n commented Mar 10, 2017

Assuming a lean, mean README like that:


  • README.md
    • (intro and description)
    • Usage
      • Add to your package.json blah blah blah
    • Contributing
      • Link to CONTRIBUTING.md

My original thought was to have a multiple-file structure like that:


  • CHANGELOG.md
    • Contains a link pointing to the GitHub releases tab for the repo.
  • CONTRIBUTING.md
  • HACKING.md
    • Setup
    • Build
    • Test
  • RELEASING.md
  • LICENSE.md

However, after the contributors talked some sense into me, I think I'll shoot for that instead:


  • README.md
    • Contributing
      • Link to the GitHub releases tab for the repo.
  • CONTRIBUTING.md
  • LICENSE.md

To be clear, CONTRIBUTING.md is the file GitHub suggests as "guidelines for contributing" when creating an issue:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants