All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Koen Kooi : Revert "ecore: catch up with	the new SONAMEs; move to autosplitting"
Date: Tue, 28 Apr 2009 17:26:34 -0400	[thread overview]
Message-ID: <49F7748A.4000405@balister.org> (raw)
In-Reply-To: <1240952918.4289.351.camel@lenovo.internal.reciva.com>

[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]

Phil Blundell wrote:
> On Tue, 2009-04-28 at 14:23 -0400, Cliff Brake wrote:
>> On Tue, Apr 28, 2009 at 10:41 AM, Phil Blundell <philb@gnu.org> wrote:
>>
>>> If we are to have a core team as the governing body for OE then I would
>>> like to see it taking a more active role in overseeing the project (in
>>> particular, to guide policies for technical issues and not merely focus
>>> on administrivia such as the formatting of commit messages or
>>> Signed-off-by lines), and for this to be done in a more transparent way.
>>> If the current members of the core team are, for whatever reason, not
>>> willing or able to discharge those duties then (much as I hesitate to
>>> call for this) perhaps it's time to hold elections and appoint new
>>> members in their place.
>> One possible path is to:
>>
>> 1) figure out how to get members added to the eV that is already in place.
>> 2) hold elections for a board
> 
> Agreed, that sounds like a good thing.  But, I'm not sure that the eV
> board would necessarily be the same thing as the core team or "steering
> committee" that would make the day-to-day decisions.  
> 
> My understanding of German law is pretty sketchy but I'm guessing that
> the main function of the eV board is to be legally responsible for the
> operation of the organisation and, as such, it probably requires a
> rather different set of skills than one would need to provide technical
> or even administrative oversight for the operation of the OE development
> project itself.  In particular, given that the eV is (obviously)
> constituted in Germany and hence that the authoritative copies of all
> the legal documents are presumably those drafted in German, I suspect
> that it would probably be a dim idea for anybody with a less than fluent
> grasp of that language to serve on the board.  

The kde ev documents are here: http://ev.kde.org/. I don't think there 
is any issue having non-German's on the board. In fact I would be 
unhappy if there was such a restriction in place.

The OE articles of association are based on the kde ones.

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  parent reply	other threads:[~2009-04-28 21:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090425075933.E6E18188456@amethyst.openembedded.net>
2009-04-25 11:04 ` [oe-commits] Koen Kooi : Revert "ecore: catch up with the new SONAMEs; move to autosplitting" Michael 'Mickey' Lauer
2009-04-25 13:32   ` Philip Balister
2009-04-25 13:40     ` Michael 'Mickey' Lauer
2009-04-25 18:17       ` Otavio Salvador
2009-04-25 18:27         ` Tom Rini
2009-04-25 18:51           ` Otavio Salvador
2009-04-25 19:00             ` Tom Rini
2009-04-25 19:03               ` Otavio Salvador
2009-04-25 18:34         ` Michael 'Mickey' Lauer
2009-04-25 18:44           ` Graeme Gregory
2009-04-25 19:44             ` Michael 'Mickey' Lauer
2009-04-25 20:01               ` Otavio Salvador
2009-04-25 20:13                 ` Michael 'Mickey' Lauer
2009-04-25 20:47               ` Marcin Juszkiewicz
2009-04-26  1:19                 ` Graeme Gregory
2009-04-26 12:09                   ` Philip Balister
2009-04-26  2:11                 ` Carsten Haitzler
2009-04-25 21:29               ` Marcin Juszkiewicz
2009-04-28 14:41               ` Phil Blundell
2009-04-28 18:13                 ` Stefan Schmidt
2009-04-29  8:12                   ` Marcin Juszkiewicz
2009-04-28 18:23                 ` Cliff Brake
2009-04-28 21:08                   ` Phil Blundell
2009-04-28 21:23                     ` Philip Balister
2009-04-28 21:26                     ` Philip Balister [this message]
2009-04-28 21:53                       ` Phil Blundell

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=49F7748A.4000405@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 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.