<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">Netalyzr is currently not NSF-funded at all. Even if it were, such<br></span><span style="font-size:12.8px">funding doesn't imply open-sourcing of code in any way.</span></blockquote><div><br></div><div>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.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Thanks,</div><div>--MM--<br><span style="font-size:small">Matt Mathis Home & Travel voice: 412-654-7529 SMS and Daytime: 650-417-3029</span><br>-------------------------------------------<br>Evil is defined by mortals who think they know "The Truth" and use force to apply it to others. <br></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Jan 3, 2018 at 10:01 AM, Christian Kreibich <span dir="ltr"><<a href="mailto:christian@icir.org" target="_blank">christian@icir.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 01/03/2018 04:07 AM, Brian J. Murrell wrote:<br>
> Is it open source? That could go a long way to making an otherwise<br>
> doomed project self-sustaining.<br>
<br>
</span>I hear you Brian, but unfortunately that view is simplistic. Running an<br>
open-source project well takes significant cycles to sustain<br>
communication, documentation, support, etc. Also, sourcing/managing<br>
high-quality contributions can be a real challenge. We know this very<br>
well, since we're already running large open-source projects, such as<br>
the Bro network monitor.<br>
<span class=""><br>
> If it's not open source, why isn't it,<br>
<br>
</span>It's not currently open source, but we have repeatedly handed out code<br>
and data to interested collaborators at our discretion. We didn't<br>
open-source our code for several reasons, including the additional<br>
resource drain it would entail, and the fact that we did not want to be<br>
in the API maintenance business to allow other parties to build tests<br>
against our back-ends.<br>
<br>
In retrospect, I agree that perhaps we should have, but that's easy to<br>
say once a project is successful. You'll be happy to hear that once we<br>
complete the JavaScript-driven version, we will be open-sourcing both<br>
intentionally and as a side-effect of using that language.<br>
<span class=""><br>
> particularly when it's being<br>
> developed at a non-profit center for research in computer science at an<br>
> .edu?<br>
<br>
</span>Indeed, our mission is fundamental research, so please judge us by the<br>
success of our papers, not the availability of our code. Our projects<br>
have anywhere from zero to complete compatibility with open-source<br>
development, and we structure them accordingly. We are actually one of<br>
the most open-source-supportive research groups I can think of.<br>
<span class=""><br>
> Not to mention it's at least partial government (IOW, taxpayer)<br>
> funded (NSF as one).<br>
<br>
</span>Netalyzr is currently not NSF-funded at all. Even if it were, such<br>
funding doesn't imply open-sourcing of code in any way.<br>
<br>
Best,<br>
-C.<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
Netalyzr mailing list<br>
<a href="mailto:Netalyzr@mailman.ICSI.Berkeley.EDU">Netalyzr@mailman.ICSI.<wbr>Berkeley.EDU</a><br>
<a href="http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/netalyzr" rel="noreferrer" target="_blank">http://mailman.ICSI.Berkeley.<wbr>EDU/mailman/listinfo/netalyzr</a><br>
</div></div></blockquote></div><br></div>