On Apr 22, 2010, at 08:46 , Peter Stuge wrote: > Andreas Jellinghaus wrote: >> b) use git/hg/bazar with svn bridge to import current opensc repository >> and all future changes to it, and develop in git/hg/bazaar. you can >> publish your codebase on one of the popular hosts (github, launchpad, >> the mercurial hub whose name I don't remember right now), or on >> opensc-projects.org (I guess, pending martins approval) - only a small >> admin work needed to add some ssh account for you with write access >> in /var/www/some-name > > I'm happy to help set up git hosting on opensc-project.org. > I have it running well for a few other projects already.
The nature of git does not need a central git repository. If git would be to used, I'd go for github, which provides a bunch of nice features in addition to just publishing the source. Additionally, "traditional" setups (like IDE-s, corporate environments, windows etc) work well with SVN which is not true for git. Eventually, what is the "official source code channel" and how developers work and share the code does not have to match. For an example have a look at a "using git for Django" description [1] written by a colleague of mine. Using SVN as the master repository, at least now, is good for backwards compatibility with peoples minds and existing tools. [1] http://code.djangoproject.com/wiki/CollaborateOnGithub -- Martin Paljak http://martin.paljak.pri.ee +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
