Skip to content

Contributing

Jesse Lawson edited this page Jul 10, 2018 · 2 revisions

Contributing

What do I need to know to help?

Campfire is a pure JavaScript tool, so if you know JavaScript then you're already 99% of the way there. NodeJS is also used to build the minified version of the main Campfire JavaScript file. If you'd like to checkout some issues you can help with that have been marked as good for first-timers, click here.

If you're not ready to contribute yet, here are some resources to help get you up to speed so that you can:

Git

JavaScript

NodeJS

How do I make a contribution?

Never made an open source contribution before? Wondering how contributions work in the in our project? Here's a quick rundown!

  1. Find an issue that you are interested in addressing or a feature that you would like to add.
  2. Fork the repository associated with the issue to your local GitHub organization. This means that you will have a copy of the repository under your-GitHub-username/campfirejs.
  3. Clone the repository to your local machine using git clone https://github.com/lawsonry/campfirejs.git.
  4. Create a new branch for your fix using git checkout -b branch-name-here. For example, if you are working on something that adds, say, a funny chicken, you might create a new branch like this: git checkout -b funny-chicken.
  5. Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
  6. Use git add . to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.
  7. Use git commit -m "Insert a short message of the changes made here" to store the contents of the index with a descriptive message.
  8. Push the changes to the remote repository using git push origin branch-name-here.
  9. Submit a pull request to the upstream repository.
  10. Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #4352".
  11. In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!
  12. Wait for the pull request to be reviewed by a maintainer.
  13. Make changes to the pull request if the reviewing maintainer recommends them.
  14. Celebrate your success after your pull request is merged!

Where can I go for help?

If you need help, you can email Jesse at jesse at lawsonry dot com or open up a new issue.

What does the Code of Conduct mean for me?

Our Code of Conduct means that you are responsible for treating everyone on the project with respect and courtesy regardless of their identity. If you are the victim of any inappropriate behavior or comments as described in our Code of Conduct, we are here for you and will do our best to remove the problem.