|
Hi,
Two projects would work also as long as we have the same team
being able to maintain both. "Non-tech" work would still be low
enough that we are willing to do it.
EMF Services or EMF Conformity/Consistency (I remember this name
was used at some point years ago) would work for EMF Query,
Validation, and Transaction, If anybody uses Query then let's keep
it around (again, that's 5K lines of codes and not a problem to
build and ship)
GMF Runtime+Notation are definitely candidates to merge in a
single "GMF Runtime" project (this split has always been a bit
weird to me anyway as the runtime is tightly coupled with
notation) but GMF Tools is a completely different matter depending
on many more technologies (it might have changed but last time I
checked QVT-O, an Xpand flavor...).Take the responsability of GMF
Tooling is not an option for Obeo but if GMF runtime is taken care
of Michael might be in a position where he can still take care of
GMF Tooling.
Cédric
Le 15/12/2016 à 17:25, Wayne Beaton a écrit :
Thanks Cédric.
I've made cross-project-issues-dev BCC (though I'm not entirely
sure that this will work as I expect) and have moved this
discussion to the Modeling PMC's mailing list. At this point,
cross-project-issues-dev knows the issues and if anybody wants
to join in the conversation, they can join us on the PMC list.
We'll circle back when we've made a decision.
I believe that this resolves the participation "opt-in"
requirements for Oxygen. We'll have to wait to update the
participation list [1] until after we have the restructuring
resolved.
I'd like to recommend that we move forward with two projects:
one for the GMF pieces, and one for the EMF pieces. My sense is
that these are really separate things and I don't like the idea
of a "mixed bag of stable stuff" project. Though, I could be
convinced otherwise.
Does it make sense to merge GMF Runtime/Notation/Tooling into a
single "GMF" project?
IMHO, EMF Query certainly needs to either be part of a merged
project or retired. I'm open to other options. What would we
call the merged project? "EMF Services"? "EMF Query, Validation,
and Transaction"? (we need to be careful to make sure that this
is not confused with QVT Operational)
Wayne
[1] http://projects.eclipse.org/releases/oxygen
On 15/12/16 08:00 AM, Cédric Brun
wrote:
Hi,
We are currently looking for future proof solutions to secure
EMF Transaction, Validation, GMF Notation and GMF Runtime as
part of the release train.
Wayne, you told us that we could envision a solution where
administrative burden is kept to a minimum by merging those
projects, I rolled with this idea and then reached out to the
GMF runtime team (Aurelien Pupier, Vikas Chandra) which is OK
for proceeding to such a merge and to become commiters in this
"merged project.” Pierre-Charles is willing to lead the
project, Michael Golubev is also willing to give a hand at
least during Oxygen + SRs cycle. This project could also
include EMF Query if anybody consume it as this is very very
small and has virtually no specific dependency.
That would be a project with at least four people from
different organization in the position to maintain it. The
objectives are: meeting the release train requirements,
keeping the artifacts separately consumable and the occasional
bug fix.
From a pure technical perspective these contributions are
already in the repository and meeting the expected
constraints, Wayne: is that good enough as a declaration of
intent to participate in Oxygen for those projects?
Cheers,
Cédric
Le 14/12/2016 à 21:07, Wayne Beaton a écrit :
According to my records, the following projects have not yet
declared their intent to participate in our Oxygen
Simultaneous Release. The deadline to state your intention
to participate is this Friday, December 16/2016.
If your project is listed below, please take immediate steps
to declare your intent to participate. The process is
described in the Planning Council's documentation [1] and in
the Eclipse Committer Handbook [2]. If you really are planning
to drop out of the simultaneous release, please also let us
know.
- Xpand
- Thym
- Maven Integration for Web Tools Platform
- Lua Development Tools (LDT)
- Subversive - SVN Team Provider
- Eclipse Paho
- Andmore - Eclipse Android Tooling
- Accessibility Tools Framework
- Java Workflow Tooling
- Eclipse Gyrex Project
- ATL - A Model Transformation Technology
- Data Tools Platform
- Graphical Modeling Framework (GMF) Tooling
- Graphical Modeling Framework (GMF) Notation
- Graphical Modeling Framework (GMF) Runtime
- EMF Transaction
- EMF Validation
- EMF Query
If a project that you depend on is
on this list, please make that concern known as well. I know
that we have some staffing challenges on a handful of these,
so it will be valuable to know who cares about something
that is missing.
Note that I did add EMF Validation and Query to the list
based on the description in the release records. AFAICT, the
project teams have not formally declared.
I've updated the dates on the wiki page [3]
- December 16/2016 - Opt-in deadline
- February 17/2017 - CQ Submission deadline (specify
that the CQ is required for Oxygen)
- May 24/2017 - IP Log submission deadline
- May 31/2017 - Review materials due
- June 7/2017 - First round of release reviews (aim for
this date if you can)
- June 21/2017 - Second (final?) round of release
reviews
- June 28/2017 - Eclipse Oxygen GA
Please pay special attention to the CQ deadline to give the
IP Team a fighting chance of getting all the required CQs
processed. If you know that you're going to be coming in
late with some third-party dependencies, please contact emo-ip-team@xxxxxxxxxxx
to let them know.
Thanks,
Wayne
[1] https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
[2] https://www.eclipse.org/projects/handbook/#pmi-joining-a-simultaneous-release
[3] https://wiki.eclipse.org/Category:Oxygen
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Cédric
Brun
CTO
+33 2 51 13 51 42
@bruncedric
7 Boulevard Ampère - Carquefou
- France
obeo.fr
| twitter | linkedin
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
--
Cédric
Brun
CTO
+33
2 51 13 51 42
@bruncedric
7 Boulevard Ampère - Carquefou -
France
obeo.fr | twitter | linkedin
|
