Hi
Fedora docs are linked from the story line. Useful thing to keep in mind that we are constantly serving a bigger audience
http://ask.slashdot.org/askslashdot/07/04/18/2312218.shtml
Rahul
On Fri, 2007-04-20 at 06:40 +0530, Rahul Sundaram wrote:
Hi
Fedora docs are linked from the story line. Useful thing to keep in mind that we are constantly serving a bigger audience
FWIW, I've heard consistent interest ... for about three years ... from across various distros ... to find a way for us all to work from some kind of common base.
OTOH, Spot (and others) have reminded me that the differences between distros outweigh the similarities.
Maybe ... maybe we need to coordinate with other distros to put a common front-end on TLDP to allow us all to update it, and use it as a common docbase? We can use any content that is GPL, afaik, although it's not our preferred license for documentation. The majority of TLDP is still GPL, right?
- Karsten
Karsten Wade wrote:
OTOH, Spot (and others) have reminded me that the differences between distros outweigh the similarities.
That is not a problem for some of the documentation like basic server side sys administration guides.
Maybe ... maybe we need to coordinate with other distros to put a common front-end on TLDP to allow us all to update it, and use it as a common docbase? We can use any content that is GPL, afaik, although it's not our preferred license for documentation. The majority of TLDP is still GPL, right?
GPL? You mean GNU FDL. TLDP licensing is a bit of mess but I would guess that the important docs are under GNU FDL which I believe is incompatible with Open Publication License.
Rahul
On Fri, 2007-04-20 at 07:33 +0530, Rahul Sundaram wrote:
Karsten Wade wrote:
OTOH, Spot (and others) have reminded me that the differences between distros outweigh the similarities.
That is not a problem for some of the documentation like basic server side sys administration guides.
We'd still need a full analysis to see if it was worth it. It could be that 20% or 50% or 80% of the content could be shared.
Maybe ... maybe we need to coordinate with other distros to put a common front-end on TLDP to allow us all to update it, and use it as a common docbase? We can use any content that is GPL, afaik, although it's not our preferred license for documentation. The majority of TLDP is still GPL, right?
GPL? You mean GNU FDL. TLDP licensing is a bit of mess but I would guess that the important docs are under GNU FDL which I believe is incompatible with Open Publication License.
:( Bummer ...
http://www.tldp.org/LDP/LDP-Author-Guide/html/doc-licensing.html
Because authors retain copyright and choose their own license, there isn't going to be a way that e.g. LDP could multi-license content. So that pretty much lets us out of the running.
FWIW, I'm glad. I don't like the GNU FDL. It's a PITA to administrate, I believe the lawyers who tell me it doesn't give enough protection, and it definitely seems contradictory to the GPL. It's too bad the CC BY-SA doesn't include warranty protection ...
- Karsten
Hi,
Maybe ... maybe we need to coordinate with other distros to put a common front-end on TLDP to allow us all to update it, and use it as a common docbase?
Has docbook something like ifdef ?
introdcution theory bladibladibla
#ifdef fedora text text text #idef ubuntu text text text #idef gentoo text text text
blablabla
So a
make fedora
would produce the manuals in Fedora oder Ubuntu flavor ?
Another problem I hit several times is to keep various languages in sync. If you don`t see excatly what changed in the original-document, it`s near to impossible.
So keeping the documentation per chapter or even smaller in a cvs would help.
cu romal
A belated follow-up that has been sitting on my desktop ...
On Sat, 2007-04-21 at 22:45 +0200, Robert M. Albrecht wrote:
Has docbook something like ifdef ?
Yes, although the exact mechanism for XML escapes my ability to recall at the moment.
So a
make fedora
would produce the manuals in Fedora oder Ubuntu flavor ?
Right. I think the mechanics of sharing a common base with distro variants is the easy part.
The hard part is stuff such as - different community styles; different expectations of quality, quantity, etc.; different writing styles; difficulty in creating an upstream with the authority to enforce style guidelines, etc.
Another problem I hit several times is to keep various languages in sync. If you don`t see excatly what changed in the original-document, it`s near to impossible.
So keeping the documentation per chapter or even smaller in a cvs would help.
We typically do this modularity for DocBook, sometimes down to the <section>-per-file. Not sure how this would work with the POT file; perhaps there could be some way to group/ungroup/regroup from modular files.
- Karsten
On 5/21/07, Karsten Wade kwade@redhat.com wrote:
A belated follow-up that has been sitting on my desktop ...
On Sat, 2007-04-21 at 22:45 +0200, Robert M. Albrecht wrote:
Has docbook something like ifdef ?
Yes, although the exact mechanism for XML escapes my ability to recall at the moment.
AFAIK, the most syntactically correct mechanism for conditionally branching in XML is XPATH.
See: http://en.wikipedia.org/wiki/XPath for a quick explanation.
John Babich Volunteer, Fedora Dcos Project
On Mon, 2007-05-21 at 14:21 +0300, John Babich wrote:
On 5/21/07, Karsten Wade kwade@redhat.com wrote:
A belated follow-up that has been sitting on my desktop ...
On Sat, 2007-04-21 at 22:45 +0200, Robert M. Albrecht wrote:
Has docbook something like ifdef ?
Yes, although the exact mechanism for XML escapes my ability to recall at the moment.
AFAIK, the most syntactically correct mechanism for conditionally branching in XML is XPATH.
See: http://en.wikipedia.org/wiki/XPath for a quick explanation.
I was under the impression that XPath was more a specification for locating or addressing parts of an XML document. There's much easier ways to deal with this in DocBook using simple XSLT, e.g.:
http://www.sagehill.net/docbookxsl/Profiling.html
docs@lists.stg.fedoraproject.org
-
John Babich -
Karsten Wade -
Paul W. Frields -
Rahul Sundaram -
Robert M. Albrecht