Wayne,
Comments below.
On 28/11/2012 8:29 PM, Wayne Beaton
wrote:
Comments in line.
On 11/28/2012 01:42 PM, Philipp W. Kutter | Montages AG wrote:
I
would like to note that UML2 Tools is not terminated!!
Not yet anyway.
But very soon.
The UML2 Tools project is moved into GMF Tooling as a
subproject.
That's not what the review requested.
Yes.
The review document states that "The project is a subproject of
the to-be-terminated MDT project. Its contents will be migrated as
samples for the GMF project."
Having said that, I'm more inclined to do whatever the right thing
is (in contrast to following the letter of the review document).
This is exactly what I'm expecting to happen. They're simply
samples not a useable tooling. So the project is to be terminate
and the code is to be migrated as a GMF Tools sample.
Focus of the UML2 Tools project is now:
- demonstrate what can be generated with GMF Tooling 3.0 for the
UML2 Metamodels of all UML2 diagram types.
- test advanced features from Papyrus, that are backported to
GMF Tooling.
- validate new GMF Tooling features before they are used in
Papyrus and other projects using GMF Tooling.
People working on generating UML2 like diagram editors for UML2
like metamodels are welcome to contribute to the GMF Tooling
subproject UML2 Tools" and become committers.
Do you really mean subproject, or is the UML2 Tools code more
appropriate as example code within GMF Tooling? Do you, for
example, anticipate that the two code bases will have different
sets of committers? Is there value in maintaining a separate web
presence for two separate projects? Will there be separate builds?
Or is it just two separate Git repositories owned by the one (GMF
Tooling) project?
I don't see that it needs to be two separate repositories.
If the UML2 Tools code is really just an aspect of the GMF Tooling
code, then I recommend that we stick with the letter of the review
and go ahead with just moving the code from UML2 Tools into GMF
Tooling, and retire the UML2 Tools project.
Yes, please do.
People looking for full featured UML2 Tooling should look at
Papyrus.
This seems to reinforce my opinion that UML2 Tools code is just an
aspect/part of GMF Tooling and should not be a project in its own
right.
Exactly.
I CC the component leads, if they want to add details.
Regards,
Philipp
On 28.11.2012 18:00, modeling-pmc-request@xxxxxxxxxxx
wrote:
From: Wayne Beaton <wayne@xxxxxxxxxxx>
To: "'PMC members mailing list'" <modeling-pmc@xxxxxxxxxxx>,
Date: 2012/11/27 01:11 PM"
Subject: [modeling-pmc] Modeling projects in CVS
Sent by: modeling-pmc-bounces@xxxxxxxxxxx
...
Some of the projects on this list are scheduled for
termination (UML2
Tools and UMLX) and so will be taken care of naturally.
...
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
|
