Ed,
This sounds confusing to me. Projects at Eclipse generally use
org.eclipse names and are developed under the EPL by committers on the
project. Eclipse isn't a general purpose content management host for
arbitrary software and all IP contributed to Eclipse is carefully
reviewed and tracked, raising issues like the one Kenn is asking
about. At this point, it's entirely unclear what you mean by "OMG
plugins." Is the OMG looking to develop plugins at Eclipse or are you
just preferring to use different package names for things you see as
being a "pure implementation of an OMG specification"?
Regards,
Ed
Kenn Hussey wrote:
Ed,
Where will the IP for these new projects come from? If anything
originates from activities of (members of) the RTF instead of directly
from you, you'll need to have a CQ approved before committing those
changes (since MDT OCL is a "mature" project and hence does not qualify
for the parallel IP process).
Cheers,
Kenn
On Mon, Dec 6, 2010 at 5:24 AM, Ed Willink <ed@xxxxxxxxxxxxx>
wrote:
Hi
OMG appear to be unable to provide a CM facility for development of its
specifications: UML is hosted at modeldriven.org and
requests for a repository for OCL have been ignored.
My OMG RTF activities that make the OCL specification model-generated
require a CM repository, so I would like to host some org.omg.ocl...
plugins at cvsroot/modeling org.eclipse.mdt/org.eclipse.ocl/omg/...
(migrating to GIT post Indigo).
As well as providing a host for OMG, it will also clearly distinguish
the 'Eclipse-independent' OMG OCL plugins from the added-value Eclipse
OCL plugins while allowing Eclipse OCL to layer on top of the OMG
plugins.
Is this within project scope and acceptable?
Regards
Ed Willink
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
|
