Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.

3 лет назад
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. # This is an OPEN Open Source Project
  2. ## What?
  3. Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.
  4. ## Rules
  5. There are a few basic ground-rules for contributors:
  6. - No --force pushes or modifying the Git history in any way.
  7. - Non-master branches ought to be used for ongoing work.
  8. - External API changes and significant modifications ought to be subject to an internal pull-request to solicit feedback from other contributors.
  9. - Internal pull-requests to solicit feedback are encouraged for any other non-trivial contribution but left to the discretion of the contributor.
  10. - For significant changes wait a full 24 hours before merging so that active contributors who are distributed throughout the world have a chance to weigh in.
  11. - Contributors should attempt to adhere to the prevailing code-style.
  12. Releases
  13. Declaring formal releases requires peer review.
  14. - A reviewer of a pull request should recommend a new version number (patch, minor or major).
  15. - Once your change is merged feel free to bump the version as recommended by the reviewer.
  16. - A new version number should not be cut without peer review unless done by the project maintainer.
  17. ## Want to contribute?
  18. Even though collaborators may contribute as they see fit, if you are not sure what to do, here's a suggested process:
  19. ## Cutting a new version
  20. - Get your branch merged on master
  21. - Run `npm version major` or `npm version minor` or `npm version patch`
  22. - `git push origin master --tags`
  23. - If you are a project owner, then `npm publish`
  24. ## If you want to have a bug fixed or a feature added:
  25. - Check open issues for what you want.
  26. - If there is an open issue, comment on it, otherwise open an issue describing your bug or feature with use cases.
  27. - Discussion happens on the issue about how to solve your problem.
  28. - You or a core contributor opens a pull request solving the issue with tests and documentation.
  29. - The pull requests gets reviewed and then merged.
  30. - A new release version get's cut.
  31. - (Disclaimer: Your feature might get rejected.)
  32. ### Changes to this arrangement
  33. This is an experiment and feedback is welcome! This document may also be subject to pull-requests or changes by contributors where you believe you have something valuable to add or change.