Hi Mike, To give you the advice you are looking for I would need to have an idea of what your project consists of. Sometimes, the subtleties related to inner-workings between different software/hardware modules or components may change your approach to licensing.
As such, you may create your open source license. After all, a license is a simple contract. A canned approach is not always better. Perhaps, you could let us know what is your project about? Regards, Paul ________________________________________ From: [email protected] <[email protected]> on behalf of Mike Dewhirst <[email protected]> Sent: Monday, August 11, 2014 7:58 PM To: [email protected] Subject: Re: OS license requirements Thanks Paul - no, Melbourne Australia Cheers Mike On 11/08/2014 10:42 PM, Paul Greenberg wrote: > Hi Mike, > > I will be able to help you out. Are you local to US? > > Best Regards, > Paul Greenberg, Esq. > > Law Office of Paul Greenberg > 530 Main Street, Suite 102 > Fort Lee, NJ 07024 > E-mail: [email protected] > Tel: 201-402-6777 > Fax: 201-301-8876 > Cell: 212-380-7343 > Web: http://www.greenberg.pro/ > Twitter: @nymetrolaw > > CONFIDENTIALITY NOTICE: The information contained in this email, including > any attachment(s), is confidential information that may be privileged and > exempt from disclosure under applicable law, and is intended only for the > exclusive use by the person(s) mentioned above as recipient(s). If you are > not the intended recipient, you are hereby notified that any disclosure, > copying, distribution, or use of the information contained herein is strictly > prohibited and may be unlawful. If you received this transmission in error, > please immediately contact the sender and destroy the material in its > entirety, whether in electronic or hard copy format. > > CONFIDENTIAL: ATTORNEY/CLIENT PRIVILEGED; ATTORNEY WORK PRODUCT The > information contained in this email is intended for the individual or entity > above. This email is protected by the Electronic Communications Privacy Act, > 18 U.S.C. Sections 2510-2521 and is legally protected by the attorney/client > privilege and/or work product doctrine. If you are not the intended > recipient, please do not read, copy, use, forward or disclose this > communication to others; further, please notify the sender by replying to > this message and then delete this message from your system. Thank you. > > ________________________________________ > From: [email protected] <[email protected]> on behalf > of Mike Dewhirst <[email protected]> > Sent: Sunday, August 10, 2014 8:34 PM > To: Melbourne Python Users Group; [email protected] > Subject: OS license requirements > > Apologies for cross-posting > > I'm getting near to open sourcing a Django project and have to choose an > appropriate license. Can anyone help me choose? > > I have settled on the following requirements ... > > 1. Project source must be freely available for end users to view and > download and modify and further distribute to others > > 2. But if user modified source is distributed the modified source must > be freely available for others to view and download and modify and be > subject to the identical license as the project source > > 3. However, if the user modified source is kept in-house and not further > distributed the changed source may be kept private or offered back to > the project as a patch at the whim of that user. > > 4. Project (and user modified) source may be combined with proprietary > software but the project (or user mofified) source component remains > subject to the same license. It cannot be distributed as a combined > whole under any other license than the project license. > > 5. But it can be distributed as a combined whole with proprietary > software provided the project (or user modified) source component is > freely available for end users to view and download and further > distribute to others under the project license even if the proprietary > component is not. > > BTW, Django doesn't require that my project use the Django license and > of course I won't be distributing Django. > > I'm leaning towards the LGPL but would appreciate feedback from anyone > with contrary views. > > Thanks > > Mike > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/53E80F97.8030008%40dewhirst.com.au. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/53E958A4.8080704%40dewhirst.com.au. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1407803467824.65449%40greenberg.pro. For more options, visit https://groups.google.com/d/optout.
