<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">An OSI approved license is fine with me.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Historical note – the original Berkeley license had a fourth clause in it that required acknowledging UCB in any advertising. This was a sore point within
the open source community. So Berkeley modified the license to remove the advertising clause. This modified license is known as the “Modified Berkeley” or “Modified BSD” license, or in some circles the “New BSD License”, and is the one that OSI approved.
In 2008, the OSI board approved a variant which they call the “Simplified BSD License”, which is essentially the same as what historically has been called the “Modified BSD” license. So we are talking about the same thing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Some people remove the third cause (the “no endorsement” clause), which is allowed by OSI. I would prefer if we leave it in.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">In fact some people (e.g. the caBIG® community) do not feel that the third clause goes far enough. They feel that one should mention trademarks, and not
just the name of the copyright holder (i.e., that the software license is not a license to use the copyright owner’s trademarks). Some of the other OSI licenses have such trademark clauses (e.g. the Apache V2.0 license).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Also some people (e.g. the caBIG® community) feel that a patent clause is needed. Some of the other OSI licenses have such patent clauses (e.g. the Apache
V2.0 license, the Mozilla 1.1 license, CDDL, the Eclipse Public License 1.0).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Although I am relatively neutral, in some ways I would prefer the Apache license over the Berkeley license. The Apache license is closer to the caBIG® Model
License Agreement that we were required to use for the initial XIP development. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I definitely do not want to use a GPL license, or any license that has a viral (sometimes called “copyleft”) provision, though I have no problem with utilizing
LGPL code if accessed solely as a library.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Lawrence<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Will Schroeder [mailto:will.schroeder@kitware.com]
<br>
<b>Sent:</b> Thursday, November 12, 2009 10:27 AM<br>
<b>To:</b> Tarbox, Lawrence<br>
<b>Cc:</b> Marco Viceconti; ctk-developers@commontk.org<br>
<b>Subject:</b> Re: [Ctk-developers] Qt licenses model<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Maybe this wasn't clear, but if possible use a OSI-compliant license, not a modified BSD. This makes it possible to seek funding or respond to technology requests (since I believe an OSI-compliant license can
be a pre-condition to engagement, it also gives a sense of authoratative approval which warms some people's hearts). We thought about gaining OSI approval for VTK's original license but eventually just adopted a standard BSD.<br>
Will<o:p></o:p></p>
<div>
<p class="MsoNormal">On Thu, Nov 12, 2009 at 10:00 AM, Tarbox, Lawrence <<a href="mailto:tarboxl@mir.wustl.edu">tarboxl@mir.wustl.edu</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">I think the reason that the Qt Software folks (now owned by Nokia) left the GPL option in is for the benefit of some of their partners who were writing GPL code (or dual-licensed GPL/Commercial code) back in the days when Qt Software was
TrollTech. Some of those partners have made additions/modifications to Qt, released them under GPL, and do not want to ever release them under LGPL. While technically they could still release their additions/modifications under GPL even though Qt is LGPL
(i.e., LGPL allows it), these partners prefer to keep their licensing straight forward, and just say the whole combined mess is GPL. Qt Software is merely saying formally that Qt Software is OK with that model, basically reaffirming their partners' right
to continue releasing modified versions of Qt under GPL.<br>
<br>
At least that is the impression that I get.<br>
<br>
I don't think that there is a problem with release our software under a modified BSD license, as long as we are only linking to Qt, and not modifying Qt code directly (i.e., one could switch to a Qt clone, if it existed, or to a modified version of Qt by simply
rebuilding against a different link library).<br>
<br>
If we do modify the Qt code itself, then those modifications would have to be released as LGPL. Of course, if we modify Qt itself, I would vote for feeding those modifications back to the Qt community for potential incorporation into a future release of Qt.<br>
<br>
Lawrence<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
-----Original Message-----<br>
From: <a href="mailto:ctk-developers-bounces@commontk.org">ctk-developers-bounces@commontk.org</a> [mailto:<a href="mailto:ctk-developers-bounces@commontk.org">ctk-developers-bounces@commontk.org</a>] On Behalf Of Marco Viceconti<br>
Sent: Thursday, November 12, 2009 3:44 AM<br>
To: <a href="mailto:ctk-developers@commontk.org">ctk-developers@commontk.org</a><br>
Subject: [Ctk-developers] Qt licenses model<br>
<br>
I would like to open another discussion thread, parallel to the one we<br>
started on Qt core. Currently Qt is available under two possible open<br>
source licenses: Qt GNU LGPL v. 2.1 and Qt GNU GPL v. 3.0.<br>
<a href="http://qt.nokia.com/products/licensing" target="_blank">http://qt.nokia.com/products/licensing</a><br>
<br>
If I understand correctly the code is the same, the access rules are<br>
the same, so I am not sure why one would choose GPL which is more<br>
restrictive than LGPL. Can someone clarify this to me?<br>
<br>
Secondly, having agreed that CTK will be BSD-like, can anyone confirm<br>
me that by using a LGPL library to develop CTK we shall not break the<br>
BSD-like license we plan to adopt?<br>
<br>
Thanks<br>
<br>
Marco<br>
<br>
<br>
<br>
--------------------------------------------------<br>
MARCO VICECONTI, PhD<br>
(<a href="mailto:viceconti@tecno.ior.it">viceconti@tecno.ior.it</a>)<br>
Laboratorio di Tecnologia Medica tel. 39-051-6366865<br>
Istituto Ortopedico Rizzoli fax.<br>
39-051-6366863<br>
via di Barbiano 1/10, 40136 - Bologna, Italy<br>
<br>
Tiger! Tiger! Burning bright in the forest of the night,<br>
what immortal hand or eye could frame thy fearful symmetry?<br>
--------------------------------------------------<br>
Opinions expressed here do not necessarily reflect those of my employer<br>
<br>
<br>
<br>
_______________________________________________<br>
Ctk-developers mailing list<br>
<a href="mailto:Ctk-developers@commontk.org">Ctk-developers@commontk.org</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">The material in this message is private and may contain Protected Healthcare Information (PHI). If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on
the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">_______________________________________________<br>
Ctk-developers mailing list<br>
<a href="mailto:Ctk-developers@commontk.org">Ctk-developers@commontk.org</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
William J. Schroeder, PhD<br>
Kitware, Inc.<br>
28 Corporate Drive<br>
Clifton Park, NY 12065<br>
<a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a><br>
<a href="http://www.kitware.com">http://www.kitware.com</a><br>
(518) 881-4902<br>
<br>
<o:p></o:p></p>
</div>
<br>
<hr>
<font face="Courier New" color="Black" size="3">The material in this message is private and may contain Protected Healthcare Information (PHI). If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of
any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.<br>
</font>
</body>
</html>