Historic archive of defunct list bismark-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Tim Upthegrove <tim.upthegrove@gmail.com>
To: openwrt-devel@lists.openwrt.org
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] Request for help on OpenWRT-based project
Date: Sun, 17 Apr 2011 13:13:47 -0400	[thread overview]
Message-ID: <BANLkTi=MhpEHDLt74QsoCjNHDk2F3qe9CQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin2kKkOou02B0GnnZYFjBksaVyQmA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]

Sorry for the spam, but a few more direct links with some relevant
information on the project, just so people have a clue of what they might be
working on :)

http://www.caida.org/workshops/isma/1102/slides/aims1102_ssundaresan.pdf
http://gettys.wordpress.com/2011/02/17/caida-workshop/

Thanks,
Tim



On Sun, Apr 17, 2011 at 12:58 PM, Tim Upthegrove
<tim.upthegrove@gmail.com>wrote:

> Greetings All!
>
> I am on a team of folks working on the BISMark project over at Georgia Tech
> and around the world.
>
> The BISMark project is part of an effort to benchmark the openness of
> network connections [1] as well as a means to collect data for identifying
> problems such as bufferbloat [2] in upstream networks.
>
> Our goal is to collect performance metrics from a diverse set of locations
> that sit at the edge of the Internet.
>
> The team is using OpenWRT on the wndr3700, noxbox, and an atom based
> platform.
>
> While we are aware of resources such as this mailing list and the #openwrt
> channel on irc,  we are hoping to find a few people with significant OpenWRT
> development experience and insight into OpenWRT best practices, to join our
> team and help get us over some humps.
>
> Right now we could really use help with the packaging of some experimental
> software. Are there any packaging experts around that could spend a few days
> talking to a group of people on how to do it right?
>
> Our end goal is not just to have a new platform which people can use, but
> to provide a slew of new packages and patches back to the OpenWRT community.
> [3]
>
> More information on the project and how to participate can be seen at
> http://www.bufferbloat.net/projects/bismark/wiki , and we can be found on
> irc in #bismark and #bufferbloat on freenode.net
>
> Tim
>
> [1] http://www.gatech.edu/newsroom/release.html?nid=65059
> [2] http://www.bufferbloat.net/
> [3] http://www.bufferbloat.net/projects/bismark/issues/<http://www.bufferbloat.net/projects/bismark>
>
>

[-- Attachment #2: Type: text/html, Size: 3266 bytes --]

      reply	other threads:[~2011-04-17 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-17 16:58 Tim Upthegrove
2011-04-17 17:13 ` Tim Upthegrove [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

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

  git send-email \
    --in-reply-to='BANLkTi=MhpEHDLt74QsoCjNHDk2F3qe9CQ@mail.gmail.com' \
    --to=tim.upthegrove@gmail.com \
    --cc=bismark-devel@lists.bufferbloat.net \
    --cc=openwrt-devel@lists.openwrt.org \
    /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