How to Contribute to the DocBook Project on GitHub?

[Thomas Schraitle <tom_schr@web.de>]

Hi fellow DocBookers,

thanks to the release of the new DocBook XSL stylesheets and the
move from SourceForge to GitHub. Great to see this!

Well, as the move to GitHub is still ongoing, I would like to shed some
light on two questions:

 1. How to contribute?
 2. Which branching model does DocBook follows?

It seems, at least to me, these aren't answered yet completely and
things are still a bit foggy. Be it for a new contributor or for an
old-timer. :) Also I couldn't find any information on GitHub in this
regard (although it is somehow implied coming from SourceForge).

=== 1. How to contribute?
What is the preferred method in regards to collaboration for
DocBook@GitHub? I can think of some scenarios:

a. Move all(?) DocBook users on SourceForge to GitHub and give them
   write permissions
b. Only a handful of users get write permissions, others have to create
   pull requests
c. Something completely different?


=== 2. Branching model for DocBook?
Does the DocBook project has decided yet about a branching model?

For example, some projects consider the master branch as "holy" and
only stable releases are published. Others create features in a special
branch and merge them into master after the feature is finished. Some
project use a develop branch etc. So there are almost endless
possibilities with Git in comparison to SourceForge.

Speaking of a develop branch: In this regard, I made some good
experiences with GitFlow[1]. It's "a collection of Git extensions to
provide high-level repository operations for Vincent Driessen's
branching model[2]" according to its home page.


What do you think? :)


-----
[1] https://github.com/petervanderdoes/gitflow-avh
[2] http://nvie.com/git-model

-- 
Gruß/Regards,
    Thomas Schraitle