Re: [che-dev] che-lib repo metadata - second request

[Sergii Kabashniuk <skabashn@xxxxxxxxxx>]

Can you fix merging conflicts? Plz.

On Mon, Aug 20, 2018 at 7:46 PM Nick Boldt <nboldt@xxxxxxxxxx> wrote:

Thanks to everyone who's already filled in information in the spreadsheet linked below [2] about che-lib [1]. I now know who to ask for help if I run into more problems building this stuff.

There are still a few items without owners. Could you have a quick look and fill in some names/URLs?

[1] https://github.com/eclipse/che-lib

[2] https://docs.google.com/spreadsheets/u/1/d/187SJjeyi2wL8ViZ3TJZc_MBuu1IEo_4cBQfLtkNSU4M/edit?usp=drive_web&ouid=112863742817366497518

Note that I've managed to get che-lib to build in Project Newcastle (NCL) server, but it takes over 90 mins! So reducing dependency on these not-quite-the-same-as-upstream artifacts would make it easier to productize Che. But at least for now I can proceed w/ trying to build Che server itself, so we can get that into a container. 

Thanks in advance,

Nick

From: Nick Boldt <nboldt@xxxxxxxxxx>
To: che-dev@xxxxxxxxxxx
Cc: Roman Iuvshyn <riuvshyn@xxxxxxxxxx>, Sergii Kabashniuk <skabashn@xxxxxxxxxx>, Florent Benoit <fbenoit@xxxxxxxxxx>, Oleksandr Andriienko <oandriie@xxxxxxxxxx>, Valerii Svydenko <vsvydenk@xxxxxxxxxx>, Yevhen Vydolob <yvydolob@xxxxxxxxxx>, Mykhailo Kuznietsov <mkuznets@xxxxxxxxxx>, Oleksandr Garagatyi <ogaragat@xxxxxxxxxx>, Vitalii Parfonov <vparfono@xxxxxxxxxx>
Bcc: 
Date: Wed, 1 Aug 2018 10:18:44 -0400
Subject: Request for information: che-lib forks and patches -- why do we need these?

In order to streamline the process for building and productizing Che, I'd like to gather some information about the che-lib [1] bundles on which Che depends.

Here's a spreadsheet [2] I've started where we can collect that information.

If you're a committer on che-lib, or have contributed in the past, please help me collect this information so I can use it to get exceptions from Prod Sec w.r.t. Brew build processes and explain to them why we can't simply use upstream versions of these dependencies (eg., those already in Fedora or RHEL). 

[1] https://github.com/eclipse/che-lib

[2] https://docs.google.com/spreadsheets/u/1/d/187SJjeyi2wL8ViZ3TJZc_MBuu1IEo_4cBQfLtkNSU4M/edit?usp=drive_web&ouid=112863742817366497518

Спасибі!

-- 

Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED.

@ @redhatnews      Red Hat

“The Only Thing That Is Constant Is Change” - Heraclitus

--

Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED.

@ @redhatnews      Red Hat

“The Only Thing That Is Constant Is Change” - Heraclitus

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

--

Sergii Kabashniuk

Principal Software Engineer, DevTools 

Red Hat Ukraine

skabashniuk@xxxxxxxxxx