On Mar 7, 2013, at 11:48 AM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote:
> Hi folks -- > > This one's simple: I'd like to deprecate `django.contrib.comments`, > scheduling it to be removed in a couple of releases. > > 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. > > Practically, I'd do this by deprecating `django.contrib.comments` in > 1.6. We'd immediately stop making any changes to it (except for > security or data loss issues). It'd stay deprecated in 1.7, and would > be removed in 1.8. > > 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. > > Any objections? > > Jacob > > -- > 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 django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > +1 -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
