Dmitry, I am not stating that SourceForge is ideal rather their poor implementation of git would facilitate a further transition to GitHub.
In my opinion it would be easier (for all involved) to transition to directly to GitHub for git than leverage the SourceForge (poor) implementation as a workaround. I would be interested in Andreas' opinion as he might prefer SVN over git and hence retaining SourceForge? On Fri, Jul 13, 2012 at 7:28 PM, dimisec <dimi...@googlemail.com> wrote: > The sourceforge "GitWeb" interface looks very weird and has errors - > attached are a couple of screenshots. Not sure anyone would want to > use it... I would definitely prefer GitHub! > > Thanks, > > Dmitry > > On Fri, Jul 13, 2012 at 2:49 AM, Christian Heinrich > <christian.heinr...@cmlh.id.au> wrote: >> Andreas, >> >> The support of Sourceforge for git is available from >> http://sourceforge.net/apps/trac/sourceforge/wiki/Git >> >> I can also assist with the mitigation to GitHub or >> http://www.kernel.org/pub/software/scm/git/docs/git-svn.html if >> needed. >> >> On Thu, Jul 12, 2012 at 9:43 PM, dimisec <dimi...@googlemail.com> wrote: >>> Hi Andreas, >>> >>> would you please consider moving the code from SourceForge to GitHub? >>> SourceForge overloads the site with ads, and GitHub would be more >>> developer-friendly environment. >>> >>> I want to check out the code to look at Taras' project, but the svn >>> client gives a certificate error: >>> >>> $ svn co https://w3af.svn.sourceforge.net/svnroot/w3af/branches/webapps >>> w3af-webapps >>> Error validating server certificate for >>> 'https://w3af.svn.sourceforge.net:443': >>> - The certificate is not issued by a trusted authority. Use the >>> fingerprint to validate the certificate manually! >>> Certificate information: >>> - Hostname: *.svn.sourceforge.net >>> - Valid: from Sat, 25 Feb 2012 23:58:41 GMT until Sun, 31 Mar 2013 >>> 19:51:44 GMT >>> - Issuer: GeoTrust, Inc., US >>> - Fingerprint: 0b:11:76:de:db:4c:74:72:cb:01:49:7d:13:70:c2:f1:13:7b:cb:bf >>> (R)eject, accept (t)emporarily or accept (p)ermanently? ^C >>> >>> I think I had the same error a year ago - so the Sourceforge probably >>> does not care. I've never seen a certificate error when working with >>> the GitHub. I hope you and the community would make the move! :) >>> Thanks. >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> W3af-develop mailing list >>> W3af-develop@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/w3af-develop -- Regards, Christian Heinrich http://cmlh.id.au/contact ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
