Hi Alon, > Hello, > > GIT/SVN repository is expected to be published clearly in opened > source projects, just like you have Download option in menu, there > should be Source or similar. > Agreed, Git repo is too hard to find currently. I'll get this fixed. > If your git is the one that is candidate for next release, publish it, > better something than nothing. > > Also, please install gitweb, so the repository can be tracked online. > The "beta2.2" branch in Git is the basis for the next release. It's hosted on SF.net, and instructions for using it are here:
<https://community.openvpn.net/openvpn/wiki> Trac has it's own Git browser, but it's pretty slow and does not scale up well. Fortunately SF.net provides a GitWeb interface already: click on the "Source" link in Trac panel. Or use this direct link: <http://openvpn.git.sourceforge.net/git/gitweb.cgi?p=openvpn/openvpn-testing.git;a=summary> > You should have a branch for the "james" openvpn so people know what he acked. > James' SVN tree is just another "external" tree, like cron2's or jjo's. All ACKs James gives will be announced on openvpn-devel and will also show up in Git commit logs. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
