Changes

Jump to: navigation, search

Developer policies

96 bytes added, 21:07, 18 April 2018
Becoming an official developer
=== Becoming an official developer ===
The road to become an official developer is as follows:
* Fix bug issues bugs on the bug tracker and participate in the ''gramps-devel '' mailing list. * Accept the guidance from existing developers. If you do not agree with them, you need to convince them. To do that , first consider first to code coding what is asked for and pointing out the weakness afterward, i.e . let the code speak for you.* Take up a feature request after assuring yourself (eg e.g. via the ''gramps-devel '' mailing list) the feature will probably be accepted by the developers. **Let your code be reviewed. * Once you come to the conclusion your code needs little change before commit, ask one of the admins technical architect (Benny, BrianNick) to add your Github id send you an invitation to join the list of developersGitHub ''Developers'' team. If you did not have contact with the admins technical architect yet, ask one of the other developers to vouch for you.* Even after you obtained commit rights, consider a review of your code by other developers by submitting a pull request or using the bug tracker (send reminder) or the ''gramps-devel '' mailing list.
[[Category:Developers/General]]

Navigation menu