Re: QManager - suggested inclusion in Django
On Thu, Jul 17, 2008 at 10:01 AM, Waylan Limberg <[EMAIL PROTECTED]> wrote: > > On Thu, Jul 17, 2008 at 6:46 AM, zvoase <[EMAIL PROTECTED]> wrote: >> >> Dear Developers, >> I've written a module which may be helpful to a lot of Django >> developers, and would like to suggest it for trials and testing, and >> possible inclusion with Django. > > Well, for starters, it appears to be licensed under the GPL while > Django had a BSD license. As long as the conflict exists, your changes > of inclusion are pretty slim, I would think. A general plea to everyone working on Django extensions: if you have any inclination towards eventually seeing your code merged into Django itself, *please* don't release it under a restrictive "share-alike" (to use the CC turn of phrase) license. If Django wants to remain BSD-licensed, it can't accept such code. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: QManager - suggested inclusion in Django
On Thu, Jul 17, 2008 at 6:46 AM, zvoase <[EMAIL PROTECTED]> wrote: > > Dear Developers, > I've written a module which may be helpful to a lot of Django > developers, and would like to suggest it for trials and testing, and > possible inclusion with Django. Well, for starters, it appears to be licensed under the GPL while Django had a BSD license. As long as the conflict exists, your changes of inclusion are pretty slim, I would think. Either way, don't get your hopes up for inclusion any time soon. Everyone is currently working to get 1.0 out the door and this is not a show stopper for that (it doesn't break backward compatibility of the API - just adds new stuff) so I doubt the core devs will even consider it until after 1.0. In the meantime, review the points on contributing [1] in the docs, continue to maintain your code as separate code and prove your worth as a reliable maintainer. [1]: http://www.djangoproject.com/documentation/contributing > I'm currently just looking for > developers to help test and work with the module; it should be quite > helpful. It certainly looks interesting. Perhaps I'll play with it if I get a chance. > It's also heavily documented - *everything* has a docstring. I hope > you enjoy, I'll say. What, less that 50 lines of code in a 500+ line document? Wow. -- Waylan Limberg [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: QManager - suggested inclusion in Django
> In summary, it is called 'QManager', and is a Manager subclass which > helps developers create Managers from Q objects. QManager instances > can be joined by & and |, and by using the negative operator you can > create a QManager which is the complement of the original. Whether included in core or not, I think it's a very nice idea. Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
