J Aaron Farr wrote: ... cut ... > As for dormant code, leave it where it is. If we still have a few > committers working on it and making releases occasionally, then we'd > still need a functional PMC. Otherwise, if we get enough noise about > a subproject, it can be revived (perhaps with help from the > Incubator). > ... cut ...
There may be many reasons why a project turned "dormant": no interest (dead technology), committers having gone astray, etc. One reason that may be special is a project which got developed, is used, but there is no reason to develop it further. If classifying a project as "matured" it still may need fixing of problems and/or enhancements over time, making it necessary to create a new distribution. The idea of putting a "matured" project into the "incubator" realm does not sound "right" to me. It would not be a project which needs to gain additional developers to "grow", if it has become clear that it is matured. Or with other words: I would not expect a "matured" project to get out of an "incubator", which (from the name) is probably meant to try out, interest, nurture new projects. Also morphing a matured project into a TLP seems not to be concludent to me (a TLP should be either an umbrella for other "little" active projects that belong somehow together, or be a project that gets actively developed for the foreseeable future and has a broad developer and user community). Case in question: the Beans Scripting Framework. Version 2.4.0 has gone Golden last fall and it is expected to be stable. There may be new engines that get developed for this Java scripting framework, but from todays perspective, there are no new features for 2.4.0 that can be foreseen. So 2.4.0 would be in "matured" mode, people are using it and maybe new Java developers take advantage of it. There is a new version (3.0) of BSF in beta, created according to the JSR-223 specs, implementing the official Java scripting framework in opensource under an Apache license, and can be deployed starting with Java 4. There are plans by ant to eventually test it againast the TCK. Now this version is in active development, but if everything goes well, it will become "mature" once it is officially released. Then this project would be in "maintenance" mode as well, mainly bug-fixing and supporting users will be necessary. Of course, if Sun's Java scripting framework gets enhanced, then these enhancements would probably be incoroportated into the future BSF 3.0. Unless there are already rules that mandate that projects that got developed to a point after which they go into "maintenance" mode need to go into the "incubator", I would suggest to create a new classification for such projects. They should be named "matured". Depending whether there are committers who maintain matured projects, they should be further qualified as "maintained" projects, or otherwise be put into an archive of unmaintained matured projects. ---rony --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
