[m2t-dev] Xpand OCL component proposal (code migration)

[Richard Gronback <richard.gronback@xxxxxxxxxxx>]

Hello,

As discussed on the last PMC call [1], we'd like to finally get the Xpand
variant out of GMF and into M2T where it belongs.  Given the current
migration of the current Xpand to an Xtext-based foundation, and given the
desire to continue using Xtend and underlying expression language by the
current Xpand team, we'd like to create a new 'Xpand OCL' component in M2T.

This version of Xpand will use OCL and QVTO for the query/expression
language, and include the enhancements made to Xpand for GMF's needs [2],
but which were never fully implemented in the original Xpand.  Also provided
will be a migration utility that converts the use of Xtend to OCL/QVTO.  The
initial committers for this component will be Artem Tikhomirov (lead) and
Alexander Shatalin (both GMF committers already).

Copying the GMF and M2T dev mailing lists to get approval for code
migration.

Copying the Modeling PMC to get PMC approval (obviously, my vote is +1).

Copying the EMO to serve as indication that the obligatory community
announcement needs to be made for this new component.  Actually, as it's not
really 'new' but just relocating, is this necessary?  It can't hurt, I
suppose.

Copying the IP team for confirmation to get clarification on what moving
code from one project to another will entail, from an IP perspective.
Anything?  A CQ for tracking purposes?  Maybe we could use a cartoon for
moving code between projects? ;)

Copying Bjorn as the "master of process" to help identify any complications
the newly approved development process changes may present in this move.  I
didn't see anything specifically on this under /dev_process, but suppose
this topic could be the first under the "I am a PMC Member..." on [3].

Thanks,
Rich

[1] http://wiki.eclipse.org/Modeling_PMC_Meeting%2C_2008-08-19
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=202813
[3] http://www.eclipse.org/projects/dev_process/index.php