Contributing: Difference between revisions
No edit summary |
|||
Line 15: | Line 15: | ||
* Create a pull request for your feature branch against the 'develop' branch | * Create a pull request for your feature branch against the 'develop' branch | ||
* If your pull request is accepted, your change will be merged. | * If your pull request is accepted, your change will be merged. | ||
* All copyrights should be assigned to AllStarLink, Inc. This ensures that any disputes over copyrighted code can be resolved through our non-profit. | |||
(C) 2018-2021 AllStarLink Inc. | |||
= Contributing to the [https://github.com/AllStarLinkInc/Asterisk AllStar Client Github Repository] = | = Contributing to the [https://github.com/AllStarLinkInc/Asterisk AllStar Client Github Repository] = |
Revision as of 01:03, 1 March 2021
Infrastructure / Web Portal
We're currently looking for volunteers to contribute to the ever growing ASL infrastructure. If you feel you can help out in any way, please contact volunteer@allstarlink.org.
Some technologies we use:
ASL Linux Distribution
Our next release is currently in beta, and all contributions are welcome.
- Submit any bug/issue reports here: https://github.com/AllStarLinkInc/ASL-Live-Build/issues
Contributing
- Fork the repository
- Create a feature branch, such as "fix-problem-x-y-z"
- Create a pull request for your feature branch against the 'develop' branch
- If your pull request is accepted, your change will be merged.
- All copyrights should be assigned to AllStarLink, Inc. This ensures that any disputes over copyrighted code can be resolved through our non-profit.
(C) 2018-2021 AllStarLink Inc.
Contributing to the AllStar Client Github Repository
Like any open source project, AllStarLink's Github repo has a few basic rules regarding contributions.
1. Make sure you only make a pull request on the relevant development branch. (Currently develop)
2. Do annotate your changes so that they are easily understood when reviewed.
3. Do ensure that if your submission contains work from or based on other projects, that you have clearly identified this work, provided a link to the source material, and ensured that the license is compatible with the GNU GPL v2.
4. Do ask questions on the community page [1] before submitting a pull request. Reviews are appreciated as well.
5. Do not claim credit or ownership for code that is not yours.