|
Hi
Quentin
I'm not clear
what you mean by 'implement'.
If you are going
to start again from the QVT specification, you have about 25 bugs to fix and
EMOF-based serialization to support.
If you are going
to create a copy of a substantial body of code, then I think there may be some
Eclipse ethics issues to resolve.
Regards
Ed Willink
Hi all,
As I have not seen any incoming
submission, I shall implement the Declarative QVT metamodels for the M2M
component.
We are now working to get the best balance between functionality
and standardization. We are exploring the possibilities of model decoration to
fulfil it.
Ed, if you change your mind, let us
know!
Regards,
Quentin Glineur
Quentin Glineur a
écrit :
Hi Ed,
I repeat
myself:
For the Declarative QVT component, we could just accept your
declarative EQVT metamodels submitted through a patch.
I do not in
intend to "deprive" anybody of anything.
Declarative QVT is a component
with its objectives that we are trying to fulfil: This could be done by
*our* integration of your work.
Then we could work together... heading
toward a committer status vote.
Regards,
Quentin Glineur
Ed Willink a écrit :
Hi Fredieric, Quentin
Quentin properly summarized the new committer policy.
I am glad that we now have a clean solution for the contribution of
your QVT work into M2M.
Thanks to you, we are making significant progress.
I'm afraid you do not seem to understand what we are discussing.
QVTR has requested use of the UMLX models. In order to make these more
sensibly available I have suggested making them available within M2M.
The models have been developed as part of the GMT project, for which
I have been a GMT committer for perhaps 5 years, rather longer than
nearly all M2M committers. The models are work in progress, so there
is no way I can be expected to deprive myself of update access.
The code is being transferred not contributed. The code comes with a
committer to maintain it. This is partly why I wanted to contribute
the models to the empty M2M infrastructure component; I have no desire to
take on responsibilities of committer for EMF and OCL and QVTR and QVTOM.
and conversely I certainly should not be an EMF or OCL committer.
If the code is to be partitioned between just QVTR and QVTOM then I
'only' need QVTR and QVTOM committer access. [I would still prefer to
put them all in M2M infrastructure.]
Regards
Ed Willink
_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev
_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev
|
