That seems entirely reasonable, but if it is the convention, I wasn't aware
of it - sorry.  The ticket got some relatively quick traction just in trac.

This goes to the heart of defining the purpose, current and future, of
contrib.

I believe in shrinking in contrib - but I do think it has to be done
mindfully.

There was some *brief* conversation at DjangoCon about phasing
contrib.markup out in a fashion similar to localflavor - but it seemed to
end unresolved in a discussion of submodules, namespace, and other
imperfect solutions.

On this issue of markup I do think the answer should lie in a strong 3rd
party option.

 I agree we could provide better migration docs and maybe we shouldn't do
an accelerated deprecation to give a better migration option the chance to
be developed?

-Preston