<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/28/2013 03:01 PM, Alireza Mahdian
wrote:<br>
<br>
[...]<br>
<br>
</div>
<blockquote
cite="mid:3464940A-220D-4AFB-A1A4-34DD7332B061@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>To answer John: As I mentioned in an earlier post I have done
this protect myself from any liability if someone modifies the
code rendering it a malware. I may publish the service layer
code independently under a different license where anyone can
modify it as they want to. However I do understand your point.</div>
</blockquote>
<br>
Hi Alireza,<br>
If you get a free moment, I'd highly recommend emailing your
concern to either or both of the FSF (Free Software Foundation) and
the SFLC (Software Freedom Law Center). I've found they are both
very quick to advise on licensing issues, very knowledgeable, and
can give you detailed information that you can use to hopefully find
a better solution than adding your own terms to the Apache license.
They are both very friendly organizations and can probably also
recommend other resources for you on this issue:<br>
<br>
<a href="mailto:info@fsf.org">info@fsf.org</a><br>
<br>
<a href="mailto:help@softwarefreedom.org">help@softwarefreedom.org</a><br>
<br>
I advise doing this because a license that does not look standard is
a non-starter for building a community around your software (or even
for people building something else using your ideas). I'm convinced
that if you take a modicum of time to communicate your concerns to
these organizations they can help you arrive at a licensing scheme
that does exactly what you want without hindering a potential
development community.<br>
<br>
-Jonathan<br>
</body>
</html>