Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Donation
Date: Tue, 14 Nov 2017 10:51:53 +0100	[thread overview]
Message-ID: <F37EDD85-33CF-42FE-9F4F-48F7EC4F3D46@gmail.com> (raw)
In-Reply-To: <mailman.7.1510506001.13084.cake@lists.bufferbloat.net>


> On Nov 12, 2017, at 6:00 PM, cake-request@lists.bufferbloat.net wrote:
> 
> I sometimes think we should establish an organization, with a board of
> directors, a bank account, etc, but aside
> from grant money, donated computers and computer time, and all the
> massive efforts of all the volunteers, that's most of the donations
> we've ever got, and it would be, at least, 800 bucks to start a
> non-profit, + an accountant to "do right".
> 
> Any and all thoughts as to how to do better are welcomed.
> 
> We could have a bake sale for cake, to get it mainlined.

Has there been any thought towards monetizing some portion of the bufferbloat project to help pay for it? Here are a couple of ideas:

- Make a network and bloat testing service with a subscription tier or advertising supported free tier. Proceeds could at first fund the server resources needed, and maybe there’d be something left over. I don’t think there’s anything out there that’s more technically oriented and measures one-way delay, or differentiates between upstream and downstream packet loss, or has some of flent’s features like TCP RTT or the myriad of tests it supports, for starters. I really don’t know if anyone would pay a subscription fee for this though, or how much ad revenue would be possible.

- I’m intrigued by the idea of a cooperative or so-called “platform cooperative". In this case, individuals or companies could pay a monthly or annual fee to either just support the effort, or get access to a higher level of support, the bloat testing service, or specific code changes, etc. Any income beyond what’s needed to meet expenses could be distributed to its members somehow. This is a vague idea so far, I know. But I’ve been pretty impressed with how well the cooperative ISP I use works (lbcfree.net), and at its apparent resiliency over time. Though, the service they offer to their customers may be more clearly defined (“become a member, get Internet”).

By the way, what or how much is needed to get Cake mainlined?


       reply	other threads:[~2017-11-14  9:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7.1510506001.13084.cake@lists.bufferbloat.net>
2017-11-14  9:51 ` Pete Heist [this message]
2017-11-14 20:10   ` Dave Taht
2017-11-15 14:41     ` Pete Heist
2017-11-15 19:44       ` [Cake] Cake upstream Planning Dave Taht
2017-11-15 20:04         ` Dave Taht
2017-11-15 20:44           ` Pete Heist
2017-11-15 20:49             ` Dave Taht
2017-11-15 20:06         ` Pete Heist
2017-11-15 20:19           ` Dave Taht
2017-11-15 20:28             ` Nils Andreas Svee
2017-11-15 20:58               ` Pete Heist
2017-11-15 22:40                 ` Nils Andreas Svee
2017-11-16  8:41                   ` Pete Heist
     [not found] <mailman.970.1510459224.3609.cake@lists.bufferbloat.net>
2017-11-12  4:42 ` [Cake] Donation Dave Taht

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F37EDD85-33CF-42FE-9F4F-48F7EC4F3D46@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@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