The scala-js-browser-extension-example project welcomes contributions from anybody wishing to participate. All code or documentation that is provided must be licensed with the same license that scala-js-browser-extension-example is licensed with (Apache 2.0, see LICENSE).
People are expected to follow the Scala Code of Conduct when discussing scala-js-browser-extension-example on the Github page, Gitter channel, or other venues.
We hope that our community will be respectful, helpful, and kind. If you find yourself embroiled in a situation that becomes heated, or that fails to live up to our expectations, you should disengage and contact one of the project maintainers in private. We hope to avoid letting minor aggressions and misunderstandings escalate into larger problems.
-
Make sure you can license your work under Apache 2.0
-
Before starting to work, make sure there is a ticket in the issue or create one first. It can help accelerate the acceptance process if the change is agreed upon
-
If you don't have write access to the repository, you should do your work in a local branch of your own fork and then submit a pull request. If you do have write access to the repository, never work directly on master.
-
Submit a Pull Request.
-
Anyone can comment on a pull request and you are expected to answer questions or to incorporate feedback.
-
It is not allowed to force push to the branch on which the pull request is based.
-
It is recommended that the work is accompanied by unit tests.
-
The commit messages should be clear and short one lines, if more details are needed, specify a body.
-
New source files should be accompanied by the copyright header (should be taken care of automatically by the build tool, but do check).
-
Follow the structure of the code in this repository and the indentation rules used.
-
Your first commit request should be accompanied with a change to the AUTHORS file, adding yourself to the authors list.