Cleaning Project Due to the lack of progress and lack of focus in the Cleaning Project I am restating the purpose of the project.
The Cleaning Projects purpose is as follows: - To remove deprecated code, unused code and bad engineered code. With a focus on code that is still specific for the VPRO. - Increased configurability of classes, especially towards different languages, and bad constants. Package restructuring is outside this project. I consider this too big for this project and suggest that this will be it's own project. Fases in this project: - Tagging fase, we are currently in this fase, and every developer is free to tag code. See also http://web.omroep.nl/mmbase/deprecation/plan.html - Cleaning up the code, this fase will probably occur after the freeze and release of 1.7, and hence will take place in 1.8 This because otherwise the release of 1.7 will be delayed too much. Things related to this project but outside of it are free for developers to do: Reindentation and documenting code, or more in general applying codeconventions. However class/package restructuring does not fall into this, and will require a vote. Also cleaning which requires code changes (in non-bug cases) is only allowed after a vote. See also http://web.omroep.nl/mmbase/deprecation/codingstandards.html -- Rico Jansen ([EMAIL PROTECTED]) "You call it untidy, I call it LRU ordered" -- Daniel Barlow
