From: Dave Taht <dave.taht@gmail.com>
To: Nick Feamster <feamster@cc.gatech.edu>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] Fwd: Bismark on M-Lab
Date: Wed, 25 May 2011 23:23:58 +0000 [thread overview]
Message-ID: <BANLkTi=xm34=ivr+oL62PA7h3VjWsPye6g@mail.gmail.com> (raw)
In-Reply-To: <B337120B-ED16-4915-B2D2-37FC0A155B20@cc.gatech.edu>
[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]
I would very much like it to stay below the radar for a while as we sort
various bits of infrastructure out.
This includes the vpn issue, the ditg issue, the possible dhcp bug, and
getting the database and website actually working well enough to withstand
the onslaught of real users.
And for me to get caught up on sleep.
Limit this to < the original 40 planned?
On Wed, May 25, 2011 at 11:01 PM, Nick Feamster <feamster@cc.gatech.edu>wrote:
> Please comment ... thoughts?
>
> Begin forwarded message:
>
> *From: *Meredith Whittaker <meredithrachel@google.com>
> *Date: *May 25, 2011 11:39:59 PM GMT+02:00
> *To: *Nick Feamster <feamster@cc.gatech.edu>
> *Subject: **Bismark on M-Lab*
>
> Hi Nick, all,
>
> I wanted to close the loop on a few next steps for getting Bismark up,
> running and known on M-Lab.
>
> 1. We're ready when you are to post an announcement about the tool on
> this site.
> This should be done when you begin accepting sign-ups for the router,
> and can stay there, soft-launched, until you're prepared for the sign-ups PR
> would generate. We will send you or draft for the text of the page within a
> day or two.
> 2. Whenever you're ready, I can put you in touch with the people who
> run the data pipeline, which will result in your getting the BisMark data
> off the M-Lab servers and in to Google Storage. You can work with them on
> data structure, etc..
> 3. Here's a link
> <http://googleblog.blogspot.com/2011/02/visualize-your-own-data-in-google.html>to
> the Public Data Explorer blog post, announcing their new API for data
> upload. This should give you a cursory idea of what would be involved in
> getting the analyzed BisMark data properly structured and visualized.
>
> My apologies for the delayed communication. I'm happy to answer any
> questions, and coordinate with you more closely on getting PR off the ground
> to coincide with your ability to quickly ship routers :)
>
> Thanks!
> Meredith
>
> --
> Meredith Whittaker
> Program Manager, Google NYC
> (917) 568-1666
>
>
>
>
>
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
>
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 4019 bytes --]
next prev parent reply other threads:[~2011-05-25 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikO9v6z3g0sfbS_3d_B3aKDayZ0Xg@mail.gmail.com>
2011-05-25 23:01 ` Nick Feamster
2011-05-25 23:23 ` Dave Taht [this message]
2011-05-25 23:30 ` Nick Feamster
2011-05-25 23:34 ` Dave Taht
2011-05-25 23:35 ` Nick Feamster
2011-05-26 9:34 ` Walter de Donato
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=xm34=ivr+oL62PA7h3VjWsPye6g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=feamster@cc.gatech.edu \
/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