Bug 380978 - How we can get GMF Tooling back to Modeling package
Summary: How we can get GMF Tooling back to Modeling package
Status: NEW
Alias: None
Product: EPP
Classification: Technology
Component: modeling-package (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: 1.4.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-29 20:26 EDT by Michael Golubev CLA
Modified: 2013-10-02 09:45 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Golubev CLA 2012-05-29 20:26:00 EDT
Last year GMF Tooling missed the Indigo and had been removed from Modeling EPP. 

Also, QVTo (one of GMFT dependencies) was part of Indigo release, it had been also dropped from Modeling package for Indigo. All other (transient) GMFT dependencies were there. 

Both GMFT and QVTo are part of the Juno now, and after a some pause between the buids QVTo had been finally built its RC1 a week ago. 

GMFT also has its own RC1 build (and now testing RC2) for Juno. 

Also GMFT is discoverable through the amalgamation discovery, we would like to get back to the package. 

Cedric, can you please clarify what is required from us to get there? 

Regards, 
Michael
Comment 1 Markus Knauer CLA 2012-06-05 10:49:20 EDT
Cedric, any updates here?
Comment 2 Cedric Brun CLA 2012-06-05 11:21:26 EDT
Hi Michael,


The principles are documented here : http://wiki.eclipse.org/ModelingAmalgam#Eclipse_Modeling_Package


In a nutshell : """
To be part of the base platform a component should fulfill the following requirements :

a low UI profile
small (including non-packaged dependencies)
being a complementary framework to EMF or a tool with a fairly small focus.
being already adopted by the community at large
part of the simultaneous release and fulfilling all the release train requirements
not being in incubation (NEW INDIGO)
"""

Regarding GMF Tools my main concern would be adding a bunch of dependencies (QVTo, Xpand ?) making the package bigger (we're already 270MB)

Furthermore if we includes GMF Tools and QVTo, why not Graphiti and ATL ? So far we did quite a good job keeping the package neutral though useful enough for EMF and Ecore users. Technologies are easily accessible  through the discovery mechanism, I really don't want to ends up with a 300MB package, download figures showed that the choice I made so far : sliming it down and enabling the discovery, are leading to more adoption of the package.


That said I'm open to suggestion enabling us to get more feedback from the community so that I can decide to include this or that component based on this feedback. Maybe something similar to the survey I conducted a few years ago (http://model-driven-blogging.blogspot.fr/2010/06/modeling-survey-results.html)

Anyway it would be an impacting change which can't be done in the RC's phase, integration issues for Juno were quite a challenge with the content we have so far.
Comment 3 Cedric Brun CLA 2013-10-02 09:45:03 EDT
I just started a new survey for Luna : 

http://model-driven-blogging.blogspot.fr/2013/10/eclipse-modeling-package-road-to-luna.html