It is rough but there is a list of TODO items for the User Guide at
For most chapters someone just needs to sit down in front of an F13 system
and check for glaring changes.
Small chunks of easy work - feel free to grab one (or three).
I am continuing work on the Office Suites Chapter - after some sleep....
I'll be in fedora-docs tomorrow. Lots of other people there can probably
help fill in the blanks on how to accomplish the TODO items.
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974
I have a request with regard to closing docs bugs. Although not
required, it would be super-helpful if you include a link to the git
(or SVN) commit for your fix when you mark a bug as CLOSED. That way
anyone cc'd on the bug can click the link and see how you fixed it.
Doing this helps optimize transparency and also gives other people who
are lurking a better feel for how we fix bugs. Seeing how easy such
fixes might be creates a higher potential for getting others involved.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
I'd like to add you to my professional network on LinkedIn.
- Mustafa Qasim
Advisory Board Member at Pakistan Open Source Foundation
Confirm that you know Mustafa Qasim
(c) 2010, LinkedIn Corporation
I removed all of Ch.7 and put in the TODO on the User-Guide to get ready
for translation like John, Rudi, and I talked about after the meeting.
So now it should be ready when the time comes to do the "overhaul" as
per the bug that Paul wrote on it.
<rudi> Emad78 -- so feel free to just replace the whole of the content
of that chapter with <para>TODO</para> or something
<rudi> If it's still not done a couple of weeks out from GA, we can just
comment out the whole chapter for F13
<Emad78> So delete what's in there?
<Emad78> and put in the TODO para.
<jjmcd> yes, that way L10N doesn't waste their time
<Emad78> Ok, I will remove the whole chapter then.
A funny thing happened I thought I would share. I did report this to
Shaun McCance by email yesterday, but he is off to a conference so I
don't expect to hear from him until next week at best.
Over the weekend, Shaun asked why we dropped the GNOME application
documentation. Now I hadn't given it a lot of thought. I know I
sometimes had seen other stuff in Yelp, but not lately. Since I wasn't
responsible for that "other stuff" I assumed others had made some sort
of decision and I didn't really give it any thought.
Well, while testing the F13 release notes I noticed that at one point I
saw the documentation appear. So I did a little test.
I made a temporary directory, and moved /usr/share/omf/about-fedora
and /usr/share/omf/fedora-release-notes into the temporary directory (on
F12). Voila, the GNOME documentation appears. Move either one back and
the GNOME docs disappear!
I don't know if there is something quirky with our omf files or what.
Hopefully Shaun can track down what is happening.
If anyone would like to try a test install of the draft release notes
(English only), a test RPM can be found at
Note that this is called "release-notes" rather than
"fedora-release-notes" so it will not overwrite your existing release
notes and can be safely removed. The beta release notes will appear
under System -> Documentation on your menu.
For the terminally curious, yes the specfile is a little limited on
comments. The file sent to beta will be complete. This one was
This release we are doing nightly builds of the release notes and the
guides (Items 6 and 28 on poelcat's schedule). David Nalley asked if I
would share the script I use so others don't have to re-invent the
In addition, Richy Zhou has built a place on fedorapeople where we can
consolidate all the drafts.
I've put up a wiki page with my script and a description for getting the
documents in the right place:
The script is a little clumsy, I'm sure others can do it better, but at
least it is a starting point.
Also, rudi has been talking about a web publishing feature that I
haven't tried, but perhaps that can make it easier still.
Some folks around here have expressed interest in helping with DocBook
conversion for the Teaching Open Source textbook.
This is *not* a Fedora 13 guide, it's an upstream book entirely
outside of the Fedora Project, but since several people offered to
help in the book who are on this list, thought I'd remind you all
Tomorrow (Friday) we begin conversion to DocBook, specifically
Publican formatted. (I'm working on a publican-tos brand package for
I'll do a raw output from MediaWiki using mw-render, then check that
work in to SVN. At that point, we'll grab chapters and start
editing. We'll be sprinting together in #teachingopensource on
After Friday, I expect to have some finishing work over the weekend.
If you are available for any of that time and want to work on this
conversion, let me know. If you are not on the list, please join:
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
smooge is requesting some non-technical help with EPEL as a part of
Max's weekly wiki challenge. His plea copied below:
"I know it is late in the week, but I would love to get some help on the
EPEL page. I need basically a non-technical look at it. Does it
effectively tell what it needs to say? Does it need to be thrown out and
rewritten (ok with me.. I just need some direction and help)"
Is anybody from Docs up for doing this soonish? I would have the same
troubles smooge has right now with reworking the page, so I'm just
sending along his ask for help. :)
Ian Weller <ian(a)ianweller.org>
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments