<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 18, 2016 at 11:45 AM, Philip Balister <span dir="ltr"><<a href="mailto:philip@balister.org" target="_blank">philip@balister.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb adM"><div class="h5">On 10/18/2016 02:20 PM, Otavio Salvador wrote:<br>
> On Tue, Oct 18, 2016 at 4:12 PM, Mark Hatle <<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a>> wrote:<br>
>> On 10/18/16 12:54 PM, Christopher Larson wrote:<br>
>>><br>
>>> On Tue, Oct 18, 2016 at 10:45 AM, Otavio Salvador<br>
>>> <<a href="mailto:otavio.salvador@ossystems.com.br">otavio.salvador@ossystems.<wbr>com.br</a> <mailto:<a href="mailto:otavio.salvador@ossystems.com.br">otavio.salvador@<wbr>ossystems.com.br</a>>> wrote:<br>
>>><br>
>>> On Tue, Oct 18, 2016 at 3:32 PM, Mark Hatle <<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a><br>
>>> <mailto:<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.<wbr>com</a>>> wrote:<br>
>>> > On 10/18/16 1:42 AM, Samuel Stirtzel wrote:<br>
>>> >> 2016-10-18 4:22 GMT+02:00 Mark Hatle <<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a><br>
>>> <mailto:<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.<wbr>com</a>>>:<br>
>>> >>> On 10/17/16 7:06 PM, akuster808 wrote:<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> On 10/17/2016 04:22 PM, Mark Hatle wrote:<br>
>>> >>>>> At OEDEM I presented the setup program I've been working on at Wind<br>
>>> River. It<br>
>>> >>>>> was generally accepted that OpenEmbedded would like to accept and own the<br>
>>> >>>>> contribution of this component.<br>
>>> >>>>><br>
>>> >>>>> The one remaining question was what to call the program. I had<br>
>>> temporarily<br>
>>> >>>>> called it 'oe-setup'. However, we need a real name for this repository.<br>
>>> >>>>><br>
>>> >>>>> The purpose of the repository is to 'setup' a new project using the<br>
>>> Layer Index.<br>
>>> >>>>><br>
>>> >>>>> So for lacking a better name, I'd say:<br>
>>> >>>>><br>
>>> >>>>> * openembedded-setup<br>
>>> >>>>> * oesetup<br>
>>> >>>>> * oe-setup<br>
>>> >>>><br>
>>> >>>> oe-project-creator<br>
>>> >>>><br>
>>> >>>> project-creator<br>
>>> >>>><br>
>>> >>>> project-baker<br>
>>> >>>><br>
>>> >>>> chief<br>
>>> >>><br>
>>> >>> Ohh this makes me think of 'chef' -- it goes with the bitbake, cooker,<br>
>>> toaster,<br>
>>> >>> etc names.<br>
>>> >>><br>
>>> >>> openembedded-chef<br>
>>> >>><br>
>>> >>> Hows that sound?<br>
>>> >>><br>
>>> >><br>
>>> >> The name could be confused with the Chef infrastructure automation<br>
>>> software [1]<br>
>>> >><br>
>>> >><br>
>>> >> [1] <a href="https://www.chef.io/chef/" rel="noreferrer" target="_blank">https://www.chef.io/chef/</a><br>
>>> ><br>
>>> > Ya, I've heard the same from a few people offline. They suggested we refer to<br>
>>> > this as "Sous Chef" (documentation, wiki pages, READMEs...), but keep the idea<br>
>>> > of the repo name being openembedded-chef or oe-chef.<br>
>>> ><br>
>>> > Anyone have any opinion on that?<br>
>>> ><br>
>>> > (Explanation, the Sous Chef is the one that prepares everything, but the<br>
>>> Chef is<br>
>>> > the one that actually does the cooking, etc.. (i.e. the developer in charge.))<br>
>>><br>
>>> Before accepting it, it would be good if there is an email discussing<br>
>>> it on oe-core mailing list so more people can review the tool.<br>
>>><br>
>>> I were not at the meeting so I am still waiting to review it.<br>
>>><br>
>>><br>
>>> Agreed.<br>
>><br>
>> The purpose of this thread is to come up with a name for a project.<br>
>><br>
>> Once the project is prepared it will be published in a location people can<br>
>> comment on.<br>
>><br>
>> From the meeting the people in the room generally agreed that the OpenEmbedded<br>
>> Project wanted this code on the <a href="http://git.openembedded.org" rel="noreferrer" target="_blank">git.openembedded.org</a> repository server. Once<br>
>> that is there, then it's like any other project subject to review, patches, etc.<br>
><br>
> Nack!! Having it there means it is official and the review must be<br>
> done prior that.<br>
><br>
> Sorry but this is unacceptable<br>
<br>
</div></div>Calm down guys, at least 20 people have seen a demo and given it<br>
favorable comments. Mark has explained he is working the code through<br>
the review needed to release it, but if you arrange a time with him, he<br>
can show it to you as some form of webcast. Please, if you want to see<br>
it, talk to Mark and arrange a time you can be available that works for him.</blockquote></div><br>If he can’t be bothered to take 15 minutes and post something more open and accessible than a webex presentation, I don’t really see the point, personally.<br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>