From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave@taht.net>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake on LEDE - package maintainer required
Date: Tue, 27 Jun 2017 15:11:46 -0700 [thread overview]
Message-ID: <20170627151146.69b6d557@xeon-e3> (raw)
In-Reply-To: <87r2ycc0pf.fsf@nemesis.taht.net>
On Wed, 21 Jun 2017 17:42:20 -0700
Dave Taht <dave@taht.net> wrote:
> I have long sought sufficient funding to push cake into the mainstream
> and come up empty. Cake represents thousands of hours of volunteer labor
> as it is, and everyone that has worked on it deserves kudos...
>
> ... and a check...
>
> or at least... a bloody t-shirt. And I mean that both in the perjorative
> sense and in the descriptive sense, of being covered in scars.
>
> Honestly, I'd settle for some happy set of users of cake to throw in for
> the t-shirt, at the very least.
>
Open Source developers need a day job. Expecting a direct check for hard work in
new technology never seems to turn out well. That seems to be one of the root
causes of the GRsecurity complaints.
Last I checked the issues were not that Cake needed more technical tweaks, more
that it needed to changed into upstream kernel style. Should be semi automatic.
Also getting simplified documentation and man pages.
There is a difference between good enough and complete. Software is never
complete.
The other change of pace would accepting the upstream version as definitive
and eliminating forks.
next prev parent reply other threads:[~2017-06-27 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 17:41 Kevin Darbyshire-Bryant
2017-06-13 22:02 ` Stephen Hemminger
2017-06-13 22:40 ` Kevin Darbyshire-Bryant
2017-06-22 0:42 ` Dave Taht
2017-06-27 22:11 ` Stephen Hemminger [this message]
2017-06-27 23:58 ` Outback Dingo
2017-06-28 8:02 ` Kevin Darbyshire-Bryant
[not found] <mailman.3.1498147201.32609.cake@lists.bufferbloat.net>
2017-06-25 4:51 ` Georgios Amanakis
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=20170627151146.69b6d557@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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