All,

Given the excitement and great relationships built at the last OpenWrt
Summit, prpl is looking forward to sponsoring and organizing another one
this year. There are a lot of decisions that need to be made: should the
summit still be associated with ELCE? Be more than one day? How to select
speakers in a fair manner and what duration talks are best? Plus social
planning. :) These are decisions that attendees should influence. After
all, we want this event to meet the needs of the OpenWrt community.

That’s why we’re inviting you, the members of the OpenWrt community
(end-users, contributors, employees of companies who use OpenWrt, really
anyone who likes the project), to consider joining the planning committee
for the 2016 OpenWrt Summit.

Planning committee members would be responsible for making decisions about
what sessions are featured at the event, when and where it happens, and
other general planning decisions. With the support of prpl staff and
volunteers, the committee would meet occasionally (likely virtually) in the
coming months to make the important logistic decisions necessary for the
event.  Closer to the event, the committee would rank and decide on which
presentation proposals to accept and to set the final schedule. While the
decisions are very important, being part of the planning committee is not
expected to require a great deal of time. prpl staff can help do the heavy
lifting of implementation while the planning committee would provide
direction.

If you’d like to be on the OpenWrt Summit Planning Committee, please email
me by April 18. Planning the Summit is a great way to make the event
valuable and productive for the whole OpenWrt community. I hope you
consider joining the fun!

Eric

-- 
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
[email protected]
cell: 920-539-0404
skype: ericschultzwi
@EricPrpl
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to