From: Eric Schultz <eschultz@prplfoundation.org>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"user@openwireless.org" <user@openwireless.org>,
"<ow-tech@eff.org>" <ow-tech@eff.org>, <battlemesh@ml.ninux.org>
Subject: [Cerowrt-devel] OpenWrt Summit Submission Deadline change
Date: Wed, 5 Aug 2015 15:46:50 -0500 [thread overview]
Message-ID: <CAMkzgA68unOT_ApDVB2=goBD00-zWAyzSMUFDOMDnfWRuC2cBw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
I’ve decided to move the OpenWrt Summit session submission deadline to
Friday August 28 (one week later than before). There were a number of folks
from Battlemesh who asked for an additional week for their proposals and
we’re happy to accommodate them
You certainly don’t have to wait until then to submit and I encourage
everyone to start submitting as soon as possible. If there are multiple
proposals on the same topic or a particular important topic that hasn’t
been addressed, addressing them sooner is much easier than later for
everyone.
Also, don’t be afraid to submit a session even if you don’t have what you
view as a cool use-case or created a new feature of OpenWrt. We’re also
looking for topics like:
* Building and customizing OpenWrt
* Adding hardware support to OpenWrt
* Package creation and submission on OpenWrt
* Integrating with LuCI
* Discussing important OpenWrt software like procd, ubus, buildroot, etc.
The OpenWrt community is filled with awesome people and I’m looking forward
to seeing what everyone comes up with.
If you’d like more information about the summit or submitting, please visit
http://summit.prplfoundation.org or contact me.
Thanks,
Eric
--
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschultz@prplfoundation.org
cell: 920-539-0404
skype: ericschultzwi
@EricPrpl
[-- Attachment #2: Type: text/html, Size: 1749 bytes --]
reply other threads:[~2015-08-05 20:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMkzgA68unOT_ApDVB2=goBD00-zWAyzSMUFDOMDnfWRuC2cBw@mail.gmail.com' \
--to=eschultz@prplfoundation.org \
--cc=battlemesh@ml.ninux.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ow-tech@eff.org \
--cc=user@openwireless.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