On Tue, Sep 29, 2009 at 5:34 PM, Jonas Obrist <ojiido...@gmail.com> wrote: > > Hi django-users > > I have a question about the license Django is released under (BSD). Or > to be more precise about: > > 3. Neither the name of Django nor the names of its contributors may > be used > to endorse or promote products derived from this software without > specific prior written permission. > > I've take then code from django.db and stripped it off any need of > anything else in django and done other changes so that it can be used > for non-django purposes (I plan to use it in EventScripts projects). I'm > really bad at naming my projects so I just wanted to name it djangodb. > However then I read the license of Django more closely and I'm not sure > if I'm allowed to do so. Is using 'Django' as part of my module's name > 'endorse or promote' my derived product?
First off - IANAL, so the following lawyering is non-professional opinion, and doesn't constitute legal advice, etc etc. My reading of this is that yes, what you are proposing would be a violation of the license. You're forking Django to produce a new product, and then want to leverage the Django name to promote and give visibility to your product. Even if it doesn't violate the letter of the license on some technicality, IMHO it certainly violates the spirit of the license. However, completely aside from the legality is the necessity. What is it that prevents you from using the standard Django install in a non-web project? I've used Django's libraries in non-web tools, but I didn't need to fork Django in order to do so. If you really do need a separate library, why start a forked project? Why not try to do this within the Django project itself? You're not the first person to say that it should be possible to use parts of Django in isolation - the template system and the database library are common candidates for this - but this is the first time I recall anyone volunteering to do the actual work. It seems a pity to fork an entire project just so you can use a small part of it - especially when you haven't asked if we're interested in pursuing the idea. What sort of modifications did you need to make? Did you need to modify any source files, or is this just a matter of deleting irrelevant directories and files? Could this be handled using a distutils configuration? > Also I don't quite get the term 'Redistributions in binary form' since > basically any redistribution in a digital way is binary. My project will > be open source, does that mean I have to ship it with the BSD license or > can I leave it away? The term "binary" is referring to the difference between "binary" and "source" - that is, a compiled executable, as opposed to a source distribution. In the Python world, this distinction is a little bit unusual, since most code distribution is as source. However, it is possible to use tools like py2app or py2exe to produce binary versions of Python code, so this clause isn't completely irrelevant. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
