discuss: Modernization/Re-Design of Website
Subject:
Re: [discuss] Modernization/Re-Design of Website
From:
Borden Rhodes ####@####.####
Date:
23 Apr 2011 20:41:13 +0100
Message-Id: <BANLkTimBk_m=4BRQ6=jQHY2rpfntkvhJxQ@mail.gmail.com>
Sorry for that interlude, everyone. I hope you found it entertaining
but let's try to keep the bullying under control.
I know that the original thread was to discuss artwork but beautifying
the site isn't going to help much if there's nothing for that pretty
artwork to present. One of the problems I think the LDP has is in
carving out a niche. A lot of the wikis are hardware specific and/or
grossly outdated. Perhaps we're best to leave driver and hardware
configuration howto to the driver writers? I think external linking
in this case would make the most sense (although, in my experience,
driver documentation leaves a lot to be desired and might need LDP
supplements).
Secondly, most distros provide fairly decent documentation about their
respective quirks. I know that Debian often rewrites the upstream
documentation because they package things (like exim) such that the
default documentation doesn't work. So, perhaps it's not necessary
for us to maintain distro-specific documentation unless, of course, it
applies on a general level. Hence, we can simply drop the 'Fedora' or
'Debian' label in howtos.
There's also niche documentation like the
Avr-Microcontrollers-in-Linux-Howto recently submitted. It makes
sense to me to give these kinds of howtos a home where they'd
otherwise get lost in Google searches and/or archived on sites like
The Gadgeteer. I don't know. That's just my thinking.
I currently use Wikipedia to learn about general concepts like udev,
ext4 vs. reiserfs, gstreamer vs. xine, etc. Perhaps the LDP could
take a greater role in these sorts of conceptual topics? The biggest
problem I have is in trying to figure out which technology has
succeeded another technology. I think to new Linux users this is the
biggest source of confusion (since it was for me) and I'd often get
forum replies to the effect of 'yeah, that package you're trying to
use isn't maintained anymore. You're looking for...' The other area
I think the LDP could use a greater emphasis is on solving common
problems or explaining the man pages to commonly-used application -
all of which I turn to Google for right now.
Just some thoughts. Rick, please make good on your promise to be 'way
past dealing with' me and don't respond unless you have something
helpful to say AND can word it nicely.
With thanks,
Borden
