This actually brings up more than you think... When all this happened, there was some discussion about pfSense and how some people (including myself) did not trust it and why. This could have gone very poorly, but it actually ended up causing Chris Buechler to contact me directly, and we talked a bit. (This was a good thing! I like Chris!) He also took the time to educate me about the ugly side of trademark law... You have no idea how bad it can get. (If you think the stuff said here was surprising, you would be shocked at stuff not said! ) Projects have lost their own name (nagios-plugins) before, and it is easy to do.
So, you have to take steps to prevent "dilution of your mark" or you will just loose it. What many projects are doing now is enacting a CLA "Contributor License Agreement" and requiring acceptance of license terms before allowing access to the repositories. This is not something I am a big fan of, (The code needs to be free) but having my name stolen is not high on my list either.
So I am still deciding a lot... For the CLA, I am looking into Project Harmony. After all, standards are nice... And for the moment, all the source is in a high powered cluster of servers at home. (But yes I back things up)
I do have plans for a better solution, but I honestly have not decided yet. But for people who are helping with development, access to the SVN can be had. After all, I do have a nice firewall at home.
Interesting information. Good to be cautious. You can pay around $8.00 a month on github to keep the source hidden on their website. You can use this temporarily, mainly to keep a log of all the changes (commits) that you are making. On the other hand most of the source code has to be published anyway since most of it is open source.
Just to bring this back from the dead... SVN is up and accessible, but not listed on the website. This was to keep the slashdotting to a minimum. If you want SVN access, let me know here or in e-mail and you will get the link.