Depends what the problem is. And, apparently, the 'problem' wasn't in commons, or commons-sandbox, but in avalon.
However, I gathered that part of the problem was code hosted by Apache that wasn't formally adopted by Apache. If that's the case, leaving projects in sandbox for long periods of time exascerbates the problem. However, if that's not part of the problem, then ignore the suggestion. On Tuesday 22 October 2002 09:56 pm, Michael A. Smith wrote: > Steve Downey wrote: > > What about an automatic sunset on sandbox code? 3 months after initial > > commit it's either voted in as a project somewhere, or removed? > > 3 months of inactivity maybe, not 3 months from initial commit. Some > code bases may require a long time to generate the necessary community, > but as long as its active, I don't see a requirement to promote or remove. > > michael -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
