Steve,

On Tue, Feb 8, 2011 at 9:59 AM, Steve Pinkham <steve.pink...@gmail.com> wrote:

> So Javier, what's your take?

I guess you've said it all. Seems that GIT is our best choice. I
personally have nothing against moving to GIT; on the contrary it
seems even fun... part of the "ruby" spirit, right? :-)

Fortunately we can count on git-python to keep the "auto-update"
feature updated.

>
> Some excellent free git resources for the uninitiated:
> http://progit.org/book/
> http://library.edgecase.com/git_immersion/index.html
> http://help.github.com/
> http://peepcode.com/products/git (I'll buy this video for any of the
> core contributors if it would help)
>

I will need these.

>
> Moving off trac would be... Annoying and time consuming. ;-)
> If SF isn't a good choice for hosting, you can host trac yourself(then
> have to do your own backups, patches, etc) or there are free services
> like http://www.assembla.com/ that allow importing databases.
> Personally I doubt moving trac off of sourceforge would be worth it in
> the long run.  I'd wait for a while until the pain gets higher before
> moving trac if it was me.
>

+1

Thanks Steve.

Javier

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
W3af-develop mailing list
W3af-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w3af-develop

Reply via email to