I like Henri's way of framing this. Velocity is a good example of a mature project, for example. Has an active user list and committers who are present, if little actual day-to-day developer activity.
WILL On 7/31/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
When no one argues with it being called dormant? :) (go circular logic). We've a bunch of meanings to cram into place. Obsolete is one term, sometimes due to JDK advances (ORO, Regexp, Commons-Logging) and sometimes because no one is really interested in the idea (ECS). The current status within Commons is that we've put things under Dormant if they hadn't had full releases. Inactive, yet released things have not been dealt with yet. Mature is very different - a mature project should still have an active user list and bugfixes being slowly made; at least someone should be listening. They don't however have any new development happening or likely to happen. For a mature project, I don't think we have to worry about labelling, we just need to make sure that people are still listening. Once the user mailing list is dead, that's when it's no longer mature and has become dead/dormant. You can argue about the dead/dormant labelling, but I think the easiest is to just go with Dormant for anything which is dead both in terms of user and dev lists. As time goes by we can refine that further. So.... * Mature projects - no change. Just something to look out for; a dead dev list and active user list with no one listening to bug reports being the bad state of a mature project. * Dormant projects - dead user list, dead dev list. Something becomes dormant by calling a vote on general@ suggesting it be moved to dormant. Forward the vote thread to the dev/user lists as a notification. Hen On Sat, 29 Jul 2006, Henning Schmiedehausen wrote: > Hm, > > how do you consider a project "dormant"? Is Velocity "dormant"? > > What I want to avoid is, that mature projects which are exactly where > the committers want them to have and the "one release a year, just bug > fixes" are put in the same bucket as projects that might be dormant or > dead. Once a project is in that state, FUD is inevitable. > > We should make the effort to distinguish between stable projects/code > and dormant/dead code. > > Best regards > Henning > > > > On Sat, 2006-07-29 at 13:25 -0400, Henri Yandell wrote: >> >> On Sat, 29 Jul 2006, Oliver Zeigermann wrote: >> >>> Hi, folks! >>> >>> Recently, worries about the state of the Slide project came up in >>> private lists. It seems to be more or less unsupported and no >>> community seems to exist any more. Most posts to the lists remain >>> unanswered. >>> >>> Additionally, I have heard voices who consider Slide redundant now >>> that Jackrabbit is a TLP. >>> >>> While this is not the thread to find out what has happened to the >>> Slide project, we should think about what to do about it. >>> >>> If there is no one who feels responsible for the project or is willing >>> to take responsibility we might put it into a dormant/unmaintained >>> mode. This might give possible new users a warning. >>> If new people came up who are ready to take the responsibility we >>> might revive it. >>> >>> Additions? Opinions? Other voices? Am I completely wrong? >> >> Looking at mail-archives; >> >> Emails on the user list are 10% of what they were at the lists peak about >> 20 months ago. 40 odd so far this month, a dozen threads. >> >> Emails on the dev list are down to around 5% of what they were at its peak >> (20 months ago too). 30 emails this month. 4 threads from contributors, >> not committers and a bunch of automated wiki/issues/commit ones. >> >> How about creating a Dormant section on the LHS under Subprojects and >> kicking off a vote to put ORO, Regexp, Slide, Alexandria (I know, it's >> dead but simpler to put under Dormant for the moment), and ECS into it? >> >> The Incubator are going to be putting Agila into dormancy I think - so we >> can simply delete that link. >> >> Hen >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > -- > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ > > RedHat Certified Engineer -- Jakarta Turbine Development > Linux, Java, perl, Solaris -- Consulting, Training, Engineering > > Social behaviour: Bavarians can be extremely egalitarian and folksy. > -- http://en.wikipedia.org/wiki/Bavaria > Most Franconians do not like to be called Bavarians. > -- http://en.wikipedia.org/wiki/Franconia > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]