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 > 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. >
This approach sounds a lot better than just booting it from the repo. Regards, Michael Manfre -- 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.
