Re: [stdlib-sig] MISC/maintainers.txt anyone?
In a message of Wed, 16 Sep 2009 10:04:00 +0200, Georg Brandl writes:
Hey, I got another idea! What about we simply add a second set of docs, f or developers?
We have lots of information scattered throughout the website, the source and the heads of important people (the most volatile sort), that, put together, should make a nice set of docs that could be collected (and mad e a sphinx tree).
Georg
I really like this idea, which also accomplishes the goal of making the python development process more transparent to non-core-developers. This, of course, assumes that you would let us read such a thing. Is that a fair assumption? Laura
Laura Creighton schrieb:
In a message of Wed, 16 Sep 2009 10:04:00 +0200, Georg Brandl writes:
Hey, I got another idea! What about we simply add a second set of docs, f or developers?
We have lots of information scattered throughout the website, the source and the heads of important people (the most volatile sort), that, put together, should make a nice set of docs that could be collected (and mad e a sphinx tree).
Georg
I really like this idea, which also accomplishes the goal of making the python development process more transparent to non-core-developers. This, of course, assumes that you would let us read such a thing. Is that a fair assumption?
Yes, certainly -- all the resources are public now, and the new thing would be in the source checkout, and I'd set up a regular build as for the docs, e.g. at http://devdocs.python.org/. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.
participants (2)
-
Georg Brandl
-
Laura Creighton