From: Philip Balister <philip@balister.org>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
"openembedded-members@lists.openembedded.org"
<openembedded-members@lists.openembedded.org>
Subject: Yocto Dev Day Sponsorship Opportunity
Date: Thu, 29 Aug 2013 09:45:10 -0400 [thread overview]
Message-ID: <521F5066.8050005@balister.org> (raw)
This is kind of short notice, but I'd like some feedback on this idea ...
So for the Yocto Dev Day before ELCE in Edinburgh, the Yocto Project is
looking for additional Sponsorship to cover the cost of coffee breaks
(and some other stuff, but these are the least expensive)
I'm wondering if OpenEmbedded would like to sponsor a coffee break.
Obviously, we'd need to do a quick round of fund raising to make this
happen. I think it would be a good way for us to increase visibility of
the OpenEmbedded brand and gives many of the smaller players a chance to
contribute to some of the larger Yocto Project costs.
So I'd like to hear two things from everyone:
1) Should we sponsor events when it makes sense?
2) If you are interested in helping sponsor this particular even, send
me a private email with amounts. If there is sufficient interest we have
access to US and EU bank accounts for money collection.
Long term, I'd like to get a more organized fund raising plan in place
and identify how we can support the needs of the project better. Some
ideas that have been tossed around over the years, travel grants for
people promoting OE, event sponsorship, pay for infrastructure
improvements, contribute to auto builder costs etc. Many of these are
being covered by volunteers working in the community It would be nice to
help them out.
I'll be semi-afk through Tuesday, but should be able to see email.
Philip
next reply other threads:[~2013-08-29 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 13:45 Philip Balister [this message]
2013-08-29 21:42 ` Yocto Dev Day Sponsorship Opportunity Denys Dmytriyenko
2013-08-29 23:29 ` Philip Balister
2013-08-30 18:19 ` Paul Eggleton
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=521F5066.8050005@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.