Name: David Niemi
Ottawa, Ontario, Canada
Profession: Working as Environmental Engineer and Manager
Company: Environment Canada, only a personal interest in the project, no
professional (work) involvement
Goals in the Fedora Project:
- In an editorial fashion contribute to the readability,
comprehensibility, and interpretation of documentation for the newbie /
average user of Fedora / Linux.
- Offer suggestions for the enhancement of documentation
- Assist in getting the docs out in as timely a fashion as possible.
I know I am probably not the best person to lead the development of a
document but feel that I am capable of contributing to it and at the
same time learning more about OS, it's ins and outs. At this time there
are too many possibilities for documents, though one that has been
suggested on the Fedora list is a summarization of many of the more
common problems and solutions that are posted.
I can edit for writing and delve into things to determine technical
accuracy and though Grammar has never been my forte, could contribute
there. I would not be good at documents dealing with programing,
scripting and the like.
I have used Linux for the past 2 years though I first played around with
it from 94 - 96 but didn't go very far. I Only have programming
experience with Fortran and Visual dbase. I feel that I am quite
generally adept with computers hhardware, software, and OS's and can
usually figure out how to do most things though not afraid to ask for
assistance when required. I have set up a small home network and
experienced many of the issues with getting Fedora to talk with
I have written documents and participated in the team development of
many documents both published and unpublished while working at my
current job. I do not keep a brag sheet of my documents and
contributions, I don't even care really if my name appears on them, I
just like to (and have to @ work) ensure that they are technically
correct and lead to the proper interpretation of the information.
I would be an excellent match for the project as while I have a low to
moderate familiarity with Fedora and Linux I am still pretty new at
other aspects and from this point would see things from a different
angle from other highly knowledgeable people. I also lack some of the
assumed knowledge that can be hidden behind a couple sentences. I enjoy
contributing to the writing of documents, learning new and challenging
things, love working with computers, and can visualize / sympathize the
information gulf that this project is in the process of bridging.
GPG KEYID and FingerPrint
pub 1024D/42888171 2006-01-22 [expires: 2007-01-22]
Key fingerprint = 3BAE CA31 FA00 FB60 8831 46AF 8274 9C1A 4288 8171
uid David Niemi (Dave) <drn_temp2(a)rogers.com>
sub 1024g/89C30083 2006-01-22 [expires: 2007-01-22]
I just realized that when CVS tagging a document revision, it is not
sufficient to tag only the document directory: one must also tag the
building infrastructure in "docs-common/". Tags are fast, cheap and
easy, so we can use as many as we like.
Using a command such as:
$ cvs tag <some-tag-or-other> docs-common example-tutorial
will make it easy to reproduce a document any time in the future.
Here comes my question:
Since tags will be shared among all documents that use
"docs-common/", how should tags be formed?
Perhaps something such as "cvs tag example-tutorial-foo docs-common
example-tutorial" where the "foo" is up to you. A tag can get
project-wide, "example-tutorial-FC5_test2", or very local,
Questions? Comments? Suggestions? Donations?
I was indicated to this list, so here I am :)
Last year I began working on a 'book', explaining many things to the
Linux world for newbies and somewhat advanced users. At that time, I
choose to use the Fedora Documentation style because I liked the way it
works and presents itself (it is pretty ;)
The book now has more than 100 pages, and it is in portuguese. I always
use the Fedora's Documentation Guide as reference, so the 7253-line XML
is nice and validates very well on building HTML pages (chunks and
Since I'll release the book freely, I will need a PDF version for
distribuition, since many people will like to print it. The
Documentation Guide says that PDF generation is somewhat broken :(
Still I'm building the pdf format well, but somethings are just broken:
like lists (itemizedList, orderedList, etc), tables (really messed up),
the "commands" box, and such are not showing pretty like in the html
Is there any way to fix these issues? I want to keep this book in this
format (Fedora's XML Docbook) since I liked and is much convenient. In
the other way, I need the PDF "pretty" version too :(
Some tips? Advices? Tutorials on changing and customizing the xsl
If anyone wants to see the PDF version, I uploaded to:
Any help apreciated!
"Talk is cheap. Show me the code." - Linus Torvalds
Dear Chester and Aman,
I have added a "Translation Quick Start Guide" to the repository (I
should have reported to the fedora-docs-list before adding it... sorry
about it). Anyway, though the guide is still a draft, it contains the
essential information about how to translate software and documentation
for the Fedora project. I believe it would be useful if we can include
it in the L10N wiki page < http://fedoraproject.org/wiki/L10N/ > .
Aman, Chester, as you are the maintainers of the Fedora Localization
Project I would need your assistance to export the XML file to the wiki
(I believe making the html file is not enough).
Karsten Wade (quaid)
Tommy Reynolds (megacoder)
Paul Frields (stickster)
Gavin Henry (G2)
Stuart Ellis (elliss)
Bob Jensen (BobJensen)
Schedule of Tasks:
* Karsten: A process is being developed to enable automatic
transcription from the Wiki to the DocBook format.
The Release Notes for FC5 test3 will be used to test and develop the
facility, with XIncludes to compile the individual sections into the
* Karsten: Initial discussions have begun on transferring the
Translation infrastructure to the main Fedora CVS.
* Karsten: To begin a Wiki page on the OPL (Open Publication License) as
a license for Fedora documentation.
The OPL without options provides the same freedoms as open source
software licenses - the content may be freely distributed and modified,
provided that the original authors are acknowledged.
Full IRC Log:
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
Currently, the RPM packaging is geared to produce two types of RPM:
1) A .src.rpm whose content is somewhat similar to a CVS checkout; and
2) A .noarch.rpm whose content is targeted to the GNOME/KDE help
Should we also include the rendered HTML files in the .noarch.rpm or
should we have an additional version?
I set up an email box specifically for use with this email list just a few
I submitted some work to the list on Friday that I've not yet had a response
to, but what puzzles me is that today I had a genuine email from paypal to
the normal address that I set up for use with ebay and paypal, asking me to
update my credit card details because it was about to expire.
Also today to the address I set up for this list only, I received two
fraudulent emails, claiming to be from paypal and Barclays, both also saying
that my card details were about to expire, and both having http links in the
email pointing to a server at 188.8.131.52.
Has anybody else had any emails like this? I have not used this address
anywhere but with the Documentation list.
Registered Linux user number 393408
There was a discussion on the Fedora list today, about how to help new users
make sure they create the installation CDs correctly.
My suggestion, which seems to be viewed as being a good idea, is to place a
text file called READ_THIS_FIRST in the same folder as the iso files. It
would contain some very basic information about how the CD burning process
operates, and how to use the iso files.
The objectives would be to make the first installation of Fedora Core less
frustrating for beginners, and reduce the wastage of blank CD-Rs.
I am happy to spend some of my time doing a little typing to achieve these
Registered Linux user number 393408
-----BEGIN PGP SIGNED MESSAGE-----
> On Sun, 2006-01-22 at 11:35 +0000, Stuart Ellis wrote:
>>On Sat, 2006-01-21 at 21:14 -0500, Debra Deutsch wrote:
>>>What do I want to write about? My primary interest is to write about
>>>topics that will help people who are comfortable with computer software
>>>and hardware but are not expert in Linux. That is how I see myself.
>>>These readers understand operating system principals, the functions of
>>>the hardware components in a computer system, and how the hardware and
>>>software work together. They may be willing to take on complex tasks
>>>that are not appropriate to a non-technical user. On the other hand,
>>>they may not have all the Linux-specific knowledge that some discussions
>>>of advanced topics assume.
>>Welcome to the project.
>>This describes what I would like to do with the Administration Guide -
>>provide a document that gives readers with some understanding of
>>computers the confidence to manage Linux systems, by clearly explaining
>>how the system works:
>>You may also be interested in the Getting Started Guide, which is a more
>>basic introduction for new users that Bob Jensen and Martin Brej are now
> Too fast on the Send button...
> If you are interested in contributing to one of these (or starting your
> own document), the next step is to create a Wiki account:
The Administration Guide sounds like a great place to start. I've
registered for a Wiki account (DebraDeutsch). However please note that
I have not yet sent back my signed license agreement. That should
happen tonight. I need to double check that my agreement with my
employer has no overlap with the project. It shouldn't, and I don't
believe it does, but I'd prefer to be completely sure.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----