docs December 2005

docs@lists.fedoraproject.org

13 participants
25 discussions

Minutes of FDSCo Meeting Dec 6 2005
by Stuart Ellis 06 Dec '05

06 Dec '05

Attending: --------- Karsten Wade (quaid) Tommy Reynolds (megacoder) Paul Frields (stickster) Stuart Ellis (elliss) Regrets: -------- Gavin Henry (G2) Tammy Fox (tcf) - leave of absence Schedule of Tasks: ------------------ http://www.fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule Highlights: ----------- * Karsten: The content of the Fedora site at redhat.com has been revised: http://fedora.redhat.com/ * Karsten: Work has begun on enabling the FOP system to run on open source Java platforms. Once this work is complete, the FDP may integrate FOP into the toolchain to enable PDF generation. For more technical details, see the Apache Wiki: http://wiki.apache.org/xmlgraphics/GnuClasspathCompatibility PDF generation with FOP is not expected to be live before the release of Fedora Core 5. * Karsten: A discussion on future enhancements to DocsRawhide will be started on the fedora-docs-list. DocsRawhide shows HTML versions of the documents in the FDP CVS, automatically updated every hour: http://webtest.fedora.redhat.com/docs/ Full IRC Log: ------------- https://www.redhat.com/archives/fedora-dsco-list/2005-December/msg00002.html -- Stuart Ellis stuart(a)elsn.org Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ GPG key ID: 7098ABEA GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA

1 0

Self-Introduction: Chad Sellers
by Chad Sellers 02 Dec '05

02 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, my name is Chad Sellers. I currently live in Columbia, MD, USA. I work for Tresys Technology as a software developer focused on security. I've been working on SELinux projects for a couple of years now, so I would like to help with the Fedora SELinux FAQ. My Fedora CVS username is csellers. GPG info: pub 1024D/0260F126 2005-12-02 Key fingerprint = 83DE 0CE7 C659 F74D 8FEA 0DA5 BFF3 424B 0260 F126 uid Chad Sellers <csellers(a)tresys.com> sub 4096g/F1BFB58B 2005-12-02 Thanks, Chad - -- - ---------------------- Chad Sellers Tresys Technology, LLC csellers(a)tresys.com http://www.tresys.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDkHd8v/NCSwJg8SYRAs29AJ0QKwBwETV4bM8Qn+/jWKPRyyfEIgCfWDuc QloyyzmDbrKRt/NJc55S8kA= =Jy3f -----END PGP SIGNATURE-----

2 1

Re: [ANN] Draft Document Rendering
by Tommy Reynolds 02 Dec '05

02 Dec '05

Uttered James Laska <jlaska(a)redhat.com>, spake thus: Please keep this on the list, thanks. > Not sure if that was intentional or not, but I think the file paths > might be incorrect for the html-nochunks path. The HTMLCSS and > HTMLCSSEXTRA are being copied to the DOCBASE-$(1)/ and not the pwd. > I filed bug#174805 to address that. Ah, the perils of cut'n paste. "I hate meeses to pieces" Japan doesnt't call me nogui-san for nothing ;-) Fixed in CVS. Cheers

1 0

{RFC] XSLT for draft watermarking?
by Paul W. Frields 01 Dec '05

01 Dec '05

Both <book> and <article> in DocBook support a CDATA attribute called "status". (I.e., <book status="published"> or something like that.) Does this mean we could have XSLT do the work of deciding which stylesheet to use, without having to have a new "make" target? When the work is approved, the author or editor can add this attribute to the top of their doc, and the next build fixes the make. If you want to dream really big like Karsten, then think of that status attribute being manipulated by a XML/XSLT capable shell script that is part of a Larger Automated Process. For example, when the doc is published, it gets branched and the branch gets the status="published" tag, whereas HEAD keeps the default draft. Is this possible? -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/

5 9

Re: help with the SELinux FAQ
by Karsten Wade 01 Dec '05

01 Dec '05

On Thu, 2005-12-01 at 10:23 -0500, Chad Sellers wrote: > We definitely want to make sure that many of the changes (move to reference > policy/policy v2, move to managed policy, move to policy modules, etc.) get > into the FAQ. Let me know what I can do to help. The main thing is to review the current content and make the following changes: * Remove out-of-date information * Update FAQs to reflect current reality * Add new content The best and fastest way to do this is directly in the XML in CVS. The FAQ is written in DocBook, and is very straightforward. If you haven't written in DocBook before, it is about 10% more difficult than HTML, and 100% more rewarding. To set this up, go through this page ... you want to follow the steps in "Signing Up". The most important step is 4., where you sign up for CVS access. "Submitting Your Own Documentation" covers the details of using DocBook and CVS in this project. http://fedoraproject.org/wiki/DocsProject/NewWriters If you cannot take that route, people in the Fedora Documentation Project can take your changes and incorporate them ourselves. For simplicity sake, I recommend that you use a plain text output of the FAQ to edit. We can then run a diff against another plain text output, and manually make the changes in the XML. Here is a plain text output of the latest (1.3-8): http://people.redhat.com/kwade/fedora-docs/selinux-faq-en-1.3-8.txt The next version starts at 1.5, as I've been using the minor release to indicate which version of Fedora Core this version of the FAQ relates to. Thanks very much for your interest, - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs December 2005