Skip to content

Latest commit

 

History

History
40 lines (29 loc) · 2.32 KB

CONTRIBUTING.md

File metadata and controls

40 lines (29 loc) · 2.32 KB

Contributing

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer

We Develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.

We Use Github Flow, So All Code Changes Happen Through Pull Requests

Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:

  1. Fork the repo and create your branch from master.
  2. Make sure your code [lints](#Use a Consistent Coding Style).
  3. Issue that pull request!

Report bugs using Github's issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!

Get coding!

Start here

Use a Consistent Coding Style

  • JavaScript Standard Style - We use eslint and provide a config file.
  • Use SPDX-License-Identifiers:
    • The SPDX license identifier shall be added at the first possible line in a file which can contain a comment.
    • // SPDX-License-Identifier: (GPL-3.0-or-later AND Apache-2.0)

License

We are initially GPL-3.0-or-later but will move to Apache-2.0 as soon as we refactor the stackoverflow code.

By contributing, you agree that your contributions will be dual licensed under (GPL-3.0-or-later AND Apache-2.0). You also agree to the Developer Certificate of Origin so please Sign-Off your commits: git commit -s.

References

This document was based on a template by briandk adapted from the open-source contribution guidelines for Facebook's Draft