[OpenWrt-Devel] Request for Feedback - prplwrt Software Support Program - initial draft

[Eric Schultz]

Linus,

Sure, I'd be happy to clarify. We had an internal discussion in prpl about
what the best way to focus the proposals for prpl funding. As with any
group of funders, there was some tension between having a totally unfocused
set of proposals about any topic and proposals that fulfill the goals of
the funders. As a way to having some focus on the topics of the proposals
while not prescribing too much, we agreed on requiring proposals to fit
into themes for projects to fund which prpl would set.

One theme that prpl and its members are particularly interested in is
"Carrier Grade Features for OpenWrt". In particular, a number of carriers
are interested in using OpenWrt more and are interested in features that
fit their needs. Some of the potential proposals related to that could
include system management features (TR-69 support has come up in
discussions a lot), autoupdating and transactional updates. (We'll come up
with a better description of the themes before we ask for project ideas)

I hope that answers your questions.

Thanks,

Eric

On Sat, Mar 5, 2016 at 12:32 PM, Linus Lüssing <linus.luessing at c0d3.blue>
wrote:

> On Thu, Mar 03, 2016 at 03:07:22PM -0600, Eric Schultz wrote:
> > * prpl and its members, as funders, would set initial themes that all
> > projects would be expected to fit into.
>
> Could you clarify what you mean with "initial themes", maybe some
> examples?
>
> What would happen if the OpenWRT community were unhappy with what
> prpl members set as "initial themes"?
>
>
> What would happen if an "initial theme" decided by
> "the industry(TM)" through prpl membership were contrary to some
> non-profit projects/organisations (for instance Freifunk) ideas on
> "initial themes"?
>



-- 
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschultz at prplfoundation.org
cell: 920-539-0404
skype: ericschultzwi
@EricPrpl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20160307/34f09e70/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel