From: Ken Gilmer <ken@buglabs.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE dev meeting
Date: Thu, 08 Jan 2009 10:15:17 -0500 [thread overview]
Message-ID: <1231427717.22380.3.camel@t61.buglabs.net> (raw)
In-Reply-To: <200901042339.31569.mickey@vanille-media.de>
Maybe you also can decide on Mateo's OE logo proposal.
cheers
ken
On Sun, 2009-01-04 at 23:39 +0100, Michael 'Mickey' Lauer wrote:
> Am Sunday 04 January 2009 23:12:15 schrieb Philip Balister:
> > How long would this meeting last? Before would be better for me. I need
> > to work this out ASAP so I can buy a plane ticket.
>
> One day would be fine. There's a number of issues that need some consensus
> before we can move forward. Things that come to mind include:
>
> * The future of BitBake -- where to continue to develop it, in which style,
> and which features to concentrate on.
>
> * Splitting the recipe tree.
>
> * Evaluating our feedback of the first months w/ git.
>
> * Streamlining Poky merges.
>
> * OE and the distro situation
>
> * Documentation, Website, and Hosting.
>
> IIRC Richard had some additional points. RP?
>
next prev parent reply other threads:[~2009-01-08 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 15:47 OE dev meeting Michael 'Mickey' Lauer
2009-01-04 16:27 ` Koen Kooi
2009-01-04 22:12 ` Philip Balister
2009-01-04 22:39 ` Michael 'Mickey' Lauer
2009-01-05 12:30 ` Richard Purdie
2009-01-05 12:41 ` Graeme Gregory
2009-01-05 12:59 ` Koen Kooi
2009-01-08 0:29 ` Michael 'Mickey' Lauer
2009-01-09 1:26 ` Philip Balister
2009-01-09 8:40 ` Phil Blundell
2009-01-13 10:47 ` Graeme Gregory
2009-01-13 13:34 ` Philip Balister
2009-01-21 21:29 ` Leon Woestenberg
2009-01-21 21:34 ` Philip Balister
2009-01-21 22:14 ` Ulf Samuelsson
2009-01-21 22:25 ` Philip Balister
2009-01-22 7:16 ` Alessandro GARDICH
2009-01-13 10:58 ` Alessandro GARDICH
2009-01-13 13:16 ` Marcin Juszkiewicz
2009-01-08 15:15 ` Ken Gilmer [this message]
2009-01-05 6:23 ` Marcin Juszkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1231427717.22380.3.camel@t61.buglabs.net \
--to=ken@buglabs.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.