<div dir="ltr">Utkarsh is right.<div><br></div><div>-berk</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 7, 2013 at 1:46 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">AFAIK, including the ParaView license and mentioning somewhere in your<br>
documentation/web-pages that it's based on ParaView Superbuild is<br>
sufficient. But I'll let Berk respond with the official answer.<br>
<span class="HOEnZb"><font color="#888888"><br>
Utkarsh<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, Aug 7, 2013 at 1:10 PM, Joshua Murphy<br>
<<a href="mailto:Joshua.Murphy@lasp.colorado.edu">Joshua.Murphy@lasp.colorado.edu</a>> wrote:<br>
> Hello,<br>
><br>
> I am new to the whole open-source model of doing things, and I have a<br>
> question:<br>
><br>
> If I were to use the ParaView Superbuild CMake code as a base for<br>
> building my plugin toolkit, how should I go about attributing it?<br>
><br>
> Thanks,<br>
> Josh<br>
> _______________________________________________<br>
> Paraview-developers mailing list<br>
> <a href="mailto:Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><br>
> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</div></div></blockquote></div><br></div>