Russell Keith-Magee wrote: > > 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? >
Thanks for your view on this. Just to make on thing clear: I don't want to promote or make my product 'visible'. The main reason I want to keep django in it's name is so people don't credit me for the work... The reason I forked this project is that I want it to be able to use in ESP (EventScripts Python, see http://python.eventscripts.com/). To do this I needed to allow multiple databases (connections) to use the lib, on cost of this I dropped all engine support but sqlite3. Further it should be easily usable without any other django part (especially django.conf). Anyway unless someone else comes up with a plausible answer I probably have to think of another name... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
