<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm not sure if anyone got back to Giorgio on this. I am sure he
would appreciate this group's thoughts.<br>
<br>
Thanks,<br>
Patrick<br>
<br>
<div class="moz-forward-container"><br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>[Osi] [General enquiries] Type of License and Keylock</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Tue, 27 May 2014 19:35:13 +0000 (UTC)</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:giorgio@sommaruga.org">giorgio@sommaruga.org</a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:osi@opensource.org">osi@opensource.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Giorgio Sommaruga (<a class="moz-txt-link-abbreviated" href="mailto:giorgio@sommaruga.org">giorgio@sommaruga.org</a>) sent a message using the contact
form at <a class="moz-txt-link-freetext" href="http://opensource.org/contact">http://opensource.org/contact</a>.
My team is developing a project in business area.
The software is developed in two segment.
A first segment is a basic version of software with an Open Source license,
but we don't want to allow to modify the code and then resell it. We want to
allow changes only for personal use.
And second segment is based over the basic version but with other proprietary
code, for example for more other functions or add-ons.
We want to enable our partners to modify the software and sell it, but only
with our authorization and acquiring the rights of the changes.
Furthermore we would like to combine the software with a hardware protection,
at least for the "business" but if possible also for the "Open" segment.
This, at least to keep track of who is using the software.
As an alternative for the Open segment, we would like to force the user to
register the software in order to receive an activation code.
Is this possible in the context of OSI licenses and which one?
Thanks in advance.
Sincerely
Giorgio Sommaruga
Report as inappropriate:
<a class="moz-txt-link-freetext" href="http://opensource.org/mollom/report/mollom_content/140527e8b62565508a">http://opensource.org/mollom/report/mollom_content/140527e8b62565508a</a>
_______________________________________________
Osi mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Osi@opensource.org">Osi@opensource.org</a>
<a class="moz-txt-link-freetext" href="http://projects.opensource.org/cgi-bin/mailman/listinfo/osi">http://projects.opensource.org/cgi-bin/mailman/listinfo/osi</a>
</pre>
<br>
</div>
<br>
</body>
</html>