Please take a second to read over this before opening an issue. Providing complete information upfront will help us address any issue (and ship new features!) faster.
We greatly appreciate bug fixes, documentation improvements and new features, however when contributing a new major feature, it is a good idea to first open an issue, to make sure the feature fits with the goal of the project, so we don't waste your or our time.
The Titus project has a Code of Conduct that all contributors are expected to follow.
A perfect bug report would have the following:
- Summary of the issue you are experiencing.
- Details on what versions of node and Titus you have (
node -v). - A simple repeatable test case for us to run. Please try to run through it 2-3 times to ensure it is completely repeatable.
We would like to avoid issues that require a follow-up questions to identify the bug. These follow-ups are difficult to do unless we have a repeatable test case.
All contributions should fit the standard linter, and pass the tests. You can test this by running:
npm run test:all
In addition, make sure to add tests for any new features. You can check the test coverage too when you run the command above.
Make sure to get a :thumbsup:, +1 or LGTM from another collaborator before merging a PR. If you aren't sure if a release should happen, open an issue.
While the Titus project as a whole is distributed under the Apache-2.0 license, all contributions to the Titus project are submitted to the project under the MIT license. This gives the project maintainers flexibility while ensuring that your rights to your contributions do not change.
The Titus project uses a Contribution Certification that is derived from the Developer Certificate of Origin. It is important to note that the Contribution Certification is not the same as the standard DCO and we do not use the term "DCO" or "Developer Certificate of Origin" to describe it to avoid confusion. Nevertheless, the intent and purpose is effectively the same.
Every contributor agrees to the Contribution Certification by including a
Signed-off-by statement within each commit. The statement must include
the contributor's real full name and email address.
Signed-off-by: J. Random User <j.random.user@example.com>
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 and hereby submit it under the MIT license; 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 MIT License; 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 license(s) involved.