Minor action item
by Paul W. Frields
Here's another (relative) quickie that any of our helpful members,
silent or not, could handle:
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/MeetingMinutes
This page on the wiki is used to record our IRC logs and meeting
summaries for the FDSCo. Unfortunately, it's a few months out of date.
There were a couple missed meetings in there, but it would be great if
someone could scour the archives and link the logs and minutes there.
Just use the existing list as your template and put in the new links the
same way. You can certainly find the minutes through the archive sites:
http://www.redhat.com/archives/fedora-docs-list (for minute summaries)
http://www.redhat.com/archives/fedora-docs-steering (for IRC logs)
There may be an occasional leakage of one or the other of these messages
to either list, but usually that's how they're done. If anyone could
look into this, it would be great. Just for information, I did the last
"Mass Info Dump" and it took me only about 30 minutes or so to find
everything and do the copy/pasting. And that was probably with various
rugrats interrupting at the time. :-)
In the future we should endeavor to link these right after publication
of course, but hey, no aspersions cast, I forgot just like everyone
else. :-D
--
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/
18 years, 2 months
help posting relnotes to Web
by Karsten Wade
If anyone has a few minutes, can you help me by posting the latest
release-notes from CVS to the Web?
You can follow the pages from http://fedora.redhat.com/docs/release-
notes with new links for FC5 test2. test1 can be left in the table
below and test2 highlighted.
The Tip box has two kind of links:
* The first is to the absolute latest in CVS HEAD.
* The second to what is tagged FC-5-TEST2-TRANS-FREEZE.
There may be more languages available in HEAD, please test by
uncommenting in the Makefile and running test builds, along with what
you know from fedora-docs-commits.
I will check back in a few hours and see if help is needed.
thx - Karsten, the deadline guy
--
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
18 years, 2 months
New Makefile targets
by Paul W. Frields
There are a couple of new Makefile targets available as part of our
march toward test3 and hopefully some usable RPM packages. Between
Tommy and me, we've made it pretty easy for you to make additions to the
rpm-info.xml file without a lot of excess work.
"make clog" - Use this target any time you add information to a document
or need to roll a new RPM. The target provides prompting to create a
new <revision> entry at the top of the <changelog> node set. (Currently
you still need to change the DOCVERSION and DOCDATE entities in your
document manually, but I will work on alleviating that requirement.)
"make colophon" - Provides prompting to create a new <worker> entry in
the <colophon> node set. Same rules apply. :-)
Keep in mind the approximate workflow if you have a document that you
haven't yet converted to use the new rpm-info.xml file. (If you don't
have an "rpm-info.xml" file, you and your translators will be unable to
build the document.)
--
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/
18 years, 2 months
Purpose of "fdpsh", the Fedora Documentation Project Shell
by Tommy Reynolds
Hi, Folks!
Instead of adding process flow targets to
"docs-common/Makefile.common", or making very many interrelated
targets, let me offer an alternative: "fdp-functions" and "fdpsh".
My preferred technique to adding interrelated process steps is to
use lots of tiny shell scripts. Shell scripts read like code to me
and the flow seems easier to understand. To that end, I leveraged
Paul's "fdp-functions" beginnings by adding the "fdpsh" script.
The "fdpsh" script transforms your shell (unless you are running csh,
and if so, why are you ;-?) into an FDP-specific tool. It takes care
of setting the necessary environment variables and provides handy
task-specific actions that could be awkward otherwise. The ${PATH}
is also updated so that "docs-common/bin" is first on the searchlist.
So please consider adding shell functions for actions first, and
resorting to "Makefile.common" only if you must. A target like:
show_workers:
${FDPBIN}/fdpsh -c get_all_workers
is a lot cleaner than exposing the individual steps in the
"Makefile".
End of commercial. Thank you for your patience. Please pay on your
way out.
18 years, 2 months
Fedora Projects weekly report
by Rahul Sundaram
Hi
We have a new effort in place to provide weekly reports on the all
different Fedora sub projects.
http://fedoraproject.org/wiki/Projects/WeeklyReports
Someone within the documentation team, kindly step up as a report
writer. Meeting mins, note worthy discussions in mailing lists, major
bugs and feature enhancements, upcoming changes, progress reports and
unbiased editorial comments and constructive criticisms can be included.
String freeze will be made every Friday of the week to enable
translators to do their work. Announcements will be made as part of
Fedora News (http://fedoranews.org) on the subsequent Monday. Let me
know if you require any clarifications on this.
--
Rahul
Fedora Bug Triaging - http://fedoraproject.org/wiki/BugZappers
18 years, 2 months
Re: Current IG Build Gives Duplicate Legal Notice
by Paul W. Frields
On Mon, 2006-01-16 at 00:34 +0000, Stuart Ellis wrote:
> You may well know about this, or I may have just made an error, but just
> in case...
>
> I've committed an update to the IG which uses an rpm-info.xml. This
> builds but the HTML has the "Legal Notice" link twice. Commenting out or
> deleting the LEGALNOTICE entity in fedora-install-guide-en.xml doesn't
> make a difference.
>
> To ensure that everything is in sync I checked out a fresh copy of
> docs-common at 00:28 16-01-06, so now I'm stumped.
Hi Stuart!
You're not in error at all; strangely enough, I was just fixing this
problem this morning since I appear to have found it at about the same
time. It was a simple error with the "bookinfo.xsl" file, which
transforms your "rpm-info.xml" into a <bookinfo> or <articleinfo> node
set. (This node set becomes the generated file "fdp-info.xml".)
Basically, we had calls to a legal notice entity in that file twice, so
it would always appear in the generated "fdp-info.xml" file twice.
Should be fixed now, but please let me know if you have any further
problems with it.
I'm cc'ing the list in case anyone else ran into this particular goof.
--
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/
18 years, 2 months
Self-Introduction: MikaelJacobsson
by mosp
1.
Full legal name: Mikael Jacobsson
*
City, Country; Skövde, Sweden
*
Profession or Student status: Currently unemployed
*
Company or School: n/a
*
Your goals in the Fedora Project
o
To promote Fedora in Sweden
o
Assist swedish fedora users through my website.
o
Translate documents to swedish to be used both on my site
and in the Fedora Project website.
o
Any other projects where im needed. Don't know what yet. I
joined it all this week.
*
Historical qualifications
o
What other projects or writing have you worked on in the
past? I have runned a internet magazine about sports from
2002 to 2004.
o
What level and type of computer skills do you have? I have
used computers since 95, know enough about linux and windows
to install, configure and use. I have educations in
webdesign, basic computer knowledge and more.
o
What makes you an excellent match for the project? I like
fedora ;) and i always do the things i say i will, i like
working for good projects. I have for as long as i can
remember, been involved in different projects where helping
others is the main issue, and doing it without charging for
the time spent.
*
GPG KEYID and fingerprint
o
Key ID: 1018A10D
Key fingerprint = CF75 EEB6 9136 3BD1 0E95 ACB7 EC05 87AD
1018 A10D
18 years, 2 months
Making a case for ".cvsignore" again ;-)
by Tommy Reynolds
Hello, All!
The new packaging technology Stickster and I are completing is based
on keeping all of the meta-information about a document (authors,
license, changelog and such) in a separate file "rpm-info.xml". This
will make it much easier to keep the <articleinfo>; <bookinfo>; RPM
spec file; and changelogs all in sync.
There is a DTD file in "docs-common/packaging/rpm-info.dtd"
that defines how this file is to be constructed.
A new language-specific file, "fdp-info-${LANG}.xml", will be
generated based on the "rpm-info.xml" file. It will contain the
<articleinfo> or <bookinfo> content. The base document will then
include the "fdp-info-${LANG}.xml" file using an entity reference.
The "Makefile.common" rules will generate this file any time
"rpm-info.xml" is changed.
Every document will have the following file dependency chain:
rpm-info.xml ==> fdp-info-${LANG}.xml ==> document-${LANG}/index.html
The "rpm-info.xml" file gets manually updated, the
"fdp-info-${LANG}.xml" file gets rebuilt and then the document is
rebuilt.
My recommendation is that the "fdp-info-${LANG}.xml" files NOT be
archived in CVS. They are derivative files and archiving them in CVS
may mess up the file timestamps such that after a "cvs update" the
document may not rebuild correctly.
I think this is a job for ".cvsignore", to prevent the inadvertent
archiving of these files:
========= .cvsignore =============
fdp-info-*.xml
==================================
should do the trick. Then even if an "fdp-info-${LANG}.xml" file
gets archived, CVS will simply ignore the archived version on updates
and ignore the local version on commits.
There has been prior resistance to having a ".cvsignore" file in the
CVS archive itself (although having your own local one is just fine),
but this may require more thought. I like the idea of having this
preventative file in CVS.
What do others prefer?
Cheers
18 years, 2 months
New Fedora Translation Project Maintainers
by Sarah Wang
Hi everyone,
I'm very pleased to announce that we now have a couple of new
maintainers for the Fedora Translation Project:
Amanpreet Singh Alam <aalam(a)redhat.com>
Chester Cheng <ccheng(a)redhat.com>
>From now on, they will assume the responsibility of coordinating the
Fedora Translation efforts and lead this project to the next level.
Chester has authored the translation guide for Windows users. Aman has
built the Punjabi translation team that integrated some major Open
Source projects such as Gnome, KDE, and Open Office into Fedora
translation. They both have been enthusiastic contributors and
coordinators for this project over the years. So good that I have no
reservations in turning over the leadership role to them. I view this
change as a very positive one. It will no doubt bring fresh perspectives
to the Fedora Translation Project, and increase the response time to
your queries and concerns.
I would like to thank everyone for the patience and support you have
given me over the years. I hope you would extend the same support to our
new Project maintainers and continue contributing to the overall success
of Fedora.
Sarah
18 years, 2 months