Installation Guide TODO list

[Paul W. Frields]

On Tue, 2005-01-25 at 13:01 +0000, Stuart Ellis wrote:
> On Tue, 25 Jan 2005 03:08:24 -0800 (PST), "Rahul Sundaram"
> <rahulsundaram at yahoo.co.in> said:
> >
> > ok. how about you doing the branch now and adding a
> > todo for it adding notes on whats expected to change.
> > I am actively following the fedora development tree
> > (running rawhide) and lists (discussions on fedora
> > extras, xen and what not) so I might be able to cover
> > up the intial stuff necessary for getting a fc4 guide
> > ready for the release.
> 
> The best thing to do is look at the TODO list in the tarball, which is
> essentially the roadmap (as I see it).  A branch is feasible at 0.9
> (test release to fedora-list).
> 
> The easy way to see what "0.9" means is to grep through the Installation
> Guide FIXMEs and ignore the appendices, because we can drop them and
> still have a useful document.  You will see:
> 
> - 2 sections to be written (Paul Frields has offered to tackle "Disk
> Partitioning").
> - About three TECHQUERYs in the main text (Mayank is looking at these).
> - Screenshots (see separate discussions, I've made the masters and am
> unsure how to handle the EPS).
> 
> When these are resolved one way or another we can ship 0.9 to the
> fedora-list.  At that point we have a publically available document and
> can start making noise at about it. I intend to ask for people to come
> in and help with 64-bit and PPC right from the initial post.  With a
> visible document the FDP could also make a case for developers to become
> involved in technical review for 1.0.

Speaking of which, I have started work on the Disk Partitioning section,
but discovered that my way of tackling it was, to be blunt, stupid. I
decided to make the actual Disk Partitioning chapter purely about the
mechanics of installation, and refer the reader to an additional
appendix which would explain disk geometry and how to understand
partitioning (how it works, and how to design partitioning for a
particular system).

This means that I have to mark significant sections of the parts I'm
writing with a conditional that qualifies them for "x86" architecture
only. Can anyone remind me of the means for doing so in DocBook/XML?
Feel free to respond offlist, otherwise I'll just search the archives
when I have time, assuming the search engine actually works. :-)

I did a crummy job of estimating my time the last few weeks; work has
demanded more of my hours than I expected, so the progress is slow. But
I will redouble my efforts this week.

For anyone who cares, please also note my new email address. The
frields.com domain owners shut the doors to their hosting business
December 31st, and did not notify me. They still own the domain but it
doesn't "do" anything for the time being. If you sent me anything since
mid-December, and you have the ability, you may want to resend.

-- 
Paul W. Frields, RHCE