Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] the EFF announcement
Date: Wed, 23 Jul 2014 19:22:39 -0700	[thread overview]
Message-ID: <CAA93jw7tyT4gieEdMTrEoQ2+MY5EL2UmeBwRYc9FtSbhN2b=_A@mail.gmail.com> (raw)

As you have probably seen by now, the EFF's openwireless.org project
chose cerowrt to start with as a base for future development. I have
been too busy at ietf to pay much attention to the resulting press.

I'd like to thank everyone that participated in getting cero and
bufferbloat.net's part of the story across on threads like:

http://lwn.net/Articles/606034/

http://yro.slashdot.org/story/14/07/22/2234239/eff-releases-wireless-router-firmware-for-open-access-points

https://news.ycombinator.com/item?id=8060784

http://www.gossamer-threads.com/lists/nanog/users/173307?do=post_view_threaded

and dozens more.

A couple of these threads were extremely useful and interesting -
particularly in identifying future hardware candidates.

I have no idea who most of you are in that virtual universe above,
please feel free to fess up. :)

(and thanks, regardless)

Over here (toronto) I was mostly focused on shaking up the AQM working
group with things like the below. I don't know to what extent I was
successful, but the queue at the microphone was quite impressive, and
I didn't manage to get through 1/3 of my slides.

http://snapon.lab.bufferbloat.net/~d/Presos/CaseForComprehensiveQueueManagement/



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

                 reply	other threads:[~2014-07-24  2:22 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='CAA93jw7tyT4gieEdMTrEoQ2+MY5EL2UmeBwRYc9FtSbhN2b=_A@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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