On Sun, 10 Nov 2002 18:48, Stephen McConnell wrote: > WHEREAS, the Board of Directors deems it to be in the best interests > of the Foundation and consistent with the Foundation's purpose to > establish a Project Management Committee charged with the creation > and maintenance of open-source software related to component and > service management, for distribution at no charge to the public.
I don't think this scope is something we want to accept. It is too broad a definition. Do we cover webservices? Do we cover EJB containers? Do we cover ORBs? Do we cover servlet engines? Everything there is related to "component and service management" yet little would be appropriate for avalon. It also stops us hosting enabling technologies. I would prefer a more specific scope that restricted us to maintaining component technologies developed on top of our lifecycle definition. I would also prefer that enabling technologies also be considered in scope. > RESOLVED, that the Avalon PMC be and hereby is responsible > for the creation and maintenance of software related to component > and service management, based on software licensed to the > Foundation; and be it further I would prefer to remove the phrase licensed to - if it needs to be ammended in the future then we can do that. Until such a time I would like to restrict our work code owned by Apache. -- Cheers, Peter Donald ----------------------------------------------------------------------- | I thought there was a knob on the TV to turn up the intelligence. | | There's a knob called "brightness", but it doesn't work. | ----------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
