On Tue, Aug 12, 2014 at 1:43 AM, Mike Dewhirst <mi...@dewhirst.com.au> wrote: > Cross posting again to thank everyone for responding ... > > I'm going with LGPL. > > Oliver suggested I consider Mozilla Public License and part of a > stackexchange conversation goes [1] ... > >> The major difference is how MPL / LGPL licensed code must be linked >> into the project. MPL source code files can be directly copied into a >> (possibly) proprietary software project (static linking), while LGPL >> licensed code must be dynamically linked (loosely linked to the >> possibly proprietary software project, so that end-users can switch >> out the licensed software library for another version of the licensed >> software library). > > > ... but in the context of Python running in a server (IANAL) I can't see > "linking" being applicable to the point where it would prevent the real > objective of ensuring my source (modified or not) is available for the end > user of the whole work. Running on someone else's server makes it moot and > on the end-user's server it is fait accompli.
Affero GPL covers this. Bear in mind that each license that adds protection also adds restrictions and reduces the potential number of users. I love BSD licensed software, it is easy to integrate in to all projects. LGPL software is usable in less projects, GPL in even less, and Affero GPL is so restrictive I tend to rule it out without consideration. > > Russ suggested staying within the big five and that was why I was leaning > towards LGPL anyway. My thought was about who might be interested in helping > if the license is breached. MSF or FSF? I assume FSF because that is their > entire mission. > I very much doubt either of them would be particularly interested beyond publicising the alleged breach for you. As the license holder, responsibility for enforcement would belong to you. Cheers Tom -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/CAFHbX1JSX_pMbAVCcmiyzVABvdbhvEJp-59A5Uuv4XmDJXa5Vw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
