Miles,
in the scope section, we already have a statement regarding the accessibility of profiles via this repository. Bullet point 3 in the Scope section says:
3. To provide a central repository within the Eclipse MDT project to discover and install UML profile implementations.
However, I put the paragraph you suggested into the introduction in addition.
You wrote
> whether this is intended to be a hub for active development and outside contributor involvement or if it is instead a kind of clearing house for already created implementations
Given from what we discussed about this project in order to prepare the proposal, it is actually both. Some profiles have definitely to be developed from scratch and, in future, this can surely be done by contributors as well, although we are going to contribute a bunch of implementations when setting up the project. But at the same time, some already existing profiles (SysML and MARTE from Papyrus) will be cleaned up and henceforth hosted under the UML profiles repository.
Regarding maintenance, we stated in bullet point 2 of Scope section:
2. The project aims at maintaining each hosted profile’s lifecycle, so that an evolution of a profile within its standardizing authority (e.g. OMG) will be reflected as soon as possible within the repository to guarantee an up-to-date status of the provided profile implementation at any time
Since UML profiles usually evolve once a year and the EMF-based implementation usually not require that much maintenance or improvement (most stuff will be generated), we thought this should be sufficient.
So, any suggestion how to proceed with your latter statements?
Regards,
Marc-Florian
OK, and I'll assume that the UML2 team decided that it didn't make sense to expand the scope of UML2, because this seems to be fully enclosed WRT dependencies.
What I'd like to suggest is that the language of the proposal or resulting project page be sharpened up to say what you're saying here in direct language, e.g.
The proposed project provides implementations of "standard" UML profiles and a repository in/from which to discover/install them.
I'd also want to know a bit more about whether this is intended to be a hub for active development and outside contributor involvement or if it is instead a kind of clearing house for already created implementations, almost like Orbit or something. Either way is ok I guess, I just think that if it is the latter we might be a little more clear about the process and on-going maintenance so that consumers can rely on the profiles being created. Usually a project like this has a center of gravity, and it seems vague here, but perhaps that is unavoidable given the nature of the scope.
On 2012-05-14, at 10:11 AM, Kenn Hussey wrote:
The scope of the MDT UML2 project is not designed to include profile implementations; rather, it is about (just) the UML metamodel. The proposed project is about providing implementations of "standard" UML profiles and a repository in/from which to discover/install them.
Kenn
Is there some reason that this can't be managed under the existing UML2 project, esp. given that this seems to be a matter of collecting a repository rather than active development of functionality? To me the scope and intro seemed vague about what exactly the project's goals and provided technologies are, and as a naive Modeling project consumer, I'm left wondering what the point is. That is, what if anything is actually being engineered here?
On 2012-05-14, at 9:02 AM, Ed Merks wrote:
+1
On 14/05/2012 5:09 PM, Wendland, Marc-Florian wrote:
Dear PMC,
as one of the intended project leaders and on behalf of the involved members in that project proposal, I would like to request your approval for the Eclipse MDT UML2 Profiles proposal at
in order to proceed with submitting it to the Eclipse Management Organization (EMO).
Best Regards,
Marc-Florian Wendland
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
______________________________
Senior Engineer and Product Manager, Tasktop
Committer, Eclipse Mylyn and Virgo
Project Lead, Model Focussing Tools and AMP
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
______________________________
Senior Engineer and Product Manager, Tasktop
Committer, Eclipse Mylyn and Virgo
Project Lead, Model Focussing Tools and AMP
