On Fri, Mar 8, 2013 at 12:48 AM, Jacob Kaplan-Moss <[email protected]>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.
>

+1 to trimming comments from contrib.

However, I'd argue against using /dev/null as a disposal mechanism. I don't
think the code should ever completely disappear. If someone offers to take
over, that's great; but just because nobody volunteers to maintain the
project, doesn't mean nobody is using the code.

Keeping the code in our repo with a big "DEPRECATED - THIS CODE IS NOT
MAINTAINED" warning in the README (or maybe even a new "django-attic"
repository) means the code can live on. If someone wants to use it, they
can. If someone needs to make a minor tweak, they can fork the repo and
make that change without needing to commit to maintaining the project
publicly.

Yours,
Russ Magee %-)

-- 
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.


Reply via email to