On 06/28/2013 03:01 PM, Alireza Mahdian wrote:
[...]
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.
Hi Alireza,
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:
[email protected] <mailto:[email protected]>
[email protected] <mailto:[email protected]>
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.
-Jonathan
--
Too many emails? Unsubscribe, change to digest, or change password by emailing
moderator at [email protected] or changing your settings at
https://mailman.stanford.edu/mailman/listinfo/liberationtech
