Contributing: Difference between revisions
Jump to navigation
Jump to search
imported>Kg7qin m Added link to Github wiki article on submissions |
No edit summary |
||
Line 1: | Line 1: | ||
Contributing to the [https://github.com/ | Contributing to the [https://github.com/AllStarLinkInc/Asterisk AllStarLink Github Repository] | ||
Like any open source project, AllStarLink's Github repo has a few basic rules regarding contributions. | 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 [https://github.com/AllStarLinkInc/Asterisk/tree/develop develop]'') | |||
1. Make sure you only make a pull request on the relevant development branch. (''Currently [https://github.com/ | |||
2. Do annotate your changes so that they are easily understood when reviewed. | 2. Do annotate your changes so that they are easily understood when reviewed. | ||
Line 11: | Line 9: | ||
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. | 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 | 4. Do ask questions on the community page [http://community.allstarlink.org] before submitting a pull request. Reviews are appreciated as well. | ||
5. Do not claim credit or ownership for code that is not yours. | 5. Do not claim credit or ownership for code that is not yours. | ||
[[Category:Development]] | [[Category:Development]] |
Revision as of 03:47, 18 January 2021
Contributing to the AllStarLink 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.