> 1) use svn as the main repo, and push changes to github > 2) use github as the main repo, and push changes to svn > 3) allow commits to both svn and github, and sync changes > 4) abandon svn > 5) abandon github > > My personal preference would be (2) or (4), but my opinion doesn't > count. I'm just a user. That said, github makes contributing so easy > that it could attract more developers, without the hassle of giving out > commit bits, which is why I prefer (2) or (4) over (1). > > Point (3) tries to please everybody, but I'm not sure how easy that > would be to automate. It'd probably require somebody to be responsible.
This is how Mozilla Labs are trying to do it: http://mozillalabs.com/conceptseries/2010/08/25/contribute-to-labs-projects-on-github clint --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org For additional commands, e-mail: dev-h...@perl.apache.org
