Difference between revisions of "Contributing"
Jump to navigation
Jump to search
m |
m |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Contributing to the | + | Contributing to the [https://github.com/pttlink/Asterisk PTTLink Github repo] |
| − | Like any open source project, | + | Like any open source project, PTTLink'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/ | + | Read this before making a pull request: https://github.com/pttlink/Asterisk/wiki/Submissions |
| + | |||
| + | 1. Make sure you only make a pull request on the relevant development branch. (''Currently [https://github.com/pttlink/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. | ||
| Line 11: | Line 13: | ||
4. Do ask questions on the relevant mailing lists before submitting a pull request. Even reviews are appreciated as well. | 4. Do ask 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 or ownership for code that is not yours. |
[[Category:Development]] | [[Category:Development]] | ||
Latest revision as of 23:29, 31 December 2020
Contributing to the PTTLink Github repo
Like any open source project, PTTLink's Github repo has a few basic rules regarding contributions.
Read this before making a pull request: https://github.com/pttlink/Asterisk/wiki/Submissions
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 relevant mailing lists before submitting a pull request. Even reviews are appreciated as well.
5. Do not claim credit or ownership for code that is not yours.