[prev in list] [next in list] [prev in thread] [next in thread]
List: openembedded-architecture
Subject: Re: [Openembedded-architecture] OEDEM - Setup program
From: Christopher Larson <clarson () kergoth ! com>
Date: 2016-10-18 18:16:14
Message-ID: CABcZAN=mR_S3p_sWk=LcS3JBZ1dzDe1SoYwOq2yWtutJHDep8Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, Oct 18, 2016 at 11:12 AM, Mark Hatle <mark.hatle@windriver.com>
wrote:
> On 10/18/16 12:54 PM, Christopher Larson wrote:
> >
> > On Tue, Oct 18, 2016 at 10:45 AM, Otavio Salvador
> > <otavio.salvador@ossystems.com.br <mailto:otavio.salvador@
> ossystems.com.br>> wrote:
> >
> > On Tue, Oct 18, 2016 at 3:32 PM, Mark Hatle <
> mark.hatle@windriver.com
> > <mailto:mark.hatle@windriver.com>> wrote:
> > > On 10/18/16 1:42 AM, Samuel Stirtzel wrote:
> > >> 2016-10-18 4:22 GMT+02:00 Mark Hatle <mark.hatle@windriver.com
> > <mailto:mark.hatle@windriver.com>>:
> > >>> On 10/17/16 7:06 PM, akuster808 wrote:
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> On 10/17/2016 04:22 PM, Mark Hatle wrote:
> > >>>>> At OEDEM I presented the setup program I've been working on at
> Wind
> > River. It
> > >>>>> was generally accepted that OpenEmbedded would like to accept
> and own the
> > >>>>> contribution of this component.
> > >>>>>
> > >>>>> The one remaining question was what to call the program. I had
> > temporarily
> > >>>>> called it 'oe-setup'. However, we need a real name for this
> repository.
> > >>>>>
> > >>>>> The purpose of the repository is to 'setup' a new project
> using the
> > Layer Index.
> > >>>>>
> > >>>>> So for lacking a better name, I'd say:
> > >>>>>
> > >>>>> * openembedded-setup
> > >>>>> * oesetup
> > >>>>> * oe-setup
> > >>>>
> > >>>> oe-project-creator
> > >>>>
> > >>>> project-creator
> > >>>>
> > >>>> project-baker
> > >>>>
> > >>>> chief
> > >>>
> > >>> Ohh this makes me think of 'chef' -- it goes with the bitbake,
> cooker,
> > toaster,
> > >>> etc names.
> > >>>
> > >>> openembedded-chef
> > >>>
> > >>> Hows that sound?
> > >>>
> > >>
> > >> The name could be confused with the Chef infrastructure automation
> > software [1]
> > >>
> > >>
> > >> [1] https://www.chef.io/chef/
> > >
> > > Ya, I've heard the same from a few people offline. They suggested
> we refer to
> > > this as "Sous Chef" (documentation, wiki pages, READMEs...), but
> keep the idea
> > > of the repo name being openembedded-chef or oe-chef.
> > >
> > > Anyone have any opinion on that?
> > >
> > > (Explanation, the Sous Chef is the one that prepares everything,
> but the
> > Chef is
> > > the one that actually does the cooking, etc.. (i.e. the developer
> in charge.))
> >
> > Before accepting it, it would be good if there is an email discussing
> > it on oe-core mailing list so more people can review the tool.
> >
> > I were not at the meeting so I am still waiting to review it.
> >
> >
> > Agreed.
>
> The purpose of this thread is to come up with a name for a project.
>
> Once the project is prepared it will be published in a location people can
> comment on.
>
> From the meeting the people in the room generally agreed that the
> OpenEmbedded
> Project wanted this code on the git.openembedded.org repository server.
> Once
> that is there, then it's like any other project subject to review,
> patches, etc.
>
> This is on the architecture list simply because I want a name for the
> repository
> before we setup something so we're not fighting over a name for the next 6
> months.
>
> As I said in another part of the thread, I'm happy to give a demo to
> anyone on
> the code. It's not yet available as sources yet -- it's in review here, I
> have
> to follow the process before I can share the code. Once it's published
> then it
> will be the OpenEmbedded Communities code to work on.
I don't think we should need webex or a source repository to give folks a
clue what it is and how it works. Why is there no readme, example usage,
pastebin of a terminal session, screencast video, anything?
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 18, \
2016 at 11:12 AM, Mark Hatle <span dir="ltr"><<a \
href="mailto:mark.hatle@windriver.com" \
target="_blank">mark.hatle@windriver.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 10/18/16 12:54 PM, Christopher Larson \
wrote:<br> ><br>
> On Tue, Oct 18, 2016 at 10:45 AM, Otavio Salvador<br>
</span><span class="">> <<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> </span><span \
class="">> <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> </span>> \
<mailto:<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.<wbr>com</a>>>:<br>
<div><div class="">> >>> 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>
</div></div>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>
This is on the architecture list simply because I want a name for the repository<br>
before we setup something so we're not fighting over a name for the next 6 \
months.<br> <br>
As I said in another part of the thread, I'm happy to give a demo to anyone \
on<br> the code. It's not yet available as sources yet -- it's in review \
here, I have<br> to follow the process before I can share the code. Once it's \
published then it<br> will be the OpenEmbedded Communities code to work \
on.</blockquote></div><br>I don't think we should need webex or a source repository \
to give folks a clue what it is and how it works. Why is there no readme, example \
usage, pastebin of a terminal session, screencast video, anything?<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>
_______________________________________________
Openembedded-architecture mailing list
Openembedded-architecture@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic