Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Eric Schultz <eschultz@prplfoundation.org>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	"<ow-tech@eff.org>" <ow-tech@eff.org>,
	 Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
Subject: [Cerowrt-devel] Request for Feedback - prplwrt Software Support Program - initial draft
Date: Thu, 3 Mar 2016 15:08:09 -0600	[thread overview]
Message-ID: <CAMkzgA4anLcNyEZSS8UhSBUCy_y_0dgbahagGHZYQQ=1MQX2Rg@mail.gmail.com> (raw)

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

As discussed in prplwrt meetings, prpl is interested in funding development
work on OpenWrt. In order to make this as fair as possible, I'm proposing a
process which I'm tentatively calling the prplwrt Software Support Program
(PSSP)

PSSP will fund innovative OpenWrt development work that is responsive to
the needs of the OpenWrt community and industry. To make sure the process
benefits the community as much as possible, I'm asking for your feedback.
Please look through the document I've linked below and provide feedback,
either as comments on the document or as a reply to this message.

As a quick summary, the process would go as follows:

* prpl and its members, as funders, would set initial themes that all
projects would be expected to fit into.
* the community, prpl members, and others would submit and comment on ideas
for projects that fit those themes
* potential implementers would then submit proposals for implementations,
including a budget, timeline and general plan for implementation
* an OpenWrt community committee, the prpl TSC and prpl Board would
finalize which implementations are selected and funded.

More details are in the linked document. I want to make sure everyone in
the OpenWrt community has had a chance to provide their thoughts on the
program so please provide your feedback as soon as possible and no later
than March 17.

Thanks,

Eric

PSSP proposal:
https://docs.google.com/document/d/1b5LwqNPUasSafP-3NLwnV7rXRRUPDfj5yrU772dkpoc/edit?usp=sharing

-- 
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: 2167 bytes --]

                 reply	other threads:[~2016-03-03 21:08 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='CAMkzgA4anLcNyEZSS8UhSBUCy_y_0dgbahagGHZYQQ=1MQX2Rg@mail.gmail.com' \
    --to=eschultz@prplfoundation.org \
    --cc=battlemesh@ml.ninux.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=ow-tech@eff.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