On Sat, 2005-09-03 at 07:30 +0400, Miles Brennan wrote: G'day. Nice, long holiday weekend here in the States, just getting around to some email. :) Excellent. Glad we drew you out. I haven't read all the way through, so this is a preliminary overview. 0. Thank you for bringing this here, we are very interested in working with you to get this into Fedora Documentation. 1. Great work. Very useful. Covers -lots- of common topics we have no documentation for. This project will benefit greatly from the inclusion of this guide. 2. A small book this size would benefit from more help; I'd be concerned that maintenance by yourself would be tiring. Recruit help? 3. Fedora docs focuses on solutions found only in Core and Extras; if there are solutions you choose outside of those, we would want them changed to Fedora-only solutions. We can reference other solutions in a stand-alone chapter, if you don't want to totally kill the content. I haven't finished reading through yet, so I have no examples, _if_ they exist. 4. Small style changes, throughout. For example, consistent use of the active ("Click OK and a dialog opens") v. passive ("When you click on OK, then a dialog will open"). We like the active voice, it engages the reader with what they actually experience. We expect most folks to do the task with the documentation present, so what they see is not what they -will- see but what the -are- seeing. ;-D Another example is changing the pronouns from first-person plural ("we") to second-person singular/plural ("you"). I'll be happy to explain these style choices further, if anyone needs. IMO, this is more of a guide than a how-to. It's definitely in the how-to format, but it is really a full length book/guide. Once it has chapters, it's a book. :) What do you want to do: 1. Maintain sole authorship, under the FDP 2. Lead a team of writers, under the FDP 3. Toss over the wall to the FDP, let us recruit writers and editors to continue your work Option 3 is the one we try to avoid. I recommend option 2. It keeps you in charge of the document, as the lead writer. As for the CVS parts, that is much easier than you think. Easier than learning to use DocBook, and much easier than the concepts you cover in this guide. A first step is to work with an editor to convert the guide to use the FDP DocBook template and style. The we can publish it for FC3. We can also recruit interested writers to work on sections to update to FC4, unless you are able to do that yourself. Content and concept are easy to keep together. Normally, we would have written up each chapter as a stand-alone document, then tie them all together. This comes prepackaged, which is fantastic. Our only changes would be minor formatting via the stylesheets and XML choices we make, and writing style. The latter, btw, focuses partially on making it easier to translate by reducing idioms, etc. Hello! Welcome, this was quite a nice self-introduction. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/

Miles Brennan wrote: While I found your tutorial at <http://www.brennan.id.au/01-Introduction.html> interesting, and will study it at greater length, it wasn't entirely clear to me who it was aimed at. What exactly is a "home server"? What would be a typical configuration for such a beast? Are we talking about a home LAN with a couple of machines on it? Or is it basically a model to practise on for larger systems? This isn't meant as a criticism - just that a few words describing the kind of setup in question might be useful in the introduction. -- Timothy Murphy e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Timothy Murphy wrote: I think the initial narrative on the index page explains it quicker and a little better that chap 1; the home user. http://www.brennan.id.au/02-Planning_Considerations.html#topology Bingo. Infact, many of the configurations could quite easily be used for larger scale networks (concepts are most the same). That's ok, we can wordsmith any of these types of areas so they do make more sense. Cheers, Miles