Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Michael 'Mickey' Lauer" <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: progress on OE organization issues
Date: Sat, 16 May 2009 00:37:25 +0200	[thread overview]
Message-ID: <200905160037.25213.mickey@vanille-media.de> (raw)
In-Reply-To: <1242424484.4514.117.camel@lenovo.internal.reciva.com>

I agree with pb's suggestion here. In fact some days ago I talked to RP about 
the state of OE and me, the failure of the original coreteam, the e.V. etc.

My view on that is: The ideal situation would be that everyone interested in 
OE -- no matter on which level, technically, supportive, or administrative, 
becomes a member of the e.V.  This is relatively straightforward and does not 
require any financial commitments per se as our status include that a member 
can chose its own membership fee.

The e.V. (remember, this should now include all stakeholders, so everyone who 
is interested in OE is allowed to vote -- not only the committers, but also 
the bug wizards, doc folks, etc.) then votes two boards, an administrative and 
a technical.

A) The administrative one takes care about the legal status, donations, taxes, 
granting access to servers, etc. This one we have already voted on our initial 
meeting in Brussels. It consists of 4 positions. For this year it consists of 
Florian, Robert, Holger, and me -- at least until the next elections...

B) The technical one is probably more interesting to most people on the list 
here. The technical board is responsible for keeping the project on track as a 
whole, helping us staying focused, improving BitBake and OpenEmbedded, trying 
to recruit more committers, and -- most important to me due to the recent 
series of events -- resolving conflicts.
This one should contain 7 positions, preferably filled with people having 
different areas of expertise, e.g. toolchain, system level stuff, higher level 
stuff, multimedia, mobile, etc.

All votes and discussions would be open and carried out on public mailing 
lists, wiki, etc. oe-private would be closed for good, since what we need most 
is transparency.

If we can pull such an organization off, I'd be willing to run for a position. 

Cheers,

:M:



  reply	other threads:[~2009-05-15 22:44 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
2009-05-15 21:54             ` Phil Blundell
2009-05-15 22:37               ` Michael 'Mickey' Lauer [this message]
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=200905160037.25213.mickey@vanille-media.de \
    --to=mickey@vanille-media.de \
    --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