Re: Luaforge full of empty projects.

[George Petsagourakis <petsagouris@...>]

Jeff Pohlmeyer <yetanothergeek <at> gmail.com> writes:

> 
> Andre Carregal wrote:
> 
> > I'm trying to figure out how to do this in a practical way,
> > suggestions are welcome.
> 
> One thing that might at least help keep the problem from
> getting worse, is to make it clear to the registrants of
> new projects that they will be expected to release some
> sort of code and/or binaries for their project in a
> timely manner.
> 
> Although I didn't look too hard, I really can't find any
> sort of rules or requirements for registering new projects,
> other than the notice on the main page:
> 
>   "The only requirement is that it uses Lua"
> 
> (umm, i guess that would imply that "it" exists 
> 
>  - Jeff
> 
> 
I think that a project should become active if code has been submitted.
If there isn't any code the project should be up for grabs. 
Anyone could take it over, provided that he in turn must post code 
to the csv (cvs is a little old, there are better opportunities nowadays).
The active ones should go for about 10 months and then become inactive.
The inactive project should have a lesser lifetime.