Michiel Meeuwissen wrote:
I think you should not close any project before consulting the members of
the project, or at least the leader of the concerning projects.

Then again, you vannot kepe projects open indefinitely. It invites people to continue changing the code without a thought-out plan.
Also, when a release comes out, I think it is best to close those projects that define the inyterface (i.e. Taglib, MMCI) so there is no ambiguity about which release supports what version of the project.


Riocvhtext is closed because nothing happens, and it is best to close it now an re-open it at a date when time can be devoted to it.

--
Pierre van Rooden
Mediapark, C 107 tel. +31 (0)35 6772815
"Never summon anything bigger than your head."




Reply via email to