Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [modeling-pmc] [cross-project-issues-dev] Projects that have not (AFAICT) declared participation in Oxygen

I've created review records and tracking bugs.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=509485

https://bugs.eclipse.org/bugs/show_bug.cgi?id=509487

For the second bug report, I need a list of committers for the new "EMF Services" project. Also, feel free to weigh in on any other aspect of the new project (e.g. the name).

Most of the work in these exercises will be done by EF staff. I believe that, for the most-part everything (e.g. Git repos, downloads) will stay in place with just new UNIX group assignments. I am a little concerned that we may break the builds, so I'll need somebody to step forward to take responsibility to test/fix issues like that.

I've given us a month to get everything together (I've set the end of the review period to Jan 18). I'm a bit concerned that if we break the build in the process of transitioning, we'll put Oxygen M5 at risk. We'll have to sort out timing for implementing the actual changes to mitigate that risk.

Thanks,

Wayne

On 16/12/16 04:08 AM, Cédric Brun wrote:
Sounds good to me.


Le 15/12/2016 à 21:03, Wayne Beaton a écrit :

If we have agreement, I'll start the tracking of two restructuring reviews:

  • Merge GMF Notation into GMF Runtime. This will transfer all resources and terminate GMF Notation.
  • Create a new "EMF Services" project. This will transfer all resources and terminate EMF Query, Transaction, and Validation

For each of these, I'll a definitive list of committers and things that need to change. Git repos are all already in the right place, and I'm pretty sure that none of these projects have their own website. The Hudson builds are probably fine if we just change the ownership to the new project (I'll have to check with Webmaster about whether or not we have to change the HIPP instances). The GMF Notation build seems broken. IMHO, downloads are fine right where they are.

While we will be creating a new project, we're creating it entirely from existing sources and preserving existing scope so I do not feel that a creation review is necessary. This change is entirely structural.

I'll plan to set this up tomorrow with the intention of running the actual review early in the new year.

While I don't like overloading things, I may try to use this as an opportunity to further the "flattening" exercise we started many years ago and make these new projects direct Modeling subclasses.

Any concerns?


Wayne

On 15/12/16 12:23 PM, Michael Golubev wrote:
Hello

I would like to confirm that GMF Tooling is about to be withdrawn from the train in any case, independently on the future merger of the GMF Runtime and Notation and any EMFqtv projects. 

There are some bits in the "GMF Tooling Runtime" component which may provide runtime dependencies for other train projects. 
But even if it is the case:
a) the current bits which are in the repository since Mars / Neon should be enough, 
b) if needed, this small parts may be later moved from GMF Tooling into the GMF Runtime since they logically belong there. 

I would be happy to discuss this later with the lead of the merged GMF project, but for now I would not consider GMF Tooling as a participant for the merger. 

Regards, 
Michael 


-- 

Michael "Borlander" Golubev
Eclipse Committer (GMF Tooling)
at Montages Think Tank, Prague, Czech Republic
1165/1 Dvorecka, 14700, Prague-4 Podoli

tek: +420 602 483 463

On Thu, Dec 15, 2016 at 6:00 PM, Cédric Brun <cedric.brun@xxxxxxx> wrote:
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
Eclipse Converge


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
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@eclipse.org
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 Eclipse Converge
_______________________________________________
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

_______________________________________________ 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 
_______________________________________________
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
-- Wayne Beaton @waynebeaton The Eclipse Foundation Eclipse Converge
_______________________________________________
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

_______________________________________________
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
-- Wayne Beaton @waynebeaton The Eclipse Foundation Eclipse Converge

Back to the top