CONTRIBUTING.md 3.5KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. Contributing to Chart.js
  2. ========================
  3. Contributions to Chart.js are welcome and encouraged, but please have a look through the guidelines in this document before raising an issue, or writing code for the project.
  4. Using issues
  5. ------------
  6. The [issue tracker](https://github.com/chartjs/Chart.js/issues) is the preferred channel for reporting bugs, requesting new features and submitting pull requests.
  7. If you're suggesting a new chart type, please take a look at [writing new chart types](https://github.com/chartjs/Chart.js/blob/master/docs/09-Advanced.md#writing-new-chart-types) in the documentation or consider [creating a plugin](https://github.com/chartjs/Chart.js/blob/master/docs/09-Advanced.md#creating-plugins).
  8. To keep the library lightweight for everyone, it's unlikely we'll add many more chart types to the core of Chart.js, but issues are a good medium to design and spec out how new chart types could work and look.
  9. Please do not use issues for support requests. For help using Chart.js, please take a look at the [`chartjs`](http://stackoverflow.com/questions/tagged/chartjs) tag on Stack Overflow.
  10. Reporting bugs
  11. --------------
  12. Well structured, detailed bug reports are hugely valuable for the project.
  13. Guidlines for reporting bugs:
  14. - Check the issue search to see if it has already been reported
  15. - Isolate the problem to a simple test case
  16. - Please include a demonstration of the bug on a website such as [JS Bin](http://jsbin.com/), [JS Fiddle](http://jsfiddle.net/), or [Codepen](http://codepen.io/pen/). ([Template](http://codepen.io/pen?template=JXVYzq))
  17. Please provide any additional details associated with the bug, if it's browser or screen density specific, or only happens with a certain configuration or data.
  18. Local development
  19. -----------------
  20. Run `npm install` to install all the libraries, then run `gulp dev --test` to build and run tests as you make changes.
  21. Pull requests
  22. -------------
  23. Clear, concise pull requests are excellent at continuing the project's community driven growth. But please review [these guidelines](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) and the guidelines below before starting work on the project.
  24. Be advised that **Chart.js 1.0.2 is in feature-complete status**. Pull requests adding new features to the 1.x branch will be disregarded.
  25. Guidelines:
  26. - Please create an issue first and/or talk with a team member:
  27. - For bugs, we can discuss the fixing approach
  28. - For enhancements, we can discuss if it is within the project scope and avoid duplicate effort
  29. - Please make changes to the files in [`/src`](https://github.com/chartjs/Chart.js/tree/master/src), not `Chart.js` or `Chart.min.js` in the repo root directory, this avoids merge conflicts
  30. - Tabs for indentation, not spaces please
  31. - If adding new functionality, please also update the relevant `.md` file in [`/docs`](https://github.com/chartjs/Chart.js/tree/master/docs)
  32. - Please make your commits in logical sections with clear commit messages
  33. Joining the project
  34. -------------
  35. - Active committers and contributors are invited to introduce yourself and request commit access to this project. Please send an email to hello@nickdownie.com or file an issue.
  36. - We have a very active Slack community that you can join at https://chartjs-slack-automation.herokuapp.com. If you think you can help, we'd love to have you!
  37. License
  38. -------
  39. By contributing your code, you agree to license your contribution under the [MIT license](https://github.com/chartjs/Chart.js/blob/master/LICENSE.md).