dhellmann / google-highly-open-participation-psf

Automatically exported from code.google.com/p/google-highly-open-participation-psf
0 stars 0 forks source link

Find new terms for the Python documentation's glossary and cross-link them #160

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The Python documentation for 2.6 and 3.0 has a glossary which aims to
explain common, Python-specific or otherwise important terms used in
the documentation.

See http://docs.python.org/dev/glossary.html for the 2.6 glossary.

Look at the glossary and decide which additional terms would be good
to explain here. Explain them in one or two sentences, maybe referring
to other glossary entries in turn.

Then, search through the rest of the documentation for the new terms
and, where appropriate, add a ":term:" role to them in order to create
a link to the glossary.

Completion:

Attach the results of an 'svn diff' (context diff) against the Python
source tree to this task, and send a brief description of your changes
to the ghop-python mailing list.

Relevant wiki pages:

 - DocumentationAndExampleGuidelines
 - WorkingOnDocumentation

Task duration: please complete this task within 5 days (120 hours) of claiming 
it.

Original issue reported on code.google.com by the.good...@gmail.com on 27 Nov 2007 at 4:11

GoogleCodeExporter commented 9 years ago
I'll claim this.

Original comment by jeffwheeler on 1 Dec 2007 at 6:35

GoogleCodeExporter commented 9 years ago

Original comment by the.good...@gmail.com on 1 Dec 2007 at 6:39

GoogleCodeExporter commented 9 years ago
Hey,

I’ve attached a diff from the current Python svn.  Can you give some feedback 
whether this is what you're looking 
for, or whether you're looking for considerably more terms?

Thanks

Original comment by jeffwheeler on 2 Dec 2007 at 8:26

Attachments:

GoogleCodeExporter commented 9 years ago
Yes, this is exactly what I've had in mind. The number of new material is quite
enough to mark this task as Completed. I'll apply some minor corrections and 
commit
the changes to SVN soon. Congratulations!

Original comment by georg.br...@gmail.com on 2 Dec 2007 at 2:44