The way I see it I think its 2 big tasks
1. A style guide for module/package makers.
2. A core clean up crew to clean the core. (I will sign up for the core clean up crew, I will try to make myself available if it starts). I think after the first release we should start building the core clean up crew.
Item #1 will me mainly documentation and probably some existing modules that follow the style and guidelines. This can be broken down into 2 sub projects. Documentation and examples, and maintaining a repository of good modules that follow the style. An individual or group will see if a module qualifies to be in the central repository. The a core OpenACS group will maintain the core but the modules will be done by its maintainers. Will the new OpenACS site have somekind of a code repository?
