I asked the GitHub folks directly what they recommend (see below). Rickard, do you think you would be able to work in this fashion, i.e. not committing code directly into the 'main project repo' ??
I am worried about conflict resolution issues, possibly because I have a lot of bad experience from SVN days. Cheers Niclas ---------- Forwarded message ---------- From: GitHub <[email protected]> Date: Mon, Jul 20, 2009 at 9:54 AM Subject: Re: Setting up a OSS community on GitHub [Account issues] To: [email protected] // Add your reply above here ================================================== From: Tekkub Subject: Setting up a OSS community on GitHub Usually people take the following approach... * create a "project" user (like rails) that hosts the base repos for each project. The password to this account might be shared with a few core developers, to avoid issues if one person leaves * the core developers for the project are added as collabs on each repo. They then manage pull requests and deploying releases from the base repo, but usually don't work in it directly otherwise (all new code is done in branches in forks, then merged in) * everyone who wishes to contribute, forks, including the core developers View this Discussion online: http://support.github.com/discussions/accounts/260-setting-up-a-oss-community-on-github -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
