The issue is that we want to structure more the development of MMBase. Now we have some MMBase projects that start with a well defined goal, and a group of project members. But during time frequently goals change and project members become inactive. In the future we want MMBase projects to update the community (every 2 months) with the progression of their projects. Some projects that are already inactive for some time can be closed, and restarted if new forces become available. Other projects should inform the community with well defined goals. The reason why we wanted to close (and maybe reopen directly) some projects is because we want to see again well defined goals for those projects and that we want to see which project members are willing to recommit themselves to the project.The taglib-project did not reach all its goals as defined in the initial description.
You cannot say that the taglib project is 'open indefinitely' because imho
it is certainly growing in a certain well defined direction, and I think is
one of the more active projects.
If the project must be closed before the release then I suggest we stall the
release because the project is not finished.
It would by the way be no problem to increase the taglib version number after the release.
It is silly to say that a project is finished only because MMC decides that
it is because there is a release. That is a turned-around reasoning which I
would expect from comercial software... I think a project is finished when
it's finished, and that can be after a week or after 5 years, it only
depends on well er.. if it is ready or not..
Rob
