discuss: Some ideas for TLDP
Subject:
Re: Some ideas for TLDP
From:
"J. S. Evans" ####@####.####
Date:
9 Jan 2016 18:21:44 +0000
Message-Id: <6064498.O9EfyhCuFK@localhost.localdomain>
On Saturday, January 09, 2016 07:07:13 PM Daniel Pocock wrote:
> On 09/01/16 18:59, jdd wrote:
> > Le 09/01/2016 13:18, J. S. Evans a écrit :
> >> Hi all,
> >>
> >> Where is TLDP today? Looking at the site, I see some really good
> >> information
> >> and a lot of info that is plainly outdated.
> >
> > as far as I now, LDP is mostly dead. Nowadays most people writes docs on
> > they own blog...
> >
> >> - Move away from DocBook 4 to something a little more modern and
> >> preferably
> >> user friendly like LyX.
> >
> > LyX, modern :-)) - it's the first text processor I used ten years ago
> >
> > :-) (not to say it's bad) and AFAIR it can export to docbook.
> >
> > And we have the wiki for people wanting to use easy to write interface
> >
> >> in years. Some going back to 2008 and before. TLDP is an amazing
> >> idea, why
> >> aren't we utilizing it for it's maximum value?
> >
> > because too few people care...
>
> That is a little too coarse
>
> - today, most people are always online, so they search for stuff in
> Google rather than a book. In the early days of LDP, many people were
> still on dial-up modems and they would download documentation to read later.
>
> - many things change quickly making books outdated, just look at init
> systems for Linux, or all the things we've had for managing /dev
>
> That said, people still need some books, usually for information that is
> more long lasting. People won't volunteer to write a detailed book
> about an API that will be obsolete in two years though.
I also don't think people would be too interested in writing a detailed book,
but maybe a chapter or even just a few lines that could help steer a reader in
the right directions. I think this is where we could begin.
>
> Regards,
>
> Daniel
>
> ______________________
> http://lists.tldp.org/
