I'm going to give a strong +1 here. In fact, can I inflate that to +100? As soon as something gets into Django itself then any improvements or API changes occur at a much slower pace. This is out of the necessity of providing a stable interface for developers. This becomes incredibly problematic when you need to have changes to reflect new developments in authentication and authorization. While things have currently 'stabilized' on OAuth 1 and OAuth 2, other systems may suddenly leap to the fore. In addition, major implementors of them (Twitter, Facebook, et al) are know to change things with little to no warning. Finally, there is always the risk of a security breach being discovered.
Putting this into contrib means that the community cannot quickly adapt to the changes in the authentication landscape. If Django had a faster release pattern that might not be a problem, but I'm not so sure about it. As for the Django Packages site, we've been slowly working on fixing some bugs and bitrot. Once we've gotten the priority items done we plan to implement a way to promote and demote packages which will make grids much more useful. We've had this request several times for security-related packages, database connectors, and other things. We're not sure about the API yet, but there you go. -- 'Knowledge is Power' Daniel Greenfeld Principal at Cartwheel Web; co-author of Two Scoops of Django; Maintainer of Django Packages cartwheelweb.com | pydanny.com | django.2scoops.org On Sunday, July 28, 2013 5:25:43 PM UTC+2, Aymeric Augustin wrote: > > > I have to disagree. The ecosystem of third-party packages is much more > instrumental to the success of Django than contrib apps (with the exception > of the admin). Blessing a solution stifles competition, hinders progress, > and makes it much harder for (possibly better) alternatives to emerge. > That's why the current trend is to slim down contrib. > > -- > Aymeric. > > -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers. For more options, visit https://groups.google.com/groups/opt_out.
