Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Alessandro GARDICH <gremlin@gremlin.it>
To: openembedded-devel@openembedded.org
Subject: Re: progress on OE organization issues
Date: Sun, 24 May 2009 17:49:05 +0200	[thread overview]
Message-ID: <4A196C71.7050108@gremlin.it> (raw)
In-Reply-To: <f96d234e0905151248s6962d25ck309197268d475e9b@mail.gmail.com>

Cliff Brake wrote:
> One thing about OE that may not be typical is the rate at which key
> people come and go.  That said, it seems like the structure needs to
> accommodate this -- perhaps by electing a new core team every 3
> months.  I propose we make this real simple -- everyone with commit
> access gets one vote, and we elect a core team (5 people).  Eventually
> this could be expanded to "members".  Thoughts?
> 

Maybe a such high rate of elections could be annoying, maybe better have 
a valid board with also 3 or 4 members if someone move away ...
I think is realistic that board members will be elected from more 
present developers so probably the high rate of turn over shouldn't 
affect the boards.

just my 2 cent



-- 
  /------------------------------------------------\
|     Alessandro Gardich : gremlin#gremlin!it      |
  >------------------------------------------------<
|  I never saw a wild thing sorry for itself.      |
|  A small bird will drop frozen dead from a bough |
|  without ever having felt sorry for itself.      |
  \------------------------------------------------/




  reply	other threads:[~2009-05-24 16: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
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 [this message]
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=4A196C71.7050108@gremlin.it \
    --to=gremlin@gremlin.it \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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