[prev in list] [next in list] [prev in thread] [next in thread]
List: openembedded-architecture
Subject: Re: [Openembedded-architecture] OEDEM - Setup program
From: Mark Hatle <mark.hatle () windriver ! com>
Date: 2016-10-18 19:21:48
Message-ID: 305727ca-fef6-48ae-26ce-81f88a3143bd () windriver ! com
[Download RAW message or body]
On 10/18/16 2:01 PM, Christopher Larson wrote:
>
> On Tue, Oct 18, 2016 at 11:45 AM, Philip Balister <philip@balister.org
> <mailto:philip@balister.org>> wrote:
>
> On 10/18/2016 02:20 PM, Otavio Salvador wrote:
> > On Tue, Oct 18, 2016 at 4:12 PM, Mark Hatle <mark.hatle@windriver.com
> <mailto: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>
> <mailto: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>
> >>> <mailto: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>
> >>> <mailto: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
> <http://git.openembedded.org> repository server. Once
> >> that is there, then it's like any other project subject to review,
> patches, etc.
> >
> > Nack!! Having it there means it is official and the review must be
> > done prior that.
> >
> > Sorry but this is unacceptable
>
> Calm down guys, at least 20 people have seen a demo and given it
> favorable comments. Mark has explained he is working the code through
> the review needed to release it, but if you arrange a time with him, he
> can show it to you as some form of webcast. Please, if you want to see
> it, talk to Mark and arrange a time you can be available that works for him.
>
>
> 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.
I just replied.. This is the best i can do.. It took me 20 minutes to write
this, so I've already exceeded your 15.
I am not going to put together videos of this. I will be happy to do it via a
call or similar. I can do this quickly and easily and answer questions.
Otherwise wait for the code to open up and comment at that time.
> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
_______________________________________________
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