[Python-Dev] The docs, reloaded [PEP?]

"Martin v. Löwis" martin at v.loewis.de
Thu May 24 23:09:17 CEST 2007

Michael Foord schrieb:
> This subject is generating a lot of discussion and [almost entirely] 
> positive feedback. It would be a great shame to run out of steam.
> Does it need a PEP to see a chance of it getting accepted as the formal 
> documentation system? (or a pronouncement that it will never happen...)

No. First of all, it needs a dedicated developer (preferably, but not
necessarily a committer) who indicates willingness to maintain that
for the coming years and releases. It might be that Fred Drake's offer
to maintain the documentation would be still valid after such a switch,
but we should not assume so without explicit confirmation. It might
be that this would be the time to pass one documentation maintenance
to somebody else (and I seriously do not have any one particular
in mind here).

Then, I think a should be made where the documentation is converted.
Again, a volunteer would be needed to create the branch, and then
eventually merge it back to the trunk. It might be helpful, but isn't
strictly necessary, to close all documentation patches before doing
so, as they all break with the conversion. For that activity,
multiple volunteers would be useful.

I don't think a formal document needs to be written, unless there
is a hint of disagreement within the community. In that case, a
process PEP would be necessary. However, it is much more important
that the documentation maintainer explicitly agrees than that
nobody explicitly disagrees, or that a pronouncement is made -
the pronouncement alone will *not* cause this change to be
carried out.


More information about the Python-Dev mailing list