Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread Laura Creighton
In a message of Mon, 29 Aug 2005 14:16:36 EDT, "A.M. Kuchling" writes: >On Mon, Aug 29, 2005 at 07:38:15PM +0200, Laura Creighton wrote: >> want to bother him personally about a personal page. If they were >> on python.org I would have sent my 'wish you had explained this >> better' bit and my exa

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread Laura Creighton
In a message of Mon, 29 Aug 2005 14:03:39 EDT, "Fred L. Drake, Jr." writes: >On Monday 29 August 2005 13:38, Laura Creighton wrote: > > I had a small problem with reg-exp how to the other day. > > what decided me against report it to amk was the idea that I didn't > > want to bother him personally

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread A.M. Kuchling
On Mon, Aug 29, 2005 at 07:38:15PM +0200, Laura Creighton wrote: > want to bother him personally about a personal page. If they were > on python.org I would have sent my 'wish you had explained this > better' bit and my example of how to for sure. Really? Hm, I should add a paragraph that encour

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread Ian Bicking
A.M. Kuchling wrote: >>I note that for the "What's New" document you like to retain >>authorship rather than succumb to group maintenance. I'd like that >>not to be the case for the howtos, especially since the starting >>documents come from a variety of contributors. > > > It's a fair point, bu

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread Fred L. Drake, Jr.
On Monday 29 August 2005 13:38, Laura Creighton wrote: > I had a small problem with reg-exp how to the other day. > what decided me against report it to amk was the idea that I didn't > want to bother him personally about a personal page. If they were > on python.org I would have sent my 'wish

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread A.M. Kuchling
On Mon, Aug 29, 2005 at 01:30:02PM -0400, Fred L. Drake, Jr. wrote: > How about this: Create Doc/howto/ as part of the main checkout, so > the howtos come along with the rest of the docs. This addresses > your motivations, regardless of how the howtos get formatted or > published. We can deal wit

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread Laura Creighton
In a message of Mon, 29 Aug 2005 13:30:02 EDT, "Fred L. Drake, Jr." writes: >On Monday 29 August 2005 09:28, A.M. Kuchling wrote: > > Actually they're on amk.ca now. People find them pretty well -- type > > "regular expression" into Google and the HOWTO is the top hit; it's > > the second hit for

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread Fred L. Drake, Jr.
On Monday 29 August 2005 09:28, A.M. Kuchling wrote: > Actually they're on amk.ca now. People find them pretty well -- type > "regular expression" into Google and the HOWTO is the top hit; it's > the second hit for "regular expressions". I'd have no objection to > moving them to python.org ho

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-29 Thread A.M. Kuchling
On Sun, Aug 28, 2005 at 11:26:14PM -0400, Fred L. Drake, Jr. wrote: > I'm fine with this, but we should probably figure out a better way to deal > with publishing them. Using SourceForge for this hasn't been the most > successful spot, I suspect. Actually they're on amk.ca now. People find the

Re: [Doc-SIG] Creating howto directory in Python CVS

2005-08-28 Thread Fred L. Drake, Jr.
On Sunday 28 August 2005 21:46, A.M. Kuchling wrote: > I'd like to (finally) check in the HOWTOs into the main Python CVS; > I've begun writing new ones like the Unicode HOWTO, and it would be > good if more people had access to them. I'm fine with this, but we should probably figure out a bett

[Doc-SIG] Creating howto directory in Python CVS

2005-08-28 Thread A.M. Kuchling
I'd like to (finally) check in the HOWTOs into the main Python CVS; I've begun writing new ones like the Unicode HOWTO, and it would be good if more people had access to them. Since they probably won't be added to the documentation set, they should go in nondist/ in CVS. nondist/howto/ seems to