> Great idea. The problem will be balancing the need to cover basics for > beginners, and perhaps written for a non-technical audience, with some > structure that allows people to click in to see more detail and > increasing complexity where they have an interest. > > I recommend people work on an outline of topics covered first, and then > choose from the wealth of sources between list archives, how-tos, etc. > for material to rewrite and incorporate with an eye toward constency, > style, and the intended audience. > > And there is a project for documentation, which may already have a lot > of this hashed out. No sense in re-inventing or competing here. See > http://fedora.redhat.com/projects/docs/ > > Have fun contributing. I think beginner's documentation is a great idea. > > Chris True Chris My linux foray was to get reliability into some work servers, but that might not be what everyone wants to acheive, they might just want to experiment with it on the desktop. So we may very well be pitching to different requirements right from the word go, but the overall picture/sentiment is it's for someone starting from scratch. Which was why I did the dog eared book reference. So the audience for the helpful leg up is going to be quite varied. I totally agree with your sentiment, funnily enough I was reading an article today where people with skills expect people to know already by dishing the keywords about or not going into greater depth than doing an off the cuff curt RTFM email reply which helps nobody. Everyone starts somewhere. I guess they just don't pick up on the blank stares! I quite agree with you in that it needs links going into greater depth if that's what they're after. Getting the list of topics might be a bit of a head scratcher though! I guess you really do have to ask new users or find out somehow what the usual requirements are. Anyways I'll do some more head scratching... Bryan
