Please make release notes easily accessible without javascript
by Bruno Wolff III
I wanted to see if there was mention of an issue in the f12 release notes
and when I tried to get them I found that the page
(http://docs.fedoraproject.org/) uses onchange to submit a request to
where the appropriate version of the document is. It would be nice if
browsers without javascript were able to use that page without having to
read through the source to find the correct link to use.
Perhaps listing out all of the links when javascript isn't available or
having a submit button that can be used after setting the language for
a document.
13 years, 11 months
Fedora 13 Beta release notes
by Paul W. Frields
I built the content for all languages that were at around 90% or
higher -- 8 languages -- and posted it to the web site. Rudi is
checking my work and the index.php file, and will tag it LIVE for
tomorrow morning's (EDT) release.
Paul
13 years, 11 months
Enabling floppies should be covered in the release notes
by Bruno Wolff III
As far as I can tell, not enabling floppy devices by default has not
appeared in previous release notes. Based on when I ran accross the problem
this was probably changed for f12.
While it isn't hard to enable them (modprobe floppy as root), typically
when you notice the problem you using don't want to spending time trying
to figure out why you don't have a floppy device.
There is discussion about this issue going on now on the Fedora kernel list,
but it seems likely that the trade off the kernel developers think is best
is not using them by default.
It would be nice if people were warned about this before they run across
the issue, so the release notes seem like a good place. Perhaps mentioning
on the FAQ (even though there may not be all that many people still using
them) to make it easy to find the answer if people run across the issue
after updating.
In theory some one time user space check could be made to cover most of
the people still using floppies, such a thing isn't going to exist before
the f13 release (if ever).
13 years, 11 months
Re: F13 Beta announcement
by Robyn Bergeron
On Sun, Apr 11, 2010 at 1:41 PM, Paul Frields <stickster(a)gmail.com> wrote:
> Ryan, David, Robyn, Rahul -- you guys did a great job beefing up the
> F13 Beta announcement! Thanks for the effort you put into it. I did a
> couple minor edits but I was really happy about the quality you guys
> built into the page. Great job.
The bottom of the announcement points to release notes on docs.fp.o.
(https://fedoraproject.org/wiki/F13_Beta_announcement) - but the F13
release notes aren't listed there.
Friends in docs - is there any way we get a copy / pointer to the
release notes in progress up on the front page of docs.fp.o?
Thanks,
Robyn
>
> Paul
> --
> marketing mailing list
> marketing(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/marketing
>
13 years, 11 months
Using GPG in the Security Guide
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don't like the current chapter "Using GPG" in the Fedora Security
Guide. It falls short on actually giving information on how people can
easily use GPG. We talk about generating keys in GNOME and KDE but stop
there.
We do have information on the wiki that talks about using GPG with
various email clients. If there are no complaints I'll start
integrating that information into the Using GPG chapter.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLv+peAAoJEDbiLlqcYamxIcMP/3jZvnFKoGiqeU/N1OXlJqyq
C1PmaodyjMLIBHgB5uncWrmY5NgUhusK/Vk5v98bRQovqJoui6hs+bX/ftSZD83q
2Y//iHkAL7iU1IEOqy6tcwrN5B+aB87sKbSKvZ4TyKRyVwbs8DnXQN7WbvrFdmkE
7oSw05KkPIXwjleuplUR9pMzS/8CaLRU3LUirVckAO/ZclK1JF6kNhFW7d+pvTV6
CpltgnDO30mgOvckG9jP0hXWsbPz8uUP/dG/k9uf4xJ0P7225UWHDYSYMWgIlWxq
jd0QdGoLPxwZyQUFnIVy1qCtaVwjJi2nclrp5cqNAoU+jMcHRMBMMrbt/Ghe5H0F
j6hHJbsANfPTcGgSCkANKVr8QYwnoKubGeedu996wMhnX9esl0kOGSAdJn/cUM9K
LgK1sWjTnEdP6nCZ4Vd5iaWtVIbRQ1IYkjkz6W/Vu64rocy9NqDycs5TtPwAiDeo
3PPkOA+9BtXABX4u8wSM4qWUUUt6WvIZwtb7kAssOq5q5rJwam68LQXRGMFJamjl
eOYjugmVIVR00an1wd6gTczvNmCjF69jBZQZvd8Z42fsqJJyjpj/mETykf8D9hga
a+x9L9VF7HoTgyxmhMke8atoqmVujAIvwFYkK4dqm8ON9pyLlVepF/PM+MjPpjuW
4wFnoDptw7sknI3FzEYy
=sg9W
-----END PGP SIGNATURE-----
13 years, 11 months
Re: web/html/docs/translation-quick-start-guide/zh_CN appe-Translation_Quick_Start_Guide-Contributors.html, 1.3, 1.4 appe-Translation_Quick_Start_Guide-Revision_History.html, 1.3, 1.4 index.html, 1.4, 1.5 sect-Translation_Quick_Start_Guide-Accounts_and_Subscriptions-Applying_for_an_Account.html, 1.3, 1.4 sect-Translation_Quick_Start_Guide-Accounts_and_Subscriptions-Congratulations.html, 1.2, 1.3 sect-Translation_Quick_Start_Guide-Accounts_and_Subscriptions-Create_a_Bugzilla_account.html, 1.2, 1.3 sect-Trans
by Piotr Drąg
W dniu 09.04.2010 16:56, Rüdiger Landmann pisze:
> Author: rlandmann
> Log Message:
> Update ru, zh-CN; add ko, uk
>
I'm very glad you did this, thanks a lot. Would you mind updating also
the rest of translations and en-US? Current revision in git has many
corrections (e.g. updates links to new Transifex and mailing lists)
compared to what's on docs.fp.o.
--
Piotr Drąg
http://raven.pmail.pl
13 years, 11 months
Updating POT files
by John J. McDonough
Having spent a little time battling the details around updating the POT
files automatically, I think I finally have it working. I thought I
would share the script so others don't have to go through the same
battles.
This is far from elegant, and a variant of the build script I posted on
the wiki. But there are a few little details. In this case I again
updated the po's individually. In the case of the build I wanted the
logs. In this case, it prevents me from having to build long strings of
languages for git add and update_po.
Note that since I am pushing back to git, I use the ssh:// clone variant
instead of git://
Script below
--McD
#!/bin/sh
#
# Script to update POT and PO files and push
# back to git
#
# ----------------------------------------------------------
# Modify the following variables for your situation
#
# List of subdirectories to ignore
NOLANGS="build tmp pot po publican.cfg README en-US"
# Scratch directory on local machine for work
WORKDIR="/home/jjmcd/Projects/Release-Notes/F13/makepot"
# Document to build *** NOTE ** If your document is not
# in the docs/ subtree in git, you will need to modify
# the git clone statement below
DOC="release-notes"
#
# End of variables to modify
# ----------------------------------------------------------
#
# Move to scratch directory
cd $WORKDIR
# and clean it out
rm -Rf *
# Let's check how long this takes
echo "Start " `date` >time.txt
git clone ssh://git.fedorahosted.org/git/docs/$DOC.git
pushd $DOC
cp -R en-US ..
git checkout --track -b f13 origin/f13
rm -Rf en-US
mv ../en-US .
rm -Rf pot
publican update_pot
git add en-US/ pot/
# For all subdirectories
for LANG in * ; do
# Figure out whether this one is one of those to ignore
DOIT=1
for TEST in $NOLANGS
do
if [ $LANG == $TEST ] ; then
DOIT=0
fi
done
# Do this directory
if [ $DOIT == 1 ]
then
publican update_po --lang=${LANG}
git add ${LANG}/
fi
done
git commit -m "Updated POT files"
git push origin f13
popd
# And now the finish time
echo " End " `date` >>time.txt
13 years, 11 months