Re: Updated script
by John J. McDonough
----- Original Message -----
From: "Paul Frields" <stickster(a)gmail.com>
To: "John J. McDonough" <wb8rcr(a)arrl.net>
Cc: <oglesbyzm(a)gmail.com>; <laubersm(a)fedoraproject.org>; "Eric Christensen"
<eric(a)christensenplace.us>
Sent: Tuesday, May 12, 2009 8:34 AM
Subject: Re: Updated script
> Hi guys,
>
> (1) This sort of call for review/help should be on the
> fedora-docs-list where more people can help. It's open source!
Point taken. I still need to get used to this. This seemed so grody I
didn't think the larger goup would care, but then again, being selfish, I am
always interested in learning more, and the more eyes, the more chances i
have to learn! My main motivation in sharing this was so that I wasn't the
only person who knew what I was up to, but there is no reason the three of
you have to be the only ones.
On the other hand, this could be a little misleading without some warnings.
The script essentially builds the rpm, and I am the LAST person anyone
should be looking to for advice on building an rpm. In addition, this is a
transition time, and much of what is in there we hope not to deal with for
Fedora 12. Most if this is fedora-docs-utils stuff that we hope will be
Publican, and some of the Publican stuff are things we hope will be dealt
with in Publican, so certainly, nobody should put too much value on this
script.
On the other hand, it is certainly a treasure trove of ungainly hacks.
I made the rpm for RC in two steps, so in the latest version, the Publican
parts are commented out. I have since pushed the I18n.xml that has the
offending paragraph commented out, so I should be able to run the script
from start to finish, but haven't actually done that yet. After we get the
RC done, I intend to do that so that when any zero day issues are swatted,
we can just run the script to make the rpm.
> (2) Is help still needed?
The package that went to RC has the offending paragraph commented out. We
still have absolutely no clue what is going on there. We need someone a lot
more knowledgable about Publican (hint, hint) to help sort it out. As I
said, I pushed the version of I18n.xml that has the offending paragraph (and
I mean XML paragraph here, from <para> to </para>, it is actually a table)
commented out. Uncommenting it and generating html in any non-English
language should expose the problem. Because of the need to merge the po's,
it might be easier to do this from the srpm than from git. It will
certainly be quicker as the po merge takes some time.
>
> Paul
On Fri, May 8, 2009 at 11:22 AM, John J. McDonough <wb8rcr(a)arrl.net> wrote:
> I'm copying this to Paul because if we can get a piece of him perhaps he
> can
> help, and Eric so he know what's going on.
>
> There is a paragraph in I18n.xml that talks about hotkeys. When you build
> a
> non-English anything it complains it can't find (long string) in (long
> string). Except that the second string has </para> at the end, they look
> identical. If I take the string from the po and paste it into the xml,
> clean out the quotes, I get the same error. If I delete the section from
> the xml it builds.
>
> Attached the same script as before but with a couple of bugs swatted.
> Also,
> the spec file.
>
> It looks like I won't be able to run this cleanly since I need the
> workaround until I figure out the problem with I18n.xml, and so far that
> doesn't look promising.
>
> The script essentially produces six tars from the git.
>
> The five documents produced with fedora-doc-utils are shoved into the
> tarball essentially complete. For whatever reason we haven't actually put
> sources in the script in the past. we "should" have the sources in the
> tar,
> but since we have always done the f-d-u docs building outside the rpm, I
> haven't felt the need to change that for this go. Next time we will
> probably convert those to Publican anyway.
>
> The release-notes tarball has the minimum bits needed to build the docs
> with
> publican. It also has the omf files. For the Publican build, build.sh
> grabs the doc from git, does the merge of the po's, builds the omf files,
> and shoves it all into a tarball.
>
> build.sh builds the other five documents with fedora-docs-utils and makes
> tars with the result.
>
> The tar files must be named <document>-<version> and the top directory in
> the tar must be <document>-<version>. Whether this is really "must be" I
> can't say for sure, but it is how it is always done.
>
> The .spec file is what actually makes the rpm.
>
> The first bit in the spec is pretty much identification.
>
> The section under %build describes the building that happens within the
> rpmbuild. When we do
>
> rpmbuild -ba fedora-release-notes.rpm
>
> This section gets run. The srpm basically includes the six tars and the
> spec, the rpm includes the result of the build.
>
> The %install section describes where to place the various files on the
> target system. the %files section seems to be more or less a check that
> all
> the created files that matter were actually installed and no others.
>
> When you install the rpm building tools, you create a directory tree on
> ~/rpmbuild. All the rpm building stuff happens there. Before doing the
> rpmbuild, the tars must be in ~/rpmbuild/SOURCES. The spec file ends up in
> ~/rpmbuild/SPECS, the rpm in ~/rpmbuild/RPMS and the source rpm in
> ~/rpmbuild/SRPM. The other subdirectories are used during the build.
>
> I just built fedora-release-notes-11.0.0.tar.gz separate from build.sh to
> test. I don't want to hack the git copy just yet, but I want build.sh to
> reflect not doing anything hokey. Until we get the I18n.xml thing resolved
> the other languages won't build out of git.
>
> The easiest way to test these things is with a LiveUSB or a VM. You can't
> really remove the release notes because a million other things update
> them,
> so the simplest thing to do is make a LiveUSB and keep a copy of
> /LiveOS/overlay-xxxx. You can then install the new release-notes on the
> LiveUSB and test them. To test another version, just copy your saved
> overlay file back to /LiveOS and you have a clean install of Fedora. You
> could do a similar thing with a VM, but I suspect it would be a little
> slower.
>
> It seems to be easiest to use yum to install the release-notes:
>
> yum --nogpgcheck localinstall
> fedora-release-notes-11.0.0-1.fc10.noarch.rpm
>
> I'm going to test my hacked version shortly. We still need to update the
> date/version on the f-d-u docs as outlined in the comments to build.sh. I
> would like to resolve the I18n issue, but if not we'll go with the hack. I
> guess we have until Sunday, but I am out of town most of tomorrow and
> Sunday
> is Mother's Day, so probably a lot won't get done then.
>
> --McD
>
14 years, 10 months
Fedora 11 FAQ
by John Poelstra
I have removed the Fedora 11 FAQ from this page
https://fedoraproject.org/wiki/Releases/11/FeatureList
The page is already full and it does not belong there. I think it
should go with the release notes or release summary instead of being the
first thing people see on the feature list.
If people really think it has to be on the feature list page please put
it way at the bottom.
Thanks,
John
14 years, 10 months
Geert Warrink - congratulations and many thanks!
by Ruediger Landmann
Hi all,
I just wanted to say a very big, public thank you to a member of the
Localisation Project -- Geert Warrink.
The Fedora 11 Installation Guide is a massive document (250 pages in its
PDF version) and contains 3,700 strings for translation. Over the last
three weeks, Geert has single-handedly taken the Dutch translation from
around 10% complete to 100% complete!
Congratulations Geert for your amazing effort!
Cheers
Ruediger
14 years, 10 months
bugzilla questions aka: more docs tasks TODO for (or before) F12 cycle
by Susan Lauber
Greetings,
There was some IRC discussion today about bugzilla and docs.
Along with a request to put it to the list for more conversation and
feedback from the "been there, done that" and "here's why" crowd.
The result is and will be more tasks TODO before or during the F12 cycle.
Take a look at the components that exist:
https://bugzilla.redhat.com/describecomponents.cgi?product=Fedora%20Docum...
Notice that Paul and Karsten get most of the assignments.
That doesn't seem right with so many new leaders and authors.
ITEM 1:
Questions that I see:
which docs are dead and need to be removed?
which docs are missing and need to be added?
how do we best change a component name when something has changed?
[this refers to desktop-user-guide having been just user-guide for a
long time now]
And before sparks starts reassigning things, it would be nice if the
doc owners knew it was coming.
Some of the more obvious assignees might consider this a heads up :)
but I do not have the power so you are safe for now.
ITEM 2:
The other part of this issue is that more people need to be closing bugs.
Some of this is triage work - not a bug or filed in the wrong place.
Some is fixing the doc at the source - usually git (or shouldn't be a filed bug)
So - I would suggest that anyone who has write to a doc in git should
also make sure they have the ability to close the related bug in
bugzilla.
Here's how:
1. get a bugzilla account if you do not have one. https://bugzilla.redhat.com/
2. make sure the email you list in bugzilla matches the email you list in fas
3. request sponsorship to the fas group fedorabugs
4. ask stickster to approve fedorabugs and ask sparks to start
assigning you bugs :)
5. starting fixing and closing bugs.
You do NOT need to own the bug to close it. When it is closed the
assignee and the person that opened the bug will be notified, along
with anyone else on the cc list. They will have the option to reopen
the bug if they have more information or do not believe it should have
been closed.
Do try to be polite and helpful when closing the ancient ones. It is
ok to close as the doc is end of life but it is also nice to point out
the link to the current version and encourage more review and
reporting as needed.
I seem to recall some of this info in the wiki but not really easy to
find.... so fixing the docs on how to manage docs is also still a
needed....
>From the peanut gallery,
-Susan
--
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974
14 years, 10 months
Release Notes RPM up for review
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Release Notes for F11 are in koji[1] and is ready to be evaluated.
Once it has been tested a freeze break needs to be requested.
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=101786
Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.5)
iEUEARECAAYFAkoI3U8ACgkQfQTSQL0MFMHBoACVEIuZhzmZs6qW/b3acNPz+UA/
iwCgq8uQNQGbCCYezPdBt+rpkYL9wwE=
=qFtT
-----END PGP SIGNATURE-----
14 years, 10 months
Archer release notes
by Tom Tromey
Is it too late to add release notes? I wanted to add a little warning
about GDB, but then when I looked I could not find any mention of GDB
in the release notes. (I expected the release notes from the Archer
project page to be automatically brought in... but I neglected to
check, sorry about that.)
If it is not too late, the notes from that page are still ok:
https://fedoraproject.org/wiki/Features/Archer#Release_Notes
The addition I wanted to make is a warning to the effect that the
Python API should be considered unstable. Something like:
WARNING: The Python API to GDB is still under development. We
cannot currently guarantee that future revisions to the API will
remain compatible.
thanks,
Tom
14 years, 10 months
News and media coverage plan for Fedora 11
by Steven Moix
Hello everyone,
The release date for Fedora 11 is coming close, so it's time for some
coordination between the Ambassadors and the Marketing group! In this
mail, I'm going to address different points, so everyone has a clear
view of what is going on and how we can effectively split up the tasks.
Also any feedback is of course welcome.
1. In the next couple of days, the Documentation team is going to write
an official Release Announcement for Fedora 11 in English.
2. As soon as this document exists in a final form, it is going to be
translated in a couple of languages, if all goes well German, French,
Spanish, Portuguese, Hindi, Italian and Arabic. This will be coordinated
by the Documentation team with the aid of the Translation team. These
translated versions should be available a few days before the final
release.
Now with that being done, we need to coordinate around everything else.
Earlier this year, the Marketing group has set up a structure called the
News Distribution Network (NDN) [1], which aims to distribute Fedora
news to the global media. Some Ambassadors from different languages have
joined this effort and will be pushing news to a list of publication [2]
they maintain.
Besides that, there are a number of ways in which we really need the
Ambassadors help:
1. Track all the Fedora news you see on the web and add it to our press
archive page [3], this will help us judge the depth of coverage so that
we can focus our messaging more precisely in the future.
2. At release time, and for a couple of days after that, we need you to
follow the comments on news websites. People will probably have
questions there, or you will have Fedora Myths to bust [4]. As much as
some of us might like to flame people, our official policy is to be as
professional and possible while at the same time making our points clear
and well understood. Making members of the community angry us will prove
unproductive.
3. Blog! You can start right now, get vocal about Fedora! Talk about the
upcoming release and what the time table is. Talk about a feature you
care about. Talk about how we got to 11, but most importantly, just
talk!
If you feel like there is anything to add to this list, then please feel
free to reply and make sure to cross post to fedora-marketing-list as
well. Also, please let everyone know in what capacity you can help so
that we can coordinate efforts amongst everyone. I hope that everyone
has a better understanding of the process now :)
1: https://fedoraproject.org/wiki/Marketing_news_distribution_network
2: https://fedoraproject.org/wiki/Marketing_press_publications
3: https://fedoraproject.org/wiki/Marketing/PressArchive/F11
4: http://fedoraproject.org/wiki/FedoraMyths
Have a nice day
Steven
14 years, 10 months