<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle34
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Folks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">I’ve created <a href="https://storyboard.openstack.org/#!/story/2002801">
<span style="color:black">https://storyboard.openstack.org/#!/story/2002801</span></a> to track this.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Please provide any feedback you might have. We are targeting submission for July 16<sup>th</sup>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Brent <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Jones, Bruce E [<a href="mailto:bruce.e.jones@intel.com">mailto:bruce.e.jones@intel.com</a>]
<br>
<b>Sent:</b> Tuesday, June 19, 2018 2:23 PM<br>
<b>To:</b> Little, Scott <<a href="mailto:Scott.Little@windriver.com">Scott.Little@windriver.com</a>>; Jolliffe, Ian <<a href="mailto:Ian.Jolliffe@windriver.com">Ian.Jolliffe@windriver.com</a>>; Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com">Brent.Rowsell@windriver.com</a>>;
CORDOBA MALIBRAN, ERICH <<a href="mailto:erich.cordoba.malibran@intel.com">erich.cordoba.malibran@intel.com</a>>;
<a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> AMBARDEKAR, PRANJAL <<a href="mailto:pranjal.ambardekar@intel.com">pranjal.ambardekar@intel.com</a>><br>
<b>Subject:</b> RE: [Starlingx-discuss] Repo consolidation<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> brucej<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Scott Little [<a href="mailto:scott.little@windriver.com">mailto:scott.little@windriver.com</a>]
<br>
<b>Sent:</b> Tuesday, June 19, 2018 7:40 AM<br>
<b>To:</b> Jolliffe, Ian (Wind River) <<a href="mailto:ian.jolliffe@windriver.com">ian.jolliffe@windriver.com</a>>; Jones, Bruce E <<a href="mailto:bruce.e.jones@intel.com">bruce.e.jones@intel.com</a>>; Rowsell, Brent (Wind River) <<a href="mailto:brent.rowsell@windriver.com">brent.rowsell@windriver.com</a>>;
Cordoba Malibran, Erich <<a href="mailto:erich.cordoba.malibran@intel.com">erich.cordoba.malibran@intel.com</a>>;
<a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> Ambardekar, Pranjal <<a href="mailto:pranjal.ambardekar@intel.com">pranjal.ambardekar@intel.com</a>><br>
<b>Subject:</b> Re: [Starlingx-discuss] Repo consolidation<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Ok, I'll proceed with the reorg per Brent's 'Starlingx_setup_v3.xlxs' document.<br>
<br>
I'll do the work piecewise, and leave relocating stx-gplv2/3 content till last. So there is still some time for discussion.<br>
<br>
Scott<br>
<br>
<br>
On 18-06-19 10:04 AM, Jolliffe, Ian wrote:<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Bruce;<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regards;<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Ian<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">"Jones, Bruce E"
<a href="mailto:bruce.e.jones@intel.com"><bruce.e.jones@intel.com></a><br>
<b>Date: </b>Monday, June 18, 2018 at 5:40 PM<br>
<b>To: </b>Brent Rowsell <a href="mailto:Brent.Rowsell@windriver.com"><Brent.Rowsell@windriver.com></a>, "CORDOBA MALIBRAN, ERICH"
<a href="mailto:erich.cordoba.malibran@intel.com"><erich.cordoba.malibran@intel.com></a>,
<a href="mailto:starlingx-discuss@lists.starlingx.io">"starlingx-discuss@lists.starlingx.io"</a>
<a href="mailto:starlingx-discuss@lists.starlingx.io"><starlingx-discuss@lists.starlingx.io></a><br>
<b>Cc: </b>"AMBARDEKAR, PRANJAL" <a href="mailto:pranjal.ambardekar@intel.com"><pranjal.ambardekar@intel.com></a><br>
<b>Subject: </b>Re: [Starlingx-discuss] Repo consolidation</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><a name="_MailOriginalBody"><span style="color:#1F497D">I met with Pranjal and Abraham today to discuss this.</span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">It’s rather silly that we’re letting a tool dictate something like this.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Meanwhile, our goal is to get rid of those repos, long term.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> Brucej</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Rowsell, Brent [<a href="mailto:Brent.Rowsell@windriver.com">mailto:Brent.Rowsell@windriver.com</a>]
<br>
<b>Sent:</b> Wednesday, June 13, 2018 12:00 PM<br>
<b>To:</b> Cordoba Malibran, Erich <a href="mailto:erich.cordoba.malibran@intel.com">
<erich.cordoba.malibran@intel.com></a>; Jones, Bruce E <a href="mailto:bruce.e.jones@intel.com">
<bruce.e.jones@intel.com></a>; <a href="mailto:starlingx-discuss@lists.starlingx.io">
starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> Ambardekar, Pranjal <a href="mailto:pranjal.ambardekar@intel.com"><pranjal.ambardekar@intel.com></a><br>
<b>Subject:</b> RE: [Starlingx-discuss] Repo consolidation<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">The objective over time is to eliminate the changes to these open source packages by upstreaming the changes.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Given that, I don’t think we want the overhead of creating/managing 250 repos. This project already has 50 repos.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Currently we have these packages spread over 4 repos with no real functional division.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">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. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Brent </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</blockquote>
<p><o:p> </o:p></p>
</div>
</body>
</html>