Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [Ow-tech] OpenWrt Summit RFP - Deadline August 21
Date: Wed, 29 Jul 2015 19:40:09 +0200	[thread overview]
Message-ID: <CAA93jw4soH9R-JvjdN51xPbR_tNqJru8LRWZoL+q4+5O3fzTEA@mail.gmail.com> (raw)
In-Reply-To: <CAMkzgA7J_GeTti6ukjBGojz23SLHGvx=Qjq8-ya_rhC=C8+CfA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]

---------- Forwarded message ----------
From: Eric Schultz <eschultz@prplfoundation.org>
Date: Wed, Jul 29, 2015 at 7:29 PM
Subject: [Ow-tech] OpenWrt Summit RFP - Deadline August 21
To: "<ow-tech@eff.org>" <ow-tech@eff.org>


To help encourage the growth and strength of OpenWrt, which is the base of
OpenWireless, prpl Foundation is organizing the OpenWrt Summit. Co-located
with ELCE in Dublin, Ireland on October 8, the OpenWrt Summit will be the
first community conference focusing exclusively on OpenWrt. Free for all to
attend, OpenWrt Summit does not require an ELCE ticket.

As a community centered conference, I invite users, developers, business
leaders, and anyone who is hoping to make a difference in OpenWrt to submit
a speaking/session proposal for the OpenWrt Summit.

Suggested topics include:

* OpenWrt introductory topics (What is OpenWrt? How to build? How to
install? How to build packages?)
* Hardware (Adding new OpenWrt support for hardware you created or bought,
contributing back to the core)
* Forks of OpenWrt (Best practices, staying close to core)
* OpenWrt usage (Unique and complex scenarios)
* Security (Containers, jails, etc)
* Culture (Encouraging new contributors, documentation, advocacy)
* Internet of Things/Internet of Everything
* Future of OpenWrt

We also welcome any other session topic related to OpenWrt. Again, I
encourage everyone interested to submit a session proposal for the OpenWrt
Summit. Proposals should be submitted by August 21. To learn more and to
submit your proposal, please visit:

http://wiki.prplfoundation.org/wiki/OpenWrt_Summit_2015

Also, if you're interested in learning more about the conference, including
lodging information, please visit this URL as well.

I look forward to the session proposals! If you have any questions, don't
hesitate to ask..

Thanks,

Eric Schultz


-- 
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschultz@prplfoundation.org
cell: 920-539-0404
skype: ericschultzwi
@EricPrpl

_______________________________________________
Ow-tech mailing list
Ow-tech@lists.eff.org
https://lists.eff.org/mailman/listinfo/ow-tech




-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

[-- Attachment #2: Type: text/html, Size: 3817 bytes --]

           reply	other threads:[~2015-07-29 17:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAMkzgA7J_GeTti6ukjBGojz23SLHGvx=Qjq8-ya_rhC=C8+CfA@mail.gmail.com>]

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=CAA93jw4soH9R-JvjdN51xPbR_tNqJru8LRWZoL+q4+5O3fzTEA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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