The GMF restructure is mainly a reaction to the Graphiti project proposal. The original version of the proposal was to start a new modeling project.
The scope, architecture and dependencies of Graphiti align directly with the GMF Runtime. Given this fact, it did not make a lot of sense to create a second community. The Graphiti project belongs in the same umbrella project as GMF.
To this end, we proposed the creation of the new Graphical Modeling Project that includes the existing GMF project and will include Graphiti.
A restructure of GMF also solves the following:
- GMF is currently restricted to one runtime and one tooling project.
- It makes sense in terms of our project scope to allow multiple runtimes and multiple tooling projects.
- Expand the Graphical Modeling community at Eclipse
- GMF can only have one project lead, even though since day one there was a project and committer split between GMF Tooling and GMF Runtime components.
- It makes sense to split the project between GMF Tooling and GMF Runtime.
- We will have leadership and committers for each subproject.
- It will fit into the existing model of umbrella projects in modeling such as EMF, MDT, M2M, etc.
- Easier defect management, release management, etc.
- Expand the community working in graphical modeling.
- Clients have requested a separate notational metamodel.
- Notational metamodel is aligned with the OMG diagram exchange specifications.
- GMF Runtime has separate features that deliver the notational metamodel, but end users have to extract manually.
- Makes sense to create a separate GMF Notation sub-component so other projects can reuse without requiring all of the GMF Runtime
- GMF Tooling
- GMF Runtime
- GMF Notation
We are now starting the actual restructure. The ongoing work will be discussed in Graphical Modeling Framework (GMF) Restructuring if you wish to follow along.
As well, Graphiti's Creation Review is potentially scheduled for Wed, 28 Apr 2010 at 1500 UTC