<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I'd like to leave it to Brent to share
any documents. What I have is a draft and might not reflect the
final intent. Likewise for creating a story, I'd prefer that to
our architect team.<br>
<br>
<br>
On 18-06-19 02:22 PM, Jones, Bruce E wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9A85D2917C58154C960D95352B22818BAB54A367@fmsmsx117.amr.corp.intel.com">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
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:windowtext;}
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.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;
color:black;}
span.EmailStyle31
{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;}
/* List Definitions */
@list l0
{mso-list-id:810974635;
mso-list-type:hybrid;
mso-list-template-ids:-1214185732 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1793743532;
mso-list-template-ids:-1527325622;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<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"
moz-do-not-send="true"></a><b><span
style="color:windowtext">From:</span></b><span
style="color:windowtext"> Scott Little
[<a class="moz-txt-link-freetext" 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 class="moz-txt-link-rfc2396E" href="mailto:ian.jolliffe@windriver.com"><ian.jolliffe@windriver.com></a>; Jones, Bruce E
<a class="moz-txt-link-rfc2396E" href="mailto:bruce.e.jones@intel.com"><bruce.e.jones@intel.com></a>; Rowsell, Brent (Wind
River) <a class="moz-txt-link-rfc2396E" href="mailto:brent.rowsell@windriver.com"><brent.rowsell@windriver.com></a>; Cordoba
Malibran, Erich
<a class="moz-txt-link-rfc2396E" href="mailto:erich.cordoba.malibran@intel.com"><erich.cordoba.malibran@intel.com></a>;
<a class="moz-txt-link-abbreviated" href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> Ambardekar, Pranjal
<a class="moz-txt-link-rfc2396E" 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"
moz-do-not-send="true"><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"
moz-do-not-send="true"><Brent.Rowsell@windriver.com></a>,
"CORDOBA MALIBRAN, ERICH"
<a href="mailto:erich.cordoba.malibran@intel.com"
moz-do-not-send="true"><erich.cordoba.malibran@intel.com></a>,
<a href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true">"starlingx-discuss@lists.starlingx.io"</a>
<a href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true"><starlingx-discuss@lists.starlingx.io></a><br>
<b>Cc: </b>"AMBARDEKAR, PRANJAL" <a
href="mailto:pranjal.ambardekar@intel.com"
moz-do-not-send="true"><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"
moz-do-not-send="true"><span style="color:#1F497D">I met
with Pranjal and Abraham today to discuss this.</span><o:p></o:p></a></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"
moz-do-not-send="true">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"
moz-do-not-send="true">
<erich.cordoba.malibran@intel.com></a>; Jones,
Bruce E <a href="mailto:bruce.e.jones@intel.com"
moz-do-not-send="true">
<bruce.e.jones@intel.com></a>; <a
href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true">
starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> Ambardekar, Pranjal <a
href="mailto:pranjal.ambardekar@intel.com"
moz-do-not-send="true"><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>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Cordoba Malibran, Erich
[<a href="mailto:erich.cordoba.malibran@intel.com"
moz-do-not-send="true">mailto:erich.cordoba.malibran@intel.com</a>]
<br>
<b>Sent:</b> Wednesday, June 13, 2018 2:43 PM<br>
<b>To:</b> Rowsell, Brent <<a
href="mailto:Brent.Rowsell@windriver.com"
moz-do-not-send="true">Brent.Rowsell@windriver.com</a>>;
JONES, BRUCE <<a
href="mailto:bruce.e.jones@intel.com"
moz-do-not-send="true">bruce.e.jones@intel.com</a>>;
<a href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true">starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> AMBARDEKAR, PRANJAL <<a
href="mailto:pranjal.ambardekar@intel.com"
moz-do-not-send="true">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">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">This doesn’t mean that were actual
license conflicts, it means that this use case was outside
of the scope of the tool.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-Erich<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">"Rowsell,
Brent" <</span><a
href="mailto:Brent.Rowsell@windriver.com"
moz-do-not-send="true"><span style="font-size:12.0pt">Brent.Rowsell@windriver.com</span></a><span
style="font-size:12.0pt">><br>
<b>Date: </b>Wednesday, June 13, 2018 at 12:48 PM<br>
<b>To: </b>"Jones, Bruce E" <</span><a
href="mailto:bruce.e.jones@intel.com"
moz-do-not-send="true"><span style="font-size:12.0pt">bruce.e.jones@intel.com</span></a><span
style="font-size:12.0pt">>, "</span><a
href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true"><span style="font-size:12.0pt">starlingx-discuss@lists.starlingx.io</span></a><span
style="font-size:12.0pt">" <</span><a
href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true"><span style="font-size:12.0pt">starlingx-discuss@lists.starlingx.io</span></a><span
style="font-size:12.0pt">><br>
<b>Cc: </b>"Ambardekar, Pranjal" <</span><a
href="mailto:pranjal.ambardekar@intel.com"
moz-do-not-send="true"><span style="font-size:12.0pt">pranjal.ambardekar@intel.com</span></a><span
style="font-size:12.0pt">><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"><span style="color:#1F497D">I don’t
understand the distinction. There is already gpl code in
stx_integ.</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>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jones, Bruce E [<a
href="mailto:bruce.e.jones@intel.com"
moz-do-not-send="true">mailto:bruce.e.jones@intel.com</a>]
<br>
<b>Sent:</b> Wednesday, June 13, 2018 1:29 PM<br>
<b>To:</b> Rowsell, Brent <<a
href="mailto:Brent.Rowsell@windriver.com"
moz-do-not-send="true">Brent.Rowsell@windriver.com</a>>;
<a href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true">starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> AMBARDEKAR, PRANJAL <<a
href="mailto:pranjal.ambardekar@intel.com"
moz-do-not-send="true">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">Objection.
We separated those out to comply with software license
checking tools that we will still need to run.</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">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.</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"
moz-do-not-send="true">mailto:Brent.Rowsell@windriver.com</a>]
<br>
<b>Sent:</b> Wednesday, June 13, 2018 10:22 AM<br>
<b>To:</b> <a
href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true">starlingx-discuss@lists.starlingx.io</a><br>
<b>Subject:</b> [Starlingx-discuss] Repo consolidation<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I would like to propose that the
following repo’s be consolidated under stx-integ.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">stx-gplv2<o:p></o:p></li>
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">stx-gplv3<o:p></o:p></li>
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">stx-upstream<o:p></o:p></li>
</ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Any objections/comments ? <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Brent <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Starlingx-discuss mailing list<o:p></o:p></pre>
<pre><a href="mailto:Starlingx-discuss@lists.starlingx.io" moz-do-not-send="true">Starlingx-discuss@lists.starlingx.io</a><o:p></o:p></pre>
<pre><a href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss" moz-do-not-send="true">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a><o:p></o:p></pre>
</blockquote>
<p><o:p> </o:p></p>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>