From: Nick Feamster <feamster@cc.gatech.edu>
To: "Poole, Brian" <bpoole@cc.gatech.edu>
Cc: "bismark-users@lists.bufferbloat.net"
<bismark-users@lists.bufferbloat.net>
Subject: Re: [Bismark-users] coping with conflicts
Date: Tue, 15 Mar 2011 15:24:17 -0400 [thread overview]
Message-ID: <93D811CA-EA9E-4F1F-9157-AD5877AE99F1@cc.gatech.edu> (raw)
In-Reply-To: <FC2117C703F33143ACE5AAD34CF98FBCAD3DD0@aeatlgtrmbx01.gtri.ext>
I think that sharing the active measurements could be done without IRB issues, but we should double-check.
Another issue is that we want to publish on the data before other people. :-) So, perhaps releasing smaller samples early and the full data down the road (once papers get accepted) would be a good compromise?
-Nick
On Mar 15, 2011, at 3:19 PM, Poole, Brian wrote:
> Random follow-on as I've been chatting with Dave a bit in parallel on IRC as well. He mentioned getting a few things up on the shared site would help collaboration. The two biggies being our test script infrastructure and the raw data we collect.
>
> I don't imagine sharing the testing scripts would cause any big issues; it would be mostly just be logistics of getting it up/documented and deciding whether that becomes the authoritative development source.
>
> Sharing the raw data collected stuck out to me as a harder issue. Is that possible with the way previous studies have been run (ie, does the IRB cause headaches here) ?
>
> Brian
> ________________________________________
> From: bismark-users-bounces@lists.bufferbloat.net [bismark-users-bounces@lists.bufferbloat.net] on behalf of Nick Feamster [feamster@cc.gatech.edu]
> Sent: Tuesday, March 15, 2011 3:06 PM
> To: Dave Täht
> Cc: bismark-users@lists.bufferbloat.net
> Subject: Re: [Bismark-users] coping with conflicts
>
> On Mar 15, 2011, at 3:02 PM, Dave Täht wrote:
>
>>
>> One of the things in the upcoming writing queue is a string of articles
>> for the ACM, case studies. Would you be interested in that?
>>
>
> Yes, definitely.
>
>
>> Are there other publication targets?
>
> ACM Internet measurement conference (may deadline) ACM Sigmetrics (nov deadline) and ACM Sigcomm (jan deadline) seem like natural targets, too.
>
> -Nick
> _______________________________________________
> Bismark-users mailing list
> Bismark-users@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-users
> _______________________________________________
> Bismark-users mailing list
> Bismark-users@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-users
next prev parent reply other threads:[~2011-03-15 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 18:42 Dave Täht
2011-03-15 18:43 ` Srikanth Sundaresan
2011-03-15 18:47 ` Nick Feamster
2011-03-15 18:54 ` Dave Täht
2011-03-15 18:58 ` Nick Feamster
2011-03-15 19:02 ` Dave Täht
2011-03-15 19:06 ` Nick Feamster
2011-03-15 19:19 ` Poole, Brian
2011-03-15 19:24 ` Nick Feamster [this message]
2011-03-15 19:31 ` Srikanth Sundaresan
2011-03-15 20:08 ` Nick Feamster
2011-03-16 8:37 ` Walter de Donato
2011-03-15 20:31 ` Dave Täht
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=93D811CA-EA9E-4F1F-9157-AD5877AE99F1@cc.gatech.edu \
--to=feamster@cc.gatech.edu \
--cc=bismark-users@lists.bufferbloat.net \
--cc=bpoole@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