I\'ve read a great deal of \"go from svn to git\" and other \"git-svn workflow\" articles on the web, and still I think they often deal with overly simple situations. They a
As soon as you step in "distributed" issue, you are better off with one bare git repo cloned amongst developers.
Regarding the export-import phase to the public SVN repo, for other to use, the scripts
git2svn and svn2git can help encapsulate the magic.
Other considerations when working in Git and SVN repos are found in the question "Workflow and help with git, 2 svn projects and a single “workcopy”"