I was wondering if it would be in the best interests of the application builder project to move our source from sourceforge to google projects.
I've just done that with one of my own projects, a C++ A* search implementation. http://code.google.com/p/a-star-algorithm-implementation/ The advantages are the obvious reliablity (both uptime and speed) of google infrastructure. (I've noticed a lot of downtime and slowness on sourceforge.) The bug (or issue) tracking is very simple, very visible, and easy to use. Downsides are that there is no release mechanism for easy download. Casual users may be put off by having to use subversion to get a release. Yet theres nothing stopping us putting an automatically zipped up release in the subversion database which can then be linked to in their web site. Also you need a google account to identify you. So if someone wants to create a bug or fix some code, they need to be a google user first. Just a thought. I will set up the project if it's considered a good idea. Justin _______________________________________________ application-builder mailing list [email protected] http://www.lispniks.com/mailman/listinfo/application-builder
