From: Dave Taht <d@taht.net>
To: bloat@lists.bufferbloat.net, sysmom@lists.bufferbloat.net
Subject: [Bloat] ssh keys wanted if you want on our virtual servers
Date: Tue, 29 Mar 2011 10:03:16 -0400 [thread overview]
Message-ID: <4D91E6A4.1000702@taht.net> (raw)
The new build server (huchra.bufferbloat.net) is mostly up, as are a few
virtuals for handling things like builds of openwrt, and other
mainstream OSes, and overall management of the site.
We could use a few helpers in getting the virtuals fully configured and
operational (buildbot, hudson, rt).
if interested please send me an ssh key and proposed login and what
you'd like to be working on.
There's been a bit of discussion as to where to go with the wiki, not
only to follow the redmine fork, but as to how to organize the
presentation to better express the issues of bufferbloat and the
mitigations, fixes in progress, and other projects being proposed
(notably, addressing the shaper issue). More details are available on
the www.bufferbloat.net wiki but you'd need to register on the wiki in
order to see them.
http://www.bufferbloat.net/account/register
reply other threads:[~2011-03-29 14:04 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D91E6A4.1000702@taht.net \
--to=d@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=sysmom@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