[mdt-ocl.dev] MDT-OCL project organisation for add-ons (editor etc)

[ed@xxxxxxxxxxxxxxxxxx]

Hi All

We need to consider some awkward aspects of provision of the OCL editor
(and other significant new functionality such as perhaps code synthesis)
to MDT-OCL.

I think we have three options:

a) The MDT-OCL project is retitled "MDT-OCL (with optional Incubation
elements)" so that new code is added directly to MDT-OCL => MDT-OCL
incorporates incubation code and/or incubation dependencies.

b) New functionality X is added via an MDT-OCL-X (Incubation) project
which in due course is promoted to MDT-OCL-X => an ever increasing number
of MDT-OCL subprojects.

c) New functionality is added to a re-useable e.g. MDT-OCL Tools
(Incubation) project and then migrated once stable => plugins change
project.

My preference is for a) if the PMC endorse the (with optional Incubation
elements) project suffix, otherwise c).

Comments?

    Regards

        Ed Willink