> > My one suggestion is to make this policy crystal clear to new >> developers. Whenever I write a patch for a project I want to know >> "what branch do I base this on in order to get it accepted ASAP?" If >> you make it very clear in the HACKING file, and in the wiki, that >> patches should be proposed against "next" in the form of Gitorious >> merge requests, then it will be much simpler for contributors to join. >> > > Ken, > Thanks for the feedback, I'm definitely adding a note to the HACKING file. >
Suggestion: Let's put this post on getgitorious.com, put a small note in the HACKING file, and also link to the full outline in the docs. Christian -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com
