RE: Python Tutorial 2.0 (addemendum)

[Gregory Leblanc <GLeblanc cu-portland edu>]

> -----Original Message-----
> From: battery841@mypad.com [mailto:battery841@mypad.com]
> Sent: Tuesday, June 13, 2000 9:49 AM
> To: Gregory Leblanc
> Subject: Re: Python Tutorial 2.0 (addemendum)
> 
> 
> > Anybody who writes code that's of good enough quality to go 
> into the Linux
> > kernel is a member of the "Kernel Team".  The exact same 
> type of thing
> > applies here.  What I meant was, write your docs, and 
> submit them using the
> > LDP guidelines, TO the LDP.  I didn't mean to separate 
> anybody, since I'm on
> > this list, the OSWG list, the LDP list, the SAMBA docs 
> list, and probably a
> > whole slew of others that I can't remember.  :-)  But these 
> documents are
> > not appropriate to GNOME unless they apply to GNOME, 
> running on ANY OS.
> > GNOME is not Linux specific, thus the documentation cannot be Linux
> > specific.  Now, assuming that there is a GNOME PPP 
> application that works on
> > any OS with PPP support, then document this application.  
> If you want to
> > have a step-by-step tutorial of how to use GNOME PPP to get 
> a PPP connection
> > on Linux, and it requires some things that are strictly 
> Linux specific, then
> > it shouldn't be part of the GNOME documentation.  I'm sure 
> that somebody
> > will disagree with me here, and say that we should have it 
> not only for
> > Linux, but also for Solaris, AIX, HPUX, SCO, etc.  I don't 
> think that's the
> > right way to do it, but I do acknowledge that it is a 
> possibility.  Later,
> > 	Greg
> Greg,
> 	Okay, this e-mail I will agree with more than the other 
> one.  I think though that we should take LDP docs and have 
> Nautilus as a front-end for them.  This would require that a 
> lot more LDP docs were written (thats good) and it'll keep 
> away documentation fragmentation (I love that term :).

Almost time to do some real work here, but...  There's no reason not to make
the new help browser a good front-end for the LDP.  So far, I don't know
what things need to be done to docs to make them work with this new help
browser, and I don't know what the help browser would have to do to be happy
with the LDP docs.  If somebody can compile a list of requirements that
documents must fill to work in this new help-browser, and send it to me or
the LDP list, I'd be most appreciative.  If the people who are writing the
help browser make it work with LDP docs, AWESOME!  Later,
	Greg