From christian at icir.org Tue Jan 2 15:58:20 2018 From: christian at icir.org (Christian Kreibich) Date: Tue, 2 Jan 2018 15:58:20 -0800 Subject: [Netalyzr] hello, two things please In-Reply-To: References: Message-ID: Hi Steve, On 12/21/2017 12:04 PM, Steve H. wrote: > 1- Is the Netalyzr project still active ? Yes, although Cole's suspicion that some of the original authors have moved on is indeed correct. We're currently working on migrating the web-based version of Netalyzr over to a pure JavaScript version. We're hoping to release this version in the second half of the year. > 2- Will the Android app ever get fixed ? It seems to be broken. > See here for comments: > https://play.google.com/store/apps/details?id=edu.berkeley.icsi.netalyzr.android This is the tricky part -- we're currently severely short-staffed for Android development. Thanks for flagging the comments. We do actually read them! Things may look better in the second half of the month. Fingers crossed. > Thank you very much. This project is very cool, and hopefully will never > die. Thank you so much for the praise. We agree -- in our opinion Netalyzr should be a self-sustaining project, but unfortunately we've so far been unable to arrange the project's future accordingly. All best, Christian From brian at interlinx.bc.ca Wed Jan 3 04:07:09 2018 From: brian at interlinx.bc.ca (Brian J. Murrell) Date: Wed, 03 Jan 2018 07:07:09 -0500 Subject: [Netalyzr] hello, two things please In-Reply-To: References: Message-ID: <1514981229.16207.5.camel@interlinx.bc.ca> On Tue, 2018-01-02 at 15:58 -0800, Christian Kreibich wrote: > > This is the tricky part -- we're currently severely short-staffed > for > Android development. There is a solution to this problem... > Thank you so much for the praise. We agree -- in our opinion > Netalyzr > should be a self-sustaining project, but unfortunately we've so far > been > unable to arrange the project's future accordingly. Is it open source? That could go a long way to making an otherwise doomed project self-sustaining. If it's not open source, why isn't it, particularly when it's being developed at a non-profit center for research in computer science at an .edu? Not to mention it's at least partial government (IOW, taxpayer) funded (NSF as one). b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: This is a digitally signed message part Url : http://mailman.ICSI.Berkeley.EDU/pipermail/netalyzr/attachments/20180103/97316215/attachment.bin From christian at icir.org Wed Jan 3 10:01:43 2018 From: christian at icir.org (Christian Kreibich) Date: Wed, 3 Jan 2018 10:01:43 -0800 Subject: [Netalyzr] hello, two things please In-Reply-To: <1514981229.16207.5.camel@interlinx.bc.ca> References: <1514981229.16207.5.camel@interlinx.bc.ca> Message-ID: On 01/03/2018 04:07 AM, Brian J. Murrell wrote: > Is it open source? That could go a long way to making an otherwise > doomed project self-sustaining. I hear you Brian, but unfortunately that view is simplistic. Running an open-source project well takes significant cycles to sustain communication, documentation, support, etc. Also, sourcing/managing high-quality contributions can be a real challenge. We know this very well, since we're already running large open-source projects, such as the Bro network monitor. > If it's not open source, why isn't it, It's not currently open source, but we have repeatedly handed out code and data to interested collaborators at our discretion. We didn't open-source our code for several reasons, including the additional resource drain it would entail, and the fact that we did not want to be in the API maintenance business to allow other parties to build tests against our back-ends. In retrospect, I agree that perhaps we should have, but that's easy to say once a project is successful. You'll be happy to hear that once we complete the JavaScript-driven version, we will be open-sourcing both intentionally and as a side-effect of using that language. > particularly when it's being > developed at a non-profit center for research in computer science at an > .edu? Indeed, our mission is fundamental research, so please judge us by the success of our papers, not the availability of our code. Our projects have anywhere from zero to complete compatibility with open-source development, and we structure them accordingly. We are actually one of the most open-source-supportive research groups I can think of. > Not to mention it's at least partial government (IOW, taxpayer) > funded (NSF as one). Netalyzr is currently not NSF-funded at all. Even if it were, such funding doesn't imply open-sourcing of code in any way. Best, -C. From matt.mathis at gmail.com Wed Jan 3 11:03:25 2018 From: matt.mathis at gmail.com (Matt Mathis) Date: Wed, 3 Jan 2018 11:03:25 -0800 Subject: [Netalyzr] hello, two things please In-Reply-To: References: <1514981229.16207.5.camel@interlinx.bc.ca> Message-ID: > > Netalyzr is currently not NSF-funded at all. Even if it were, such > funding doesn't imply open-sourcing of code in any way. As of a few years ago, many (most?, all?) NSF programs have explicit open source requirements. This was not the case prior to about 2004. Thanks, --MM-- Matt Mathis Home & Travel voice: 412-654-7529 SMS and Daytime: 650-417-3029 ------------------------------------------- Evil is defined by mortals who think they know "The Truth" and use force to apply it to others. On Wed, Jan 3, 2018 at 10:01 AM, Christian Kreibich wrote: > On 01/03/2018 04:07 AM, Brian J. Murrell wrote: > > Is it open source? That could go a long way to making an otherwise > > doomed project self-sustaining. > > I hear you Brian, but unfortunately that view is simplistic. Running an > open-source project well takes significant cycles to sustain > communication, documentation, support, etc. Also, sourcing/managing > high-quality contributions can be a real challenge. We know this very > well, since we're already running large open-source projects, such as > the Bro network monitor. > > > If it's not open source, why isn't it, > > It's not currently open source, but we have repeatedly handed out code > and data to interested collaborators at our discretion. We didn't > open-source our code for several reasons, including the additional > resource drain it would entail, and the fact that we did not want to be > in the API maintenance business to allow other parties to build tests > against our back-ends. > > In retrospect, I agree that perhaps we should have, but that's easy to > say once a project is successful. You'll be happy to hear that once we > complete the JavaScript-driven version, we will be open-sourcing both > intentionally and as a side-effect of using that language. > > > particularly when it's being > > developed at a non-profit center for research in computer science at an > > .edu? > > Indeed, our mission is fundamental research, so please judge us by the > success of our papers, not the availability of our code. Our projects > have anywhere from zero to complete compatibility with open-source > development, and we structure them accordingly. We are actually one of > the most open-source-supportive research groups I can think of. > > > Not to mention it's at least partial government (IOW, taxpayer) > > funded (NSF as one). > > Netalyzr is currently not NSF-funded at all. Even if it were, such > funding doesn't imply open-sourcing of code in any way. > > Best, > -C. > _______________________________________________ > Netalyzr mailing list > Netalyzr at mailman.ICSI.Berkeley.EDU > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/netalyzr > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/netalyzr/attachments/20180103/78782da8/attachment.html From christian at icir.org Wed Jan 3 12:59:56 2018 From: christian at icir.org (Christian Kreibich) Date: Wed, 3 Jan 2018 12:59:56 -0800 Subject: [Netalyzr] hello, two things please In-Reply-To: References: <1514981229.16207.5.camel@interlinx.bc.ca> Message-ID: <00f64cd8-16c2-7285-04b0-3a12a12da91e@icir.org> Hi Matt, On 01/03/2018 11:03 AM, Matt Mathis wrote: > As of a few years ago, many (most?, all?) NSF programs have explicit open > source requirements. This was not the case prior to about 2004. Could it be that you mean the requirement for a _data_ management plan in NSF proposals? We're not aware of any requirements regarding open-sourcing code in our NSF projects. Best, -C. From matt.mathis at gmail.com Wed Jan 3 14:32:10 2018 From: matt.mathis at gmail.com (Matt Mathis) Date: Wed, 3 Jan 2018 14:32:10 -0800 Subject: [Netalyzr] hello, two things please In-Reply-To: <00f64cd8-16c2-7285-04b0-3a12a12da91e@icir.org> References: <1514981229.16207.5.camel@interlinx.bc.ca> <00f64cd8-16c2-7285-04b0-3a12a12da91e@icir.org> Message-ID: It could be different for different divisions and years: My experience was CISE during about 1996-2010. Since CISE is specifically about computing technology they probably care more about code than data. Other divisions may be different in this regard. I recall being required to state which licences for at least one proposal. Thanks, --MM-- Matt Mathis Home & Travel voice: 412-654-7529 SMS and Daytime: 650-417-3029 ------------------------------------------- Evil is defined by mortals who think they know "The Truth" and use force to apply it to others. On Wed, Jan 3, 2018 at 12:59 PM, Christian Kreibich wrote: > Hi Matt, > > On 01/03/2018 11:03 AM, Matt Mathis wrote: > >> As of a few years ago, many (most?, all?) NSF programs have explicit open >> source requirements. This was not the case prior to about 2004. >> > > Could it be that you mean the requirement for a _data_ management plan in > NSF proposals? We're not aware of any requirements regarding open-sourcing > code in our NSF projects. > > Best, > -C. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/netalyzr/attachments/20180103/34624abe/attachment.html