I think it can't just disappear. Even if you can't find a maintainer, core should put at least a little effort to make sure that an API compatible third-party application exists that is compatible at least through version 1.8 when "import django.contrib.comments" stops working (basically, do the work ourselves to make sure that it doesn't rely on undocumented internals and can be cleanly split). Then, if it's not maintained, it can fester and stop being compatible with new Django versions or whatever. If it's really not important enough to anyone that it can stay modern outside of core, then it will die, but we should make it a trivial matter to fork and adopt for whoever needs it.
Anyways, +1 from me. Best, Alex Ogier On Thu, Mar 7, 2013 at 12:41 PM, Luke Granger-Brown <[email protected]>wrote: > +1 from me too - I've only tried using django.contrib.comments once, and > it ended up not being what I needed anyway, so I had to write my own > comments module (Disqus was out of the question) > > > On Thu, Mar 7, 2013 at 5:11 PM, Carlos Aguilar <[email protected]>wrote: > >> I think i can maintain comments if you want the time you need. >> >> I only use few zinnia blogs, then, is not really important to me, but I >> suppose it is important for many others developers. >> >> Best Regards >> >> >> On Thu, Mar 7, 2013 at 11:00 AM, Aymeric Augustin < >> [email protected]> wrote: >> >>> 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. >>> >>> >>> >> >> >> -- >> Carlos Aguilar >> Consultor Hardware y Software >> DWD&Solutions >> http://www.dwdandsolutions.com >> http://www.houseofsysadmin.com >> Cel: +50378735118 >> USA: (301) 337-8541 >> >> -- >> 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. >> >> >> > > -- > 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. > > > -- 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.
