Re: [ecf-dev] ECF project and Tycho

[Mat Booth <mat.booth@xxxxxxxxxx>]

----- Original Message -----
> From: "Scott Lewis" <slewis@xxxxxxxxxxxxx>
> To: ecf-dev@xxxxxxxxxxx
> Sent: Thursday, 6 November, 2014 9:01:23 PM
> Subject: Re: [ecf-dev] ECF project and Tycho
> 
> Hi Mat,
> 
> On 11/6/2014 4:10 AM, Mat Booth wrote:
> > <stuff deleted>
> > I would be happy to join the project as a committer.
> 
> That's wonderful!   Thanks for your commitment.   The committer addition
> process will take a little time for the following reasons:
> 
> 1) In order for the existing committers to vote for you as an ECF
> commiter, it will be necessary for us to get a little bit more familiar
> with your work, background, and interests WRT ECF.   There are multiple
> ways to handle this, and we can work with you to figure out what those
> ways are (e.g. perhaps working directly with Wim and/or Markus on Tycho,
> perhaps contributing in other ways to ECF, etc).  Let's figure out what
> will work for you, Wim and Markus. Also:  are you already a committer on
> some other EF project?  If so that will likely help somewhat
> particularly with the EF committer requirements.
> 
> 2) If you are not already a committer on some other project, you may
> have to work out some mechanics with Red Hat (your employer I assume).
> Here is the EF 'Becoming a Committer' page, in case you are not already
> familiar with it:
> http://www.eclipse.org/membership/become_a_member/committer.php
> 

I am already a committer on the Linux Tools project at the foundation, so that is one hurdle less :-)

Aside from my interest in Tycho/CBI, I am also keen that foundation projects move to the latest versions of their dependencies so that we benefit from any bug/security fixes they may provide. So for example, this bug about moving to the latest version of asm [1] interests me and I would be willing to spend time to keep the project using the latest versions of the Apache httpcomponents [2] (actually these have been the source of a few CVEs recently, so keeping this dependency up to date is important) and whatever else I notice is outdated.

[1] : https://bugs.eclipse.org/bugs/show_bug.cgi?id=430752
[2] : https://bugs.eclipse.org/bugs/show_bug.cgi?id=446103

> 
> >
> >> Another option (btw) is that you/Red Hat provide support for existing ECF
> >> committers. Again, this would make it much more reasonable for us to
> >> justify
> >> the committer time required to work on a Tycho-based build. Particularly
> >> given our involvement with OSGi EEG/Standards (R6 RS/RSA CT-compliant
> >> impl),
> >> as well as IoT (e.g. Wim's talk) this might be appealing to multiple parts
> >> of Red Hat. I'll leave with you, Aleksandar, to consider and/or propose
> >> something to Red Hat. Please let me know if you want more info, or to
> >> discuss.
> >>
> >> Wim and all: As project lead, my own requirements for any Tycho efforts by
> >> ECF committers are the following:
> >>
> >> 1) The existing build must not be destabilized or broken at any point
> > Of course. As mentioned in another mail, the risk of introducing Tycho is
> > very low and we can iterate on the implementation until the build outputs
> > are identical before switching over.
> 
> Yes, that's great.  I would suggest working off at least one branch.
> You can/should coordinate this with Wim Jongman and/or Markus Kuppe.
> 

Organising a branch to work from would be ideal. I don't mind making the initial contribution of a parent pom and poms for some subset of bundles such that you can successfully run a tycho build to completion and then we can expand the conversion from there. Does that sound like a good way to go?


> <stuff deleted>
> 
> >> 3) When/If the transition is done, some ECF committer(s) (you, Markus,
> >> Matt,
> >> multiple people, etc), be identified and resourced to maintain a
> >> Tycho-based
> >> build.
> >>
> > I can't speak for others, but if I were a committer on the project then
> > certainly I could justifiably commit a portion of my time to the ongoing
> > maintenance of the Tycho build.
> 
> Great, thanks.   Let's start a dialog about this among at least myself,
> you, Wim, and Markus K.   My desire here is to find a steady state
> (after the transition) that provides for the necessary maintenance
> resources...hopefully spread among >= 2 ECF committers (as we've been
> doing with ECF releng for some time).
> 
> Thanksinadvance for your commitment.
> 
> Scott
> 
> 
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>