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: Wed, 10 Jun 2009 15:11:57 +0200	[thread overview]
Message-ID: <200906101511.57613.mickey@vanille-media.de> (raw)
In-Reply-To: <d2b9ea600906092353o4fe9ea02vbc7df3b103b401c4@mail.gmail.com>

> As for the last bullet point, what is the status of membership for
> those of us without commit access? I seem to have seen mixed signals
> wether we are invited to be member of the e.V.  Some messages
> indicates that only people with commit access are going to be
> accepted, while others (like mickey) request all interested in OE to
> join the e.V.

One of the major purposes of the e.V. is being able to raise funds to give 
people a chance to improve the spots in OE where we are weak. The idea of a 
self-chosen membership fee was to invite companies who have a certain benefit 
from OE giving back in the form of tax-excemptible membership fees and 
donations.

Most e.V. associations have the notion of 'active' and 'passive' members -- 
both which are equal stakeholders interested in supporting the association 
through their contributions. I consider active members being the committers 
contributing through code, docs, etc. and passive members being the ones who 
rather want to contribute in monetary form.

By being a member, you have the rights to vote when it comes to decisions that 
influence the future of the OE.

> Could someone put a small statement on Wiki on this?

We should, if the board agrees with that.

:M:




  parent reply	other threads:[~2009-06-10 13:21 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 [this message]
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=200906101511.57613.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