Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Splitting meta-oe
Date: Wed, 25 Jan 2012 17:12:05 -0500	[thread overview]
Message-ID: <4F207E35.3030908@balister.org> (raw)
In-Reply-To: <1327525435.2716.37.camel@x121e.pbcl.net>

On 01/25/2012 04:03 PM, Phil Blundell wrote:
> On Wed, 2012-01-25 at 15:45 -0500, Philip Balister wrote:
>> On 01/25/2012 12:57 PM, Phil Blundell wrote:
>>> Agreed.  I think the mailing lists ought to remain the primary forum for
>>> decision-making.  If there's something that needs to be discussed, let's
>>> do it here.  If we can't reach a consensus, that's what we have the TSC
>>> for.
>>
>> I do not want this to discourage from OE developers talking about things
>> like this when they have the chance. Sometimes, high bandwidth face to
>> face conversations can resolve issues much faster.
> 
> Absolutely, folks should feel welcome to discuss this and any other
> issues whenever they have the chance.  And if no conclusion has emerged
> by the time ELC comes around then that might indeed be a useful way to
> move things forward.  But, such face-to-face meetings inevitably involve
> only a subset of developers and the only way to ensure that all
> interested parties are able to participate is to hold discussion on the
> mailing list whenever possible.

Sure. I don't think anyone is suggesting that a few guys get together
and make binding decisions, just try to work through things a little faster.

Philip



  reply	other threads:[~2012-01-25 22:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 12:48 Splitting meta-oe Paul Eggleton
2012-01-25 14:01 ` Frans Meulenbroeks
2012-01-25 14:10 ` Martin Jansa
2012-01-25 15:09   ` Paul Eggleton
2012-01-25 17:01     ` Enrico
2012-01-25 14:34 ` Philip Balister
2012-01-25 14:47   ` Paul Eggleton
2012-01-25 16:00     ` Philip Balister
2012-01-25 17:33       ` Frans Meulenbroeks
2012-01-25 17:51         ` Khem Raj
2012-01-26  9:02         ` Martin Jansa
2012-01-26 14:45           ` Frans Meulenbroeks
2012-01-26 16:11             ` Martin Jansa
2012-01-26 18:36               ` Andreas Oberritter
2012-01-26 20:04           ` Khem Raj
2012-01-25 17:41       ` Paul Eggleton
2012-01-25 17:57         ` Phil Blundell
     [not found]           ` <4F2069CC.7060409@balister.org>
2012-01-25 21:03             ` Phil Blundell
2012-01-25 22:12               ` Philip Balister [this message]
2012-01-25 17:49 ` Khem Raj
2012-01-25 18:39   ` Paul Eggleton
2012-01-25 23:28     ` Khem Raj
2012-02-01 10:07 ` Paul Eggleton
2012-02-01 10:33   ` Koen Kooi
2012-02-01 11:11     ` Otavio Salvador
2012-02-01 15:39       ` Koen Kooi
2012-02-05 14:58       ` Koen Kooi

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=4F207E35.3030908@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=philb@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox