From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-members@lists.openembedded.org
Subject: Re: OEDEM Agenda
Date: Thu, 28 Oct 2010 16:45:18 +0100 [thread overview]
Message-ID: <4CC99A8E.7060805@balister.org> (raw)
In-Reply-To: <4CC99826.9050805@balister.org>
And Marcin reminded me to include the link:
http://wiki.openembedded.org/index.php/Oedem/2010
Philip
On 10/28/2010 04:35 PM, Philip Balister wrote:
> I've taken a quick stab at organizing the agenda for OEDEM. The only
> thing I feel strongly about is getting the General Assembly over with
> first. The only agenda item for the General Assembly that could be time
> consuming is the online voting procedure.
>
> If anyone has strong feelings on the online voting, it would be good to
> bring a written suggestion. The current system is not perfect, but it
> does work and has been tested so it does not get into situations that
> lead to no clear result. If there are no concrete ideas for the GA to
> discuss, I would suggest that interested parties volunteer to do some
> research into online voting processes and make suggestions.
>
> Please review the agenda and make suggestions. This a meeting for
> everyone to participate in. Emailed thoughts are welcome. I left the
> times flexible after the first couple of items.
>
> Philip
>
> PS: And once again, a big thanks to Intel for arranging for the meeting
> room.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
prev parent reply other threads:[~2010-10-28 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 15:35 OEDEM Agenda Philip Balister
2010-10-28 15:45 ` Philip Balister [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=4CC99A8E.7060805@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-members@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.