From jkleint at gmail.com Thu Oct 1 06:19:35 2009 From: jkleint at gmail.com (John Kleint) Date: Thu, 1 Oct 2009 00:19:35 -0400 Subject: [Doc-SIG] Request for Eyeballs: Python Project Howto In-Reply-To: <6496ee60909241615g7d94d1bar68a3be14ec4598b9@mail.gmail.com> References: <6496ee60909241615g7d94d1bar68a3be14ec4598b9@mail.gmail.com> Message-ID: <6496ee60909302119k588e5dc2n97eaf9e3e3a5018e@mail.gmail.com> Thanks for the feedback. I've incorporated your suggestions. > You say you don't cover setuptools, but you do use easy_install... > Once the work Tarek Ziade is doing is more complete, both on distutils > and Distribute (setuptools replacement), it would be great to see the > HOWTO updated to cover them. Yeah; at the moment, easy_install seems to be the most common way to get Python packages, and distutils seems to be the simplest, most common way to create them. From what I gather the Python packaging landscape is in flux, but when there's a good replacement for distutils and easy_install, I'll be happy to include it. > Maybe move licensing to be nearer choosing a project host. > You often have to have already chosen a license when you choose > a host, so putting them together makes sense. I added a pointer to the license section at the beginning, but licensing can be a bit daunting and I don't want to scare anybody off too soon. :) > Mention Pyflakes and Pychecker when you mention Pylint? Check. > In testing resources you should link to the Python Testing Tools Taxonomy: > http://pycheesecake.org/wiki/PythonTestingToolsTaxonomy Wow - I had no idea there were so many testing tools for Python. > Please, when describing how to build the uploadable packages, as well > as setup.py sdist, add in a recommendation to build and upload > setup.py bdist_wininst. Thanks, I didn't know it was a pain for Windows users. I'm going to go make Windows installers for my own packages. -John From zstumgoren at gmail.com Sun Oct 11 18:34:55 2009 From: zstumgoren at gmail.com (Serdar Tumgoren) Date: Sun, 11 Oct 2009 12:34:55 -0400 Subject: [Doc-SIG] greetings from new volunteer and question about documentation needs Message-ID: Hi everyone! I'm new to the Python volunteer community, and another member suggested that helping out with documentation is a great way to get started. A bit of background on me: I'm a journalist who recently made the shift to full-time database work for Congressional Quarterly, a news organization based in Washington, D.C. I started dabbling with Python two years ago, and now have the good fortune to use it daily in my work. Python and its community have helped me enormously, so I figured it's time to give something back. I've started reading the style guide for documentation writers, but I wasn't able to dig up a list of projects or priorities that need doing. Is there such a list? If not, should we start one on the doc-sig page of the Python wiki? http://www.python.org/community/sigs/current/doc-sig/ For me, such a list would help focus my efforts on the genuine needs of the community. And it could help others who'd like to contribute but are not sure where to begin. So please let me know what you think about the idea of a priority list, or better yet, reply back with specific project ideas or needs. And of course, if such a list already exists, just point me to it. I'll be happy to help out. Regards, Serdar Tumgoren From grubert at users.sourceforge.net Mon Oct 12 08:55:42 2009 From: grubert at users.sourceforge.net (grubert at users.sourceforge.net) Date: Mon, 12 Oct 2009 08:55:42 +0200 (CEST) Subject: [Doc-SIG] Docutils 0.6 released Message-ID: Good morning, Release 0.6 is out. Changes are : * Two new writers for ODT and manpage (so there is no excuse for python software not having a manpage anymore). * Python2.2 is no longer supported. Release 0.6 is compatible with Python versions from 2.3 up to 2.6 and convertible to 3.1 code. * The "newlatex" writer is orphaned. * The LaTeX2e writer sports templates now and is the most active worked on part. There might be some suprises due to new defaults, but we tried to minimize breakage and choose sensible defaults. * The HTML writer supports a comma separated list of stylesheets. * Some changes to reStructuredText many thanks to all contributors. have a nice start into a new week. engelbert From ralf.gommers at googlemail.com Wed Oct 14 16:49:08 2009 From: ralf.gommers at googlemail.com (Ralf Gommers) Date: Wed, 14 Oct 2009 16:49:08 +0200 Subject: [Doc-SIG] greetings from new volunteer and question about documentation needs In-Reply-To: References: Message-ID: Hi Serdar, On Sun, Oct 11, 2009 at 6:34 PM, Serdar Tumgoren wrote: > Hi everyone! > > I'm new to the Python volunteer community, and another member > suggested that helping out with documentation is a great way to get > started. > > A bit of background on me: I'm a journalist who recently made the > shift to full-time database work for Congressional Quarterly, a news > organization based in Washington, D.C. I started dabbling with Python > two years ago, and now have the good fortune to use it daily in my > work. Python and its community have helped me enormously, so I > figured it's time to give something back. > > I've started reading the style guide for documentation writers, but I > wasn't able to dig up a list of projects or priorities that need > doing. Is there such a list? If not, should we start one on the > doc-sig page of the Python wiki? > There is no such list as far as I know, but almost any large Python project will welcome help with open arms. > > http://www.python.org/community/sigs/current/doc-sig/ > > For me, such a list would help focus my efforts on the genuine needs > of the community. And it could help others who'd like to contribute > but are not sure where to begin. > > So please let me know what you think about the idea of a priority > list, or better yet, reply back with specific project ideas or needs. > What you could do is ask on the mailing list of a project you are interested in / a user of. For me, I'm a scientist and therefore focused on contributing to NumPy and SciPy docs. For you it may be something related to databases? If you pick something you already enjoy using you will be able to contribute most effectively imho. Cheers, Ralf -------------- next part -------------- An HTML attachment was scrubbed... URL: From zstumgoren at gmail.com Thu Oct 15 01:42:37 2009 From: zstumgoren at gmail.com (Serdar Tumgoren) Date: Wed, 14 Oct 2009 19:42:37 -0400 Subject: [Doc-SIG] greetings from new volunteer and question about documentation needs In-Reply-To: References: Message-ID: Ralf, Many thanks for the response. I'm planning to take your advice and look for a project or two of interest. Something database-related would indeed be high on my list. Thanks again! Regards, Serdar