[OpenWrt-Devel] OpenWrt summit by prpl

Hauke Mehrtens hauke at hauke-m.de
Sat May 21 09:15:47 EDT 2016



On 05/16/2016 06:40 PM, Eric Schultz wrote:
> Federico,
> 
> I don't want to speak for Hauke but I think he meant that that we have
> an event at ELCE this year and then plan on another at Battlemesh next year

Yes, you are correct. ;-)

> I personally think that's the best idea all around. I know prpl members
> have expressed lots of positive feedback on the idea of ELCE to Art and
> he's gotten very solid feedback from industry because it's so convenient
> for them. Planning on Battlemesh as well (with Battlemesh's approval of
> course) then brings some of the interested industry members into contact
> with a more community focused event. Hopefully that will build some new
> bridges and relationships. I think the combination is a win-win.

Hauke

> Eric
> 
> On Fri, May 13, 2016 at 3:15 AM, Nemesis <nemesis at ninux.org
> <mailto:nemesis at ninux.org>> wrote:
> 
>     Hi everyone,
> 
>     I have been at the event in Dublin last year with a colleague.
>     The event was really interesting from a technical point of view and we
>     really missed such an event focused on OpenWRT and the various
>     applications & services one can build with it.
> 
>     It would be good to have more communities to participate in such an
>     event, and it would be awesome if the most active developers would have
>     a leading role in organizing it.
> 
>     Hauke, one note regarding co-location, you wrote: "I would like to see
>     it co located with the ELCE and the Battlemesh next year."
> 
>     But I believe the Battlemesh next year won't be co located with ELCE,
>     did you mean the Battlemesh or ELCE?
> 
>     Federico
> 
> 
> 
> 
>     On 05/13/2016 12:44 AM, Hauke Mehrtens wrote:
>     > Hi,
>     >
>     > When I use OpenWrt in this mail, I mean OpenWrt and LEDE, I hope
>     we come
>     > to a solution in the next days on this.
>     >
>     > prpl wants to organize an OpenWrt summit again. Their goal is to bring
>     > the community, industry and developers together. Currently this is in
>     > planing and I want to know what should happen so that more developers
>     > and more members of the community would come to such an event.
>     >
>     > There are different ideas on how to organize such an event:
>     > 1. prpl organizes an event co located with the Embedded Linux
>     conference
>     > this October in Berlin.
>     > 2. prpl organizes an event co located with Battlemesh next year in
>     May.
>     > 3. Some people from OpenWrt organize an event in Prague at CZ.NIC.
>     > CZ.NIC would provide a location and local logistics, prpl could help
>     > with finance.
>     >
>     > It is also possible to do more than one solution or combine them.
>     >
>     > Are there some people interested in organizing this by themselfs with
>     > the help of CZ.NIC, then we could go with this solution?
>     > If nobody is interested in organizing this I would like to see it co
>     > located with the ELCE and the Battlemesh next year.
>     >
>     > No final name for this event was chosen. The current suggestion is
>     > "OpenWrt summit by prpl" or something similar.
>     >
>     > Are there any comments on this?
>     >
>     > Hauke
>     > _______________________________________________
>     > openwrt-devel mailing list
>     > openwrt-devel at lists.openwrt.org
>     <mailto:openwrt-devel at lists.openwrt.org>
>     > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>     >
>     _______________________________________________
>     openwrt-devel mailing list
>     openwrt-devel at lists.openwrt.org <mailto:openwrt-devel at lists.openwrt.org>
>     https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
> 
> 
> 
> -- 
> Eric Schultz, Community Manager, prpl Foundation
> http://www.prplfoundation.org
> eschultz at prplfoundation.org <mailto:eschultz at prplfoundation.org>
> cell: 920-539-0404
> skype: ericschultzwi
> @EricPrpl




More information about the openwrt-adm mailing list