In addition to detailing how to do screenshots, we need to specify how to eliminate variables that are not common to a Fedora Core installation. For example, using a default, fresh user account prevents customizations in the author's ~/.bash* files such as additions to te $PATH. This "System Documenting Guidelines" would include best practices for technology usage, such as using rpm packages instead of tarballs. We might choose to have equal preferences for equivalent technologies, such as up2date and yum. A big reminder to include is to document the existing system, not provide "fixes" that make a system unsupportable, abnormal, or otherwise _more_ difficult to maintain. This would be a chapter or section.
This bug is ancient, and no longer seems applicable to me. In particular, because this has been assigned to me, it would need to apply to the Fedora Deployment Guide, which seems to cover what's listed here: file:///home/silas/repos/redhat/fedorahosted/Deployment_Guide/community/fc12/tmp/en-US/html-single/index.html#pt-pkg-management Any comments? If not, I will close this bug soon.
Because using rpms instead of tarballs, etc. is well-represented in the RPM Guide, and will be also in the upcoming Fedora Deployment Guide (and probably elsewhere too), I am closing this as NOTABUG. If there are further requests along this line, please create a new bug for them. Thanks.