Wayne, maybe the time has come indeed. The incubation status did not prevent the technology of the project from being used even in commercial products, but I understand that this is starting to be a bit “off process”. Plus, the core APIs have been stable for quite a long time.
However, I believe that a restructuring is needed before, or at the same time as, a graduation so that the state of the project is accurately reflected.
The initial scope of the project was about a merge engine for EMF models [1]. It evolved naturally to encompass features that highly depend on consistent model merging: model patches, modeling patterns, offline model synchronization. In parallel, it turned out to be useful outside the EMF world so it started to be used on structured non-EMF data thanks to a few adaptations.
I believe these evolutions brought the project closer to a “natural scope” that was difficult to foresee initially. However, a consequence is that both the name of the project and the content of the project proposal look deprecated w.r.t. what the project has become. I think both should be updated. I solicited the opinion of contributors and consumers of the project some time ago and they seem to rather approve that. This is of course not to be taken lightly given the likely cost of a renaming.
I suppose I should open a bug to discuss that.
Olivier
[1] https://www.eclipse.org/proposals/modeling.emf.edm/
De : cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] De la part de Wayne Beaton
Envoyé : jeudi 14 décembre 2017 23:09
À : Cross project issues
Objet : Re: [cross-project-issues-dev] EMF Diff/Merge participation in Photon
It's been five years since your first release. Time to graduate soon?
--
Wayne Beaton
Director of Open Source Projects