On 7 mars 2013, at 17:48, Jacob Kaplan-Moss <[email protected]> wrote:
> This one's simple: I'd like to deprecate `django.contrib.comments`, > scheduling it to be removed in a couple of releases. +1 > My rationale is this: if you don't really care much about how comments > work but just want something easy, then Disqus (and its competitors) > are easier to use and have much better features (spam prevents, > moderation, etc.). If you want something complex and specific, on the > other hand, you're better off writing something from scratch. The mere existence of django.contrib.comments implies that it's the sanctioned way to add comments to a Django application, but in 2013 it's most likely not going to be the right answer. Leaving it in contrib is a disservice to many developers using Django. Even www.djangoproject.com stopped using d.c.comments in 2009. > If someone volunteers to maintain it as an external project I'll move > the code to a new repo and direct people there in the docs. If nobody > volunteers, then it'll go to the great /dev/null in the sky. Even if no one volunteers to maintain it, I'd still consider putting it on life support somewhere under github.com/django. The goal is to provide an easier upgrade path for maintainers of websites currently using it. Otherwise we'll have people stuck at the last version of Django that still contains d.c.comments. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
