Folks,
I’ve created
https://storyboard.openstack.org/#!/story/2002801 to track this.
Please provide any feedback you might have. We are targeting submission for July 16th.
Thanks,
Brent
From: Jones, Bruce E [mailto:bruce.e.jones@intel.com]
Sent: Tuesday, June 19, 2018 2:23 PM
To: Little, Scott <Scott.Little@windriver.com>; Jolliffe, Ian <Ian.Jolliffe@windriver.com>; Rowsell, Brent <Brent.Rowsell@windriver.com>;
CORDOBA MALIBRAN, ERICH <erich.cordoba.malibran@intel.com>;
starlingx-discuss@lists.starlingx.io
Cc: AMBARDEKAR, PRANJAL <pranjal.ambardekar@intel.com>
Subject: RE: [Starlingx-discuss] Repo consolidation
Cool. Can we see the document? Best way would be to create a Story and enter the contents into the Story so we can all see it.
brucej
From: Scott Little [mailto:scott.little@windriver.com]
Sent: Tuesday, June 19, 2018 7:40 AM
To: Jolliffe, Ian (Wind River) <ian.jolliffe@windriver.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Rowsell, Brent (Wind River) <brent.rowsell@windriver.com>;
Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>;
starlingx-discuss@lists.starlingx.io
Cc: Ambardekar, Pranjal <pranjal.ambardekar@intel.com>
Subject: Re: [Starlingx-discuss] Repo consolidation
Ok, I'll proceed with the reorg per Brent's 'Starlingx_setup_v3.xlxs' document.
I'll do the work piecewise, and leave relocating stx-gplv2/3 content till last. So there is still some time for discussion.
Scott
On 18-06-19 10:04 AM, Jolliffe, Ian wrote:
Hi Bruce;
Thanks for your flexibility – we will proceed with consolidation. The fewer repos the better, it will be one place to monitor and retire these changes. Maybe there are some ways to make the tool work for us – instead of the other way around. Let’s discuss on IRC.
Regards;
Ian
From: "Jones, Bruce E" <bruce.e.jones@intel.com>
Date: Monday, June 18, 2018 at 5:40 PM
To: Brent Rowsell <Brent.Rowsell@windriver.com>, "CORDOBA MALIBRAN, ERICH" <erich.cordoba.malibran@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 met with Pranjal and Abraham today to discuss this.
The problem is that we separated that code out for a reason. We have an internal requirement to run a license scanning tool, and the tool assumes that all of the code within a single git repo is covered by the same license. If you have files covered under multiple licenses, it reports errors.
It’s rather silly that we’re letting a tool dictate something like this.
We are setting up a process to run that tool on a regular basis, so when it comes time to do a release, we don’t run into issues that we didn’t already know about.
It would not be the end of the world if someone submitted and approved a PR to merge those repos. It would make mine, Abraham’s and Pranjal’s lives easier if we did not. If you think that this would make things better for everyone else, I would withdraw my objection.
Meanwhile, our goal is to get rid of those repos, long term.
Brucej
From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com]
Sent: Wednesday, June 13, 2018 12:00 PM
To: Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io
Cc: Ambardekar, Pranjal <pranjal.ambardekar@intel.com>
Subject: RE: [Starlingx-discuss] Repo consolidation
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