"Derick Eddington" wrote: > After taking a look at GitHub and some articles about > collaborating there, I'm still unclear about how we should > use it. I don't understand what collaboration structures > are possible. I've got the impression that it's not > possible to have the primary repo controlled by multiple > people, one person controls it and others fork and request > the controller to merge, is that correct?
It is possible to add collaborators to a project[1], however I do not know how this works with free hosting plans. It seems to me that the curl project is adopting this model: bagder is the main developer, which owns the project, but a number of people commit stuff without forking (at GitHub). In any case there is no "primary" repo, everyone can officially name one of its branches as the leading one; if the user controlling the leading branch must give up for some reason, another user can take the lead and declare to "have it" by posting a message with the branch URL here. This is somewhat confusing for end users, but I think collaborators can just take care of it. [1] <http://github.com/guides/managing-collaborators> -- Marco Maggi
