Last Week: ========== Deployment Guide + Trac Page Up: https://fedorahosted.org/deploymentguide + Cleaned ids + Removed unused images + Updated PO files
Security Guide + Trac Page Up: https://fedorahosted.org/securityguide
Next Week: ========== + Get BZ components up + More general cleaning + Integrate with new version of publican + More entity clean up + Populate Security Guide files
About $subject ...
The generic "Linux ... Guide" titles cover a lot of ground.
I don't really imagine any of us covering other Linuxes, though. It's clearly outside of the Fedora Docs purview.
Naturally we can just set the scope of the book to use Fedora as the canonical example. But there seems clear room for brand confusion. Wouldn't a Linux Security Guide be about Linux and not just Fedora et al?
General question for the list and specifically for Michael:
Should these be "Fedora ... Guide" instead?
Thanks - Karsten
Karsten 'quaid' Wade wrote:
About $subject ...
The generic "Linux ... Guide" titles cover a lot of ground.
I don't really imagine any of us covering other Linuxes, though. It's clearly outside of the Fedora Docs purview.
Naturally we can just set the scope of the book to use Fedora as the canonical example. But there seems clear room for brand confusion. Wouldn't a Linux Security Guide be about Linux and not just Fedora et al?
General question for the list and specifically for Michael:
Should these be "Fedora ... Guide" instead?
Thanks - Karsten
I think this doc will nicely cover fedora, centOS, Red Hat Enterprise Linux, Scientific Linux, and Oracle Enterprise Linux. That surely enough scope for the generic title.
On Fri, 2008-08-29 at 13:20 +1000, Christopher Curran wrote:
I think this doc will nicely cover fedora, centOS, Red Hat Enterprise Linux, Scientific Linux, and Oracle Enterprise Linux. That surely enough scope for the generic title.
Fair point about generic title. 'Linux' seems a little far-reaching, I'm not sure we can get that generic to cover even other RPM-based distros (OpenSUSE, Mandriva for examples.)
Clearly an upstream decision; just saying from the sideline. What we do for the Fedora Security Guide in building from the upstream won't have any brand or command confusion. :) Just hoping it's closest to using pristine source in those builds. ;-D
Thanks - Karsten