1,057
edits
Changes
From Gramps
Add Contributing section
==Contributing==
===Create a bug report, feature request or GEP===
* It is good practice for every change to have a bug report, feature request or [[GEPS|GEP]].
* Fixing a bug in an existing bug report is a good way to start Gramps development.
===Discuss the change on the mailing list===
* Important for new features and changes to the user interface.
* Not necessary for small changes or when the has been sufficient discussion in the bug report.
* Agreeing a design before coding could prevent wasted coding effort.
* If the change is large you may be asked to write a GEP.
===Code the change===
* Assign the bug report or feature request to yourself.
* Add the change to the [[5.1_Roadmap|roadmap]] if appropriate.
* Create a GEP branch for large changes.
===Create a pull request===
* Unless it’s a trivial change create a PR to get your code reviewed.
* Add a link to the PR in the bug tracker. Use '''p:gramps:nnn:''' where nnn is the PR number.
==Branches==
* Only new features should be committed to the master branch.
