Contributions of source code, documentations, and fixes are happily accepted via github merge requests. Please see
https://bandframework.github.io/software/
for a discussion of the process.
If you are planning a contribution, reporting bugs, or suggesting features, we encourage you to discuss the concept by opening a github issue at
https://github.com/bandframework/bandframework/issues
or by emailing members of the BAND and interacting with us to ensure that your effort is well-directed.
To contribute a package to the BAND Framework, please see the [BAND Software Development Kit (SDK)](/resources/sdkpolicies/bandsdk.md), which includes requirements and recommendations.
BAND expects new major version releases of the framework to occur annually.
Status as a named coauthor will be granted for those who:
- make significant contributions to the Framework (in implementation, documentation, conceptualization, review, etc.) and
- maintain and support those contributions.
BAND's Design and Oversight Committee (DOC) will do their best to notice when contributions reach this level by editing AUTHORS, but please email or create an issue if you believe your contributions have met these criteria and haven't yet been acknowledged.
Coauthorship is expected to persist in all future releases, with new contributors being appended to the list of authors. If contributors decline to be listed as coauthors, they will be acknowledged in the repository, manual, and release notes.
The BAND Framework is distributed under a 2-clause BSD license (see LICENSE). The act of submitting a pull request or patch will be understood as an affirmation of the following:
Developer's Certificate of Origin 1.1
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 submit it under the open source license
indicated in the file; 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 same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; 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 the open source license(s) involved.