Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	 Cake List <cake@lists.bufferbloat.net>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Google summer of code
Date: Sat, 19 Jan 2019 11:38:35 -0800	[thread overview]
Message-ID: <CAA93jw5G2bZW0YVcVBLT3Tp=QTCdjvL-1O=4YUon7ivc8AdviQ@mail.gmail.com> (raw)

I started filling out the paperwork required to have bufferbloat.net
mentor a student in GSOC this year.

https://opensource.googleblog.com/2019/01/seeking-projects-for-gsoc-2019.html

Problem is, I'm stuck on potential topics! Cake's got some folk
analyzing cobalt, the new wifi code looks to land but there's no new
or old chipsets I know of that are fixable (nor do I think a student
can tackle wifi) - about the only thing I can think of thus far is to
attempt realizing the explicit load regulation (ELR) and some
congestion experienced (SGE) bit, in something like QUIC.

I liked very much that the cerowrt effort turned multiple folk into
openwrt developers, led others into kernel development, and some into
the IETF.

Any ideas for something that could fit into GSOC this summer?

-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

                 reply	other threads:[~2019-01-19 19:39 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='CAA93jw5G2bZW0YVcVBLT3Tp=QTCdjvL-1O=4YUon7ivc8AdviQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=make-wifi-fast@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