On Sun, Feb 6, 2011 at 10:11 PM, Ivan Hamer <tic...@gmail.com> wrote:
> > I would like to be able to send in some contributions, but couldn't find > much information on the topic. There is a ticket on adding this info to the > FAQ (http://fossil-scm.org/index.html/tktview?name=15dfbde729) > Do what are the guidelines on how to contribute to fossil? > > Specifically, I am interested in: > > 1. Which branch to work on? > 2. What to do with changes? > (How to test? Do I create a patch? Where to send the patch?...) > > I am volunteering to create a wiki/faq/documentation page on this topic. > I've been thinking I need to write all of this up. It has simply been crazy lately and I've had to focus on other priorities. In order to maintain clear title, I ask that all contributors sign a copyright release prior to getting check-in privilege. After receiving check-in privilege, new contributors are asked to store on branches only - at least until such time as I can evaluate their work. And, experimental changes always go on a branch. We desire to keep the trunk working and ready-to-use at all times. I need to work up checklists for coding style and design rules. I started on a testing checklist which you can see at http://www.fossil-scm.org/fossil/doc/trunk/test/release-checklist.wiki but it needs a lot of work yet. A lot of this I'll need to do since I'm the only one with the knowledge to do it. But I'd still appreciate any help and/or advice. > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
