From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: progress on OE organization issues
Date: Fri, 15 May 2009 15:04:12 -0400 [thread overview]
Message-ID: <4A0DBCAC.5000403@balister.org> (raw)
In-Reply-To: <1242410201.4514.79.camel@lenovo.internal.reciva.com>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
Phil Blundell wrote:
> On Thu, 2009-05-07 at 08:08 -0400, Philip Balister wrote:
>> My number one concern is that we not create multiple membership groups
>> and committees. There is no sense creating groups independent of the eV.
>
> I guess my problem with this point of view is that I haven't ever really
> seen a clear roadmap or timeline for getting the e.V. "deployed" in
> practice, nor a definitive statement of what exactly the e.V.'s mission
> will be once it is up and running. (In particular there seems to be
> some unclarity about whether the e.V. is intended as purely an
> administrative vehicle for managing funds, organising servers and the
> like, or whether it is to be more of a general project governance
> organisation.) So it seems like we might be waiting a long time, only
> to discover in the end that, when the e.V. is up and running, it doesn't
> actually help us with solving the problems at hand and we are no better
> off than if we'd just acted straight away.
What exactly are you proposing to do?
Philip
>
> Presumably the existing core team must have some kind of vision for the
> exact role that the e.V. would play in this new world, and how we get
> there from here, but I've never seen it articulated anywhere. Can you
> shed any light on that?
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-05-15 19:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 12:44 progress on OE organization issues Cliff Brake
2009-04-30 14:26 ` Phil Blundell
2009-05-01 1:43 ` Cliff Brake
2009-05-07 11:19 ` Phil Blundell
2009-05-07 12:08 ` Philip Balister
2009-05-15 17:56 ` Phil Blundell
2009-05-15 19:04 ` Philip Balister [this message]
2009-05-15 21:54 ` Phil Blundell
2009-05-15 22:37 ` Michael 'Mickey' Lauer
2009-05-16 9:48 ` Richard Purdie
2009-05-16 10:55 ` Phil Blundell
2009-05-16 13:03 ` Mark Brown
2009-05-16 12:02 ` Phil Blundell
2009-05-16 12:54 ` Philip Balister
2009-06-02 21:18 ` Phil Blundell
2009-06-04 19:57 ` GNUtoo
2009-06-05 21:43 ` Cliff Brake
2009-06-06 6:46 ` Michael 'Mickey' Lauer
2009-06-09 9:21 ` Michael 'Mickey' Lauer
2009-06-09 9:53 ` Rolf Leggewie
2009-06-10 13:34 ` Cliff Brake
[not found] ` <d2b9ea600906092353o4fe9ea02vbc7df3b103b401c4@mail.gmail.com>
2009-06-10 13:11 ` Michael 'Mickey' Lauer
2009-06-11 6:48 ` Esben Haabendal
2009-06-11 10:10 ` Phil Blundell
2009-06-11 12:35 ` Philip Balister
2009-05-15 19:48 ` Cliff Brake
2009-05-24 15:49 ` Alessandro GARDICH
2009-05-24 16:26 ` Philip Balister
2009-05-06 12:44 ` Cliff Brake
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=4A0DBCAC.5000403@balister.org \
--to=philip@balister.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox