> Hosting "docs.python.org/devguide/jython" doesn't seem like an
> unreasonable idea at all to me, and what's the benefit to CPython in
> making the Jython team go to the effort of building out independent
> deployment and source control infrastructure for their own devguide?

We can *host* (in the Web hosting sense) the jython devguide. That
certainly doesn't mean it belongs in the same piece of documentation.

Our devguide was created to explain how to contribute to the CPython
project. Creating a Jython section only makes things messier than they
are, and it certainly doesn't help our users.

Really, I'm sure setting up a crontab and creating an hg repo is easy
enough for the Jython people (or whoever wants to help them in that
matter).

> wiki.python.org is already shared between the two projects, and
> pydotorg hosts the Jython source control infrastructure in addition to
> CPython's.

Providing infrastructure is not the same as sharing the development
resources themselves. We don't share the (CPython) hg repo, and we don't
share the (CPython) bug tracker. There's no reason to share the
(CPython) devguide, not until the two projects merge together.

(as for the wiki... well, suffice to say that it's a terrible mess and I
hope it's not an example for the devguide. If the wiki was actually
useful and practical we wouldn't have made the devguide a separate site,
I guess)

> More generally, given that we now provide cross-links to PyPy, Jython
> and IronPython from the download pages, it also seems reasonable to
> provide pointers to their own "get involved" resources from the
> CPython devguide.

We already provide pointers from the devguide:
http://docs.python.org/devguide/#other-interpreter-implementations
It's only a matter of changing the URLs if these projects ask us to.