The objective over time is to eliminate the changes to these open source packages by upstreaming the changes.

Given that, I don’t think we want the overhead of creating/managing 250 repos. This project already has 50 repos.

Currently we have these packages spread over 4 repos with no real functional division.

I am proposing it would make more sense to consolidate into one.  One repo to manage, making it easier to track the retirement of customizations over time.  

 

Brent

 

From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com]
Sent: Wednesday, June 13, 2018 2:43 PM
To: Rowsell, Brent <Brent.Rowsell@windriver.com>; JONES, BRUCE <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io
Cc: AMBARDEKAR, PRANJAL <pranjal.ambardekar@intel.com>
Subject: Re: [Starlingx-discuss] Repo consolidation

 

This was a convenience separation. The license checking tool expects to have a repository per project and a main license defined for the entire repository. In this case, we wanted to release the project as Apache License 2.0 and the tool assumes that all the code inside the repository should has friendly licenses. However, the tool found some conflicting components and to solve the issue we move out those into the gplv2/3 repositories.

 

This doesn’t mean that were actual license conflicts, it means that this use case was outside of the scope of the tool.

 

I would like to discuss the advantage of consolidation vs split, I’m wondering if a model like CentOS has could help us, they have a repository for each component. This will lead us to have around 250 repositories (CentOS manages around 600) but I think that managing each of them would be more easy.

 

-Erich

 

From: "Rowsell, Brent" <Brent.Rowsell@windriver.com>
Date: Wednesday, June 13, 2018 at 12:48 PM
To: "Jones, Bruce E" <bruce.e.jones@intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>
Cc: "Ambardekar, Pranjal" <pranjal.ambardekar@intel.com>
Subject: Re: [Starlingx-discuss] Repo consolidation

 

I don’t understand the distinction. There is already gpl code in stx_integ.

 

Brent

 

From: Jones, Bruce E [mailto:bruce.e.jones@intel.com]
Sent: Wednesday, June 13, 2018 1:29 PM
To: Rowsell, Brent <Brent.Rowsell@windriver.com>; starlingx-discuss@lists.starlingx.io
Cc: AMBARDEKAR, PRANJAL <pranjal.ambardekar@intel.com>
Subject: RE: [Starlingx-discuss] Repo consolidation

 

Objection.  We separated those out to comply with software license checking tools that we will still need to run.

 

Pranjal and Abraham are the subject matter experts here.  If there is a way to pass the code scanning tools and still combine these, I would not object at all.

 

      brucej            

 

From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com]
Sent: Wednesday, June 13, 2018 10:22 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Repo consolidation

 

I would like to propose that the following repo’s be consolidated under stx-integ.

 

 

Any objections/comments ?

 

Brent