On Thursday, March 7, 2013 10:18:11 PM UTC+5:30, Jacob Kaplan-Moss 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.
[snipped]
> Any objections?
>
As the student (back then) who worked on
On Fri, Mar 8, 2013 at 12:38 AM, Jacob Kaplan-Moss wrote:
> On Thu, Mar 7, 2013 at 5:55 PM, Russell Keith-Magee
> wrote:
>> 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 gre
Yep. +1
Val
Sent from my mobile device.
On 2013-03-07, at 11:48 AM, Jacob Kaplan-Moss 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 a
+1
Cheers,
Thiago Avelino
On Fri, Mar 8, 2013 at 10:19 AM, Richard Bronosky wrote:
> Yes. Aymeric, you covered every point I wanted to make.
>
> Sent from my Samsung Galaxy S3 using the Swype software keyboard.
> --Richard Bronosky
> On Mar 7, 2013 12:00 PM, "Aymeric Augustin" <
> aymeric.au
Django should have a boneyard. Here is the homebrew boneyard
https://github.com/Homebrew/homebrew-boneyard
Sent from my Samsung Galaxy S3 using the Swype software keyboard.
--Richard Bronosky
On Mar 7, 2013 7:39 PM, "Jacob Kaplan-Moss" wrote:
> On Thu, Mar 7, 2013 at 5:55 PM, Russell Keith-Magee
Yes. Aymeric, you covered every point I wanted to make.
Sent from my Samsung Galaxy S3 using the Swype software keyboard.
--Richard Bronosky
On Mar 7, 2013 12:00 PM, "Aymeric Augustin" <
aymeric.augus...@polytechnique.org> wrote:
> On 7 mars 2013, at 17:48, Jacob Kaplan-Moss wrote:
>
> > This on
Sorry, but -1 from me.
Given the core premise that the job of a web application framework is to
find the common features that many websites need to implement and make them
easy to achieve, commenting definitely fits into this category.
I run two sites that use Django comments heavily. Django c
+1
Sent from my Windows Phone
From: Jacob Kaplan-Moss
Sent: 3/7/2013 5:48 PM
To: django-developers
Subject: Proposal: deprecate and remove django.contrib.comments
Hi folks --
This one's simple: I'd like to deprecate `django.contrib.comments`,
scheduling it to be removed in a couple of releases.
On Thu, Mar 7, 2013 at 5:55 PM, Russell Keith-Magee
wrote:
> 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,
It's not like /dev/null'ing it erases it from the annals of history. I
don't see what the point of creating an un-maintained repo is, if someone
decides they want to maintain it at some later point it's pretty trivial to
resurrect from VCS history.
Alex
On Thu, Mar 7, 2013 at 4:29 PM, Michael Ma
On Thursday, March 7, 2013 1:05:53 PM UTC-5, Alex Ogier wrote:
>
> 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
>
On Fri, Mar 8, 2013 at 12:48 AM, Jacob Kaplan-Moss 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 som
On Thu, Mar 7, 2013 at 12:41 PM, Luke Granger-Brown wrote:
> 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)
i had exactly the same experience.
--
Javier
--
You r
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
wo
+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 wrote:
> I think i can maintain comments if you want the t
Jumpin' on the +1 train.
Choo, choo!
Alex
On Thu, Mar 7, 2013 at 9:04 AM, Donald Stufft wrote:
> On Mar 7, 2013, at 11:48 AM, Jacob Kaplan-Moss wrote:
>
> > Hi folks --
> >
> > This one's simple: I'd like to deprecate `django.contrib.comments`,
> > scheduling it to be removed in a couple of r
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 <
aymeric.augus...@polytechnique.org> wrote:
On Mar 7, 2013, at 11:48 AM, Jacob Kaplan-Moss 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 some
On 7 mars 2013, at 17:48, Jacob Kaplan-Moss 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 D
A good idea, +1.
четверг, 7 марта 2013 г., 22:48:11 UTC+6 пользователь Jacob Kaplan-Moss
написал:
>
> 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 mu
On 03/07/2013 09:48 AM, Jacob Kaplan-Moss wrote:
> 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
21 matches
Mail list logo
