On Mar 19, 2012, at 12:26 AM, Anne wrote: > Basic ideas all look very good to me. IMO anything that is incomplete or > not maintained should be moved to Attic or Extras, unless there is a very > good reason for keeping it. The reason for moving it should be well > documented. That way it is obvious which code needs work. If someone wants > it, they can fix it and offer to maintain it, and then the community can > consider whether it is important enough to return. > > Hopefully if non-committers can easily see what areas need work, they'll be > more likely to adopt some code. > > Cheers, > Anne.
Anne, I completely agree. I actually see a few more areas of involvement/participation for the community in this cleanup effort: 1) when this discussion will be finalized, we will have a pretty clear roadmap of cleanup tasks to work one; we will then create Jira tasks for the agreed upon removals and community members (committers and non-committers) will have a chance to assign the tasks to them and help the community to implement the plan; this is really a "roadmap" 2) for components candidate to become projects in the Apache Extras (for OFBiz): we will need at least one project maintainer for each of them: this person doesn't necessarily have to be one of the existing OFBiz committers; I would actually like to see new persons show up and take the leadership; we could then delegate to them to write up (in their Apache Extras" project) the goals for the component (of course we will sync with them) 3) for components that will be simply removed (Attic): I agree about the need to document the status of the code at the time of the removal to give opportunity in the future to an interested person to get them and do some more work Kind regards, Jacopo
