[news.eclipse.technology.ohf] Re: OHF Project Development Policy

["Brian Barry" <brian@xxxxxxxxxxx>]

Having had the benefit of the discussions at the OHF meeting last week I
think what Grahame has been calling subprojects are "Components" in the
Eclipse Technololgy nomenclature, ie division of the technical work into
coherent sub-systems, within which it makes sense to assign committ rights.

I think the distinction, to the extent there is one, is that components are
intended to be less autonomous than sub-projects, and must coordinate with
other components and with the project as a whole. I'm not sure that in
practice in a well run project it matters much.

And just bye the bye, I thought "subproject" had disappeared completely from
the lexicon and that we were using "top level project" and "project"
exclusively?  Sorry to nit-pick, but I know this is causing confusion for
people who are new to the game.


"Bjorn Freeman-Benson" <bjorn.freeman-benson@xxxxxxxxxxx> wrote in message
news:4368E35A.50105@xxxxxxxxxxxxxx
> Grahame,
> The Eclipse rules of engagement do not provide for OHF to create
> sub-projects.  The Eclipse Development Process is designed to provide a
> balance between project-free-for-all and
> membership-understanding-what-is-going-on. The EDP provides for
> top-level projects (OHF is part of the Technology top-level project) and
> sub-projects (such as OHF). It does not have the concept of sub-projects
> having sub-projects. Please contact me if you would like to discuss the
> process and how to work within it.
>
> - Bjorn Freeman-Benson
>
> > I propose that OHF hosts sub-projects of it's own. All the actual work
> > of OHF will happen in the sub-projects - they have their own creation
> > proposals, requirements, committers, and deliverables and milestones