RE: [tools-pmc] Suggestion for some CVS cleanup in tools

[Doug Schaefer <DSchaefer@xxxxxxx>]

> -----Original Message-----
> From: Philippe Ombredanne [mailto:pombredanne@xxxxxxxxx]
> Sent: Tuesday, October 16, 2007 1:56 PM
> To: 'Nick Boldt'; 'Ed Merks'
> Cc: 'Doug Schaefer'; mik@xxxxxxxxxxx; 'Tools PMC mailing list'; 'Eclipse
> WebMaster (Denis Roy)'
> Subject: RE: [tools-pmc] Suggestion for some CVS cleanup in tools
> 
> I am not sure we came to an agreement on what would be best.
> What I think could be fairly simple:
> - create something like a top level /tool-archives CVS module and work in
> agreement with projects to move there some obsolete modules (Hyades, EMF
> stuffs, etc) with the help of the web masters rootness
> - come with a new tools policy such that new projects *must* use one top
> level module for their wares
> - come with a new tools policy such that existing projects *should* if
> appropriate use one top level module for their wares
> - come with a new tools policy such that projects *should* when
> appropriate
> keep their CVS as clean as possible and avoid modules duplications to
> avoid
> adopters confusion, and when appropriate move obsolete/deprecated modules
> under an /archive /deprecated /obsolete dir ass needed under their top
> level
> modules
> - publish those policies, and encourage existing projects that do not meet
> it to work towards it :-)
> 
> Doug:
> This does not speak to any lack of cohesion between the projects, but
> instead the lack of common policies on CVS top level module usage.

I guess that depends on your point of view. The lack of cohesion actually
manifests itself in a lack of activity on the top level project. If we had a
cohesive group, the project leads would be working together to institute
policies. But they are not.

To date the policy of the Tools project is that the project leads of the
sub-projects rule their own roost. If you want changes you have to ask them
individually.

Sorry, but it is the reality of the situation at the moment.
Doug.