I've started pushing content to
http://www.getgitorious.com/documentation now (the new official doc is
very much a work in progress but we're gonna keep pushing content to it
over the coming weeks and months).
The new branching model is present under
http://getgitorious.com/documentation#sec-12-2. More to come on how to
generally develop in the Gitorious codebase, we want to make it low
threshold to properly add your own features and possibly merge upstream.
<http://getgitorious.com/documentation#sec-12-2>cheers,
Thomas
On 10/16/2012 10:17 AM, Thomas Kjeldahl Nilsson wrote:
On it. I'm starting to migrate doc/content to
http://www.getgitorious.com/documentation later this week, will move
it there.
cheers,
Thomas
On Tue, Oct 16, 2012 at 9:41 AM, Christian Johansen
<[email protected] <mailto:[email protected]>> wrote:
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
<http://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 [email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:gitorious%[email protected]>
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
