Hi all, Carregal has finally agreed (or should I say that I browbeat him into finally agreeing :-) ) to take the Kepler modules that I maintain out of LuaForge source control and issue tracking. I have been using git for personal stuff for some time now, with github as my public source control provider, so I decided to create a "keplerproject" account at github and start importing the Kepler modules to there (via git-cvsimport, preserving the soure history, of course). The url is http://github/keplerproject, and I already moved Orbit, Xavante, WSAPI, LuaFileSystem, and Kepler (the installer and support files) to there (just the HEAD for now, I still have to push the tags). LuaSQL, Copas, Coxpcall and Rings are also moving there.
After all the projects are in the new home I will update the rockspecs in rocks-cvs to reference the git repositories at github instead of LuaForge, then disable the SCM and Tracker tabs of the LuaForge project pages. Github's issue tracker is not as feature-full as GForge's, but much less ennervating in actual use. I hope that moving the projects to a modern DVCS will make it easier for everyone to fetch development versions and collaborate with patches. Why github and not some other git provider? Github is what I am used to, I like the interface and it has a simple integrated issue tracker. The web interface is somewhat slow right now, but it should get faster after they complete the move to their new hosting provider. -- Fabio Mascarenhas, Lablua http://www.lua.inf.puc-rio.br _______________________________________________ Kepler-Project mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
