From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] A simple poll
Date: Tue, 3 Mar 2015 16:09:00 -0500 [thread overview]
Message-ID: <8D94367F-2437-4E7A-8EEF-AE391E5910DD@gmail.com> (raw)
In-Reply-To: <CAA93jw4FFFORg8Q=8fKCS8KfeFSeJs6puGqpXNhffNgAF9iXOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]
On Feb 28, 2015, at 12:02 PM, Dave Taht <dave.taht@gmail.com> wrote:
> A) What do you like about cerowrt?
- It just works
- It gives me a lot of cool features that I rely on (no bufferbloat, IPv6, routing on interfaces) and some that I don't (DNSSEC, babel)
- Pride in my (small) contribution to the project
- I own plenty of WNDR3800's, so I'll keep using it :-)
> B) What brought to you cerowrt?
I followed a link to the project in late 2011, and for whatever reason, I believed in the goal that you were seeking. I saw a latent gem of an idea, and the drive to make it go, but the website was disorganized. It was too hard to separate the features that were real and working, and those that were fond hopes, but were *way* out on the horizon. Dave let me edit the wiki, and you know the rest.
> C) Where do you want the project to go?
It may be time to declare victory on "fixing home routers". Since BB & CC have embraced virtually all the stuff we've pioneered, there doesn't seem to be much advantage to more development in that vein.
Maybe it is time to pivot the CeroWrt brand name to "making wifi fast".
> D) What can you do to help cerowrt?
I'll keep editing web sites and testing software. I'll also continue to offer words of encouragement.
> E) what can you do to help openwrt?
ENOTIME. But if there were a single thing they could do to help their ease-of-use (and therefore their popularity), it would be to make it drop-dead easy to find the proper firmware for a router from their Supported Devices page (http://wiki.openwrt.org/toh/start). It should be a single click to download the BB or CC version from that page.
Anyone know who would I write to at OpenWrt to make this suggestion?
Rich
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
prev parent reply other threads:[~2015-03-03 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 17:02 Dave Taht
2015-03-03 21:09 ` Rich Brown [this message]
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=8D94367F-2437-4E7A-8EEF-AE391E5910DD@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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