From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: New e.V. members - Last Call
Date: Tue, 25 May 2010 11:45:35 +0100 [thread overview]
Message-ID: <1274784335.1272.8758.camel@rex> (raw)
In-Reply-To: <1273141339.5743.82.camel@rex>
On Thu, 2010-05-06 at 11:22 +0100, Richard Purdie wrote:
> Hi,
>
> We're going to have a drive for new e.V. members since there are a lot
> of people using OE who are not part of our official body (the e.V.).
> Membership has advantages like being able to vote on e.V. issues and
> groups like the TSC.
>
> If there is anyone interested in becoming a member please let me know
> within the next week. We'll then go through the procedure for accepting
> new members.
I've been travelling so I'm a little adrift with this. Are there any
other people who'd like to become members?
I expect we'll be starting the process for accepting new members within
the next few days so speak now! :)
Cheers,
Richard
prev parent reply other threads:[~2010-05-25 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 10:22 New e.V. members Richard Purdie
2010-05-25 10:45 ` Richard Purdie [this message]
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=1274784335.1272.8758.camel@rex \
--to=rpurdie@rpsys.net \
--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