Proposing a change

Tesria takes changes as pull requests on GitHub.

Step 1: Say what you want to change, first

For anything more than a small fix, open an issue describing the problem and what you have in mind before you write the code. It is the quickest way to find out whether it fits, and whether someone is already on it.

Step 2: Make the change on a branch

Fork the repository, make a branch, and keep it to one change: a fix and an unrelated tidy-up are two pull requests.

Step 3: Test it, and look at it

The tests pass (see Running the tests), and you have tried what you changed in a browser. Add tests for new behavior.

Step 4: Open the pull request

Say what it changes, why, and how you checked it. GitHub runs the tests on it. A maintainer reviews it, may ask for changes, and merges it when it is ready.

The license of what you send

Tesria is under the Apache License 2.0, and so is anything you contribute to it: the license itself says that a contribution you submit is under its terms unless you say otherwise. Only send what you have the right to send.