On Thu, Sep 24, 2009 at 5:40 AM, Andrea D'Amore <[email protected]> wrote: > I should have read this message before sending my previous email, still the > question applies: why moving the SCM out of luaforge?
Because it would be way more difficult to implement other SCMs in LuaForge. We considered this for a while but now it seems a lot more practical to let the projects choose where to host their source. Note that LuaForge original intent was to be a project catalog, not a project hosting service. We have no resources for the latter, but the former is easily handled by GForge itself (the software behind LuaForge). Another advantage of decoupling SCM and tickets from LuaForge would be get us closer to a proposal by Yuri of migrating LuaForge to a Sputnik based system. In that vision LuaForge could be a simple directory of project pointers or we could offer a Sputnik instance for every project that needed one. Currently GForge is a pain in the neck to maintain, the list of wanted features just gets bigger and our hability to change the site is really complicated by the fact that stopping a SCM host for maintenance is a huge problem, while stopping a directory is a minor one. It's in the nature of the net to be distributed... :o) André _______________________________________________ Kepler-Project mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
