2,718
edits
Changes
Jump to navigation
Jump to search
Contributing to Zynthian Development (view source)
Revision as of 14:14, 27 November 2018
, 14:14, 27 November 2018Created page with "We would appreciate you to use the tools we use for developing, as it's a lot easier for coordinating the tasks, having traceability, testing, merging changes and of course, a..."
We would appreciate you to use the tools we use for developing, as it's a lot easier for coordinating the tasks, having traceability, testing, merging changes and of course, attributing the merit of every fix or improvement.
We use '''git''' as versioning tool and '''github''' as repository server and issue/task tracker: [https://github.com/zynthian Zynthian's Repository Index]
If you are a punctual contributor, you should follow this procedure:
* fork the repository
* make the changes
* test it
* make a pull request
When you are a habitual contributor, you will receive write access to the repositories you master and would use development branches instead of forking/pull-requesting.
Also, '''it's a good habit to create a task/issue associated with more relevant changes''', specially if you are a newcomer. In such a way other developpers will be informed of your intention of implementing a new feature or fixing a bug and will avoid overlapping efforts, at same time allowing other developper to contribute to your task by adding useful knowledge and alternative approaches.
We use '''git''' as versioning tool and '''github''' as repository server and issue/task tracker: [https://github.com/zynthian Zynthian's Repository Index]
If you are a punctual contributor, you should follow this procedure:
* fork the repository
* make the changes
* test it
* make a pull request
When you are a habitual contributor, you will receive write access to the repositories you master and would use development branches instead of forking/pull-requesting.
Also, '''it's a good habit to create a task/issue associated with more relevant changes''', specially if you are a newcomer. In such a way other developpers will be informed of your intention of implementing a new feature or fixing a bug and will avoid overlapping efforts, at same time allowing other developper to contribute to your task by adding useful knowledge and alternative approaches.