Changes

Jump to: navigation, search

Developer policies

No change in size, 21:17, 18 April 2018
m
Becoming an official developer
* Accept the guidance from existing developers. If you do not agree with them, you need to convince them. To do that, first consider 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 (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 the technical architect (Nick) to send you an invitation to join the GitHub ''Developers'' team. If you did have not have had contact with the 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