<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 15, 2019 at 8:27 PM Arce Moreno, Abraham <<a href="mailto:abraham.arce.moreno@intel.com" target="_blank">abraham.arce.moreno@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> > Some people would love to see also a virtual showroom of StarlingX<br>
> > features, more below...<br>
<br>
> Sounds great, where did this discussion occur? I'd like to take part if I can,<br>
> though I am somewhat limited in N/A daytime meeting times.<br>
<br>
It was an informal team talk while we were planning some self-learning activities for the next months.<br>
We can arrange a sync up meeting If you want to get more into the specific details.<br></blockquote><div><br></div><div><div style="font-size:small" class="gmail_default">Ok cool. My suggestion is going to be that we setup a Special Interest Group (SIG) around the <a href="http://packet.com" target="_blank">packet.com</a> work. This SIG would exist for a short time and we would funnel all the related <a href="http://packet.com" target="_blank">packet.com</a> work through it for the time being, at least in term of what resources are being used and how. Then, once we felt everything was well understood in terms of how we organize and use the <a href="http://packet.com" target="_blank">packet.com</a> infrastructure we would disband it and work would continue as normal in the teams that are using the infrastructure. I'll mention this at the community and TSC meetings this week.<br></div><div style="font-size:small" class="gmail_default"> </div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> > We can start easily right away, deploying the demos that you guys have<br>
> > presented in the past conferences, and for every demo / workload / whatever<br>
> > you want to call it, we must have generate a:<br>
> > <br>
> > - Reference Architecture<br>
> > - Solution Brief<br>
> > - Application Note<br>
<br>
> Where does these requirements come from?<br>
<br>
At Intel, we use the above artifacts when we do customer enablement and they are the core of our solutions libraries. Not a specific requirement from anyone but our proposal for ways to teach, give a working solution base or simply create awareness on StarlingX. Let us know how do we proceed with this proposal.<br>
</blockquote></div><div><br></div><div>I<span class="gmail_default" style="font-size:small"> think we would just want to make sure that whatever artifacts we generate are valuable to the community and we shouldn't just bring in an existing process if it doesn't match up with community requirements, though, of course, it might end up being exactly what we want. I mean I think I can understand what a reference architecture is, but I have no context for what an application note is. :)<br></span></div><div><span class="gmail_default" style="font-size:small"></span><div style="font-size:small" class="gmail_default">Thanks,</div><div style="font-size:small" class="gmail_default">Curtis</div><br></div></div>