Difference between revisions of "Contributing"
Jump to navigation
Jump to search
(Initial page creation) |
m Tag: visualeditor |
||
| Line 1: | Line 1: | ||
| − | + | Contributing to the AllStarLink Github repo | |
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. ( | + | 1. Make sure you only make a pull request on the relevant development branch. (''Currently [https://github.com/AllStarLink/Asterisk/tree/develop develop]'') |
| + | |||
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. | ||
| + | \ | ||
| + | |||
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 on questions on the relevant mailing lists before submitting a pull request. Even reviews are appreciated as well. | 4. Do ask on questions on the relevant mailing lists before submitting a pull request. Even reviews are appreciated as well. | ||
| + | |||
5. Do not claim credit for code that is not yours. | 5. Do not claim credit for code that is not yours. | ||
| − | |||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 16:44, 22 November 2018
Contributing to the AllStarLink Github repo
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 on questions on the relevant mailing lists before submitting a pull request. Even reviews are appreciated as well.
5. Do not claim credit for code that is not yours.