ok, I have converted this over. Can you take a look and see if all is well before we switch the trac and other info over to it?

git clone ssh://git.fedorahosted.org/git/securityguide.git

I don't know if it's worthwhile, but for a conversion, it's often desirable to drop the git-svn metadata. And bonus points for setting up an authors file so that commits have nicer author identification. There is a page on the wiki where David Nalley put together some information on both of these things. (I helped with this and wrote a little script for creating the authors file.)

https://fedoraproject.org/wiki/User:Ke4qqq/gittosvnsop

There's a section at the end showing the steps used to convert another project.

We can talk more in #fedora-admin about how to work out the branches for the repo.

I did another git-svn conversion, using an authors file and removing the git-svn metadata. To get a clean conversion, I had to use the --branches option, since the svn repository did not use the standard branches/tags/trunk layout. For future reference, here's a brief review of the steps used, where they differ from the gittosvnsop referenced earlier:

{{{
$ git svn clone --branches=community -A authors --no-metadata file:///svn/securityguide
...
$ cd securityguide

No tags were present, but if you did the next step on a repo that had tags

it would cause grief.

$ mv -v .git/refs/remotes/tags/ .git/refs/tags/ && rmdir -v .git/refs/remotes/tags
$ mv -v .git/refs/remotes/ .git/refs/heads/

Remove the trunk reference, if it matches master (it should)

$ diff -q .git/refs/heads/{master,trunk} >/dev/null && rm -vf .git/refs/heads/trunk
}}}

I've changed trac to use the git repo. You will want to change the front trac page to point to the git repo now too. ;)