On Mon, Dec 8, 2008 at 10:44 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Tue, Dec 9, 2008 at 5:07 AM, Henri Yandell <[EMAIL PROTECTED]> wrote: > >> ** Explain what the Attic is. > > Yes, I would like to know that; > > Let's say that a project X is used widely around the world. It is so > complete, low-level and bug-free that noone ever touches the code. But > it is still very useful, popular and indispensable for what it does. > Is this a candidate for Attic?
Could be. If it no longer has a developer community - defined by being unable to obtain 3 release votes, no longer belonging to a PMC or selected for the attic by its pmc - then it is a candidate. Being in the attic is our admission to the users that there is no developer community surrounding the product and they should look to themselves and other users if they have any issues. Bug-free is a tricky one. I've not seen such a thing, but if we did have something then you could argue that it has a developer community until the moment arrived (bug report) in which they would have to be seen. > If so, is it fair that it is called "Attic", since it gives the > impression "We chuck it away so that no more people use it.". I think > it boils down to a question that have been with me for a while; "Does > a project need a community for me to really use it?" I think it'll depend on project - some might make sense to allow bug reports to still come in. Definitely makes sense to keep user lists open I think. Much of the aim is to have a project still useable - rather than vanishing overnight into a hard to find corner of the ASF. Hen
