 |
lua-l archive |
|
|
||
|
Rather than have it auto-aggregate from a number of varied sources, however, I think a better plan would be to have it act as a lightweight hub, which would be used as a single point from which to track where the homepage is hosted, what repositories (LuaDist, LuaRocks, deb-pkg, Synaptic, SourceForge, Launchpad, LuaForge itself if package hosting is supported going forward, etc.) it is distributed/mirrored on and which (if any) is the development focus "main" host. Registration would be automated for both users and projects.
It would be primarily used, like the current site, as a destination for discovery of applications and libraries that use Lua, categorized by type (application/game with Lua support, Lua library/module/package, Power Patch, set of Lua scripts), then by field (games, sound, graphics - the same tree LuaForge already has (although there might be a different tree for power patches)). Projects could either be registered by the project's manager/developer, with homepage hosting provided and editing allowed only for them ("hub page" style), or by anybody who knows about the project, editable by anyone and owned by no one, but claimable by the project manager at any time after creation ("wiki entry" style).
It would also be useful if it provided homepage hosting for Lua projects (like the current version's <project>.luaforge.net sites), since many of the alternative hubs that have been suggested for code hosting and the like do not provide this service (really, everybody but Sourceforge). The biggest thing LuaForge could non-redundantly provide (assuming this would be possible) would be Kepler Lua Page support in project sites. This could be complimented with a page for adding files for the most common project page setups (such as Sputnik or a set of Lua scripts that generates pages that look like the Kepler manuals whose style 90% of LuaForge projects copy). Hosting Lua Pages would also provide a convenient avenue for library projects to provide a live demo.
As stated though, bug tracking and source control are best handled by many other sites that make this their sole purpose.
I think a good model to work from would be Launchpad (http://launchpad.net). Once you've registered for an account, you can create a page for your project simply by following a link and choosing a long name and a Unix name for it, at which point you enter your details (project homepage, where the packages are, where the source is, where the bug tracking is), with opt-in choices for each of the details for services that Launchpad provides.
"Andre Carregal" <carregal@fabricadigital.com.br> wrote in message 92ab989c0910071015y115ad3c4k9fabfe00d092dc49@mail.gmail.com">news:92ab989c0910071015y115ad3c4k9fabfe00d092dc49@mail.gmail.com...
I have bad news about LuaForge, the damage on LuaForge might take some time to recover. We have data backups for everything, but redoing a GForge installation is going to take a while. To make things harder, we are all involved today in the Lua Workshop so this may impact the recovery time too. The current plan is to create a new GForge setup and import the data. If there is anyone on the list with GForge knowledge, please contact me off list. I'll keep the list informed about the progress on this operation but our expectations are that this will certainly take a few days. Unfortunately, until them we are out of luck with these services: luaforge.net main site (catalog, project info, files downloads, CVS, issue tracker, forums) projects mailing lists projects FTP (the project_name.luaforge.net sites are up) I'm really sorry for the trouble this have caused for everyone using LuaForge services and I hope we can have everything back asap. Meanwhile, I'd like to know what you think about eventually moving from this setup based on GForge to one based on something else. One option would be to recommend that projects moved their SCM to sites like github or Google Code and then leave luaforge.net as just a catalog and news site. Of course this eventual migration would be possible only after LuaForge is back up (still using GForge). Thanks in advance for your patience. André