First post to this list. I've offered various observations on devel@ and Fedora Forums on: general boot behavior, with emphasis on making dual and triple booting work on Macs; issues surrounding MBR and GPT partitioning schemes; and the lunatic asylum of (U)EFI, CSM-BIOS and BIOS mode booting of hardware.
I see the bug is assigned, but no activity since Nov 2011. If agreeable, I can take on an edit for F16 which would also carry over to F17. The fix is very straightforward. As described in the bug, primarily it's removal of the bulk of existing text, because the current text is almost entirely obsoleted by GRUB2. And then documenting the proper command for the included GRUB2 script that causes the regeneration of a new grub.cfg. I'd expect the section to be cut in size and complexity by 80%, accounting for a mention of perhaps three optional custom configurations that admins may find useful. And probably also include some note to the effect that direct editing of the grub.cfg is not recommended by upstream, therefore advanced users who do edit the file are advised grub.cfg can be overwritten without notice, and are better off making their custom inclusions in the proper /etc/grub.d files, and then executing the regeneration script.
Basically, start simple and general purpose, and then get to a few specific examples. And leave the rest to upstream documentation.
A bit more complicated right now is bug 750108. It might be best to remove the current material, and reference Anaconda's option to configure this at install time as the absolute easiest way to deal with it. And reference upstream's documentation until someone gets around to writing a reasonable step by step for doing it post-install. Better than than obsolete material that won't work.
Yeah I know, I am boring, but hey, we just need to have the current
status of the RN, if it needs few commits, we do them, if it is ready,
we just push to transifex.net.
There current problem could be: jjmcd is always dealing with RN. But
if he is too busy, we need to finish by ourselves…
Could someone check the RN status?
If I have confirmation that they could be shared with translators, and
if nobody could push them to transifex, I would be happy to do it
myself and notice translators.
---------- Forwarded message ----------
From: Tiansworld <tiansworld(a)fedoraproject.org>
Date: Fri, Apr 27, 2012 at 2:18 PM
Subject: Re: Is Fedora 17 Release Notes available?
To: Fedora Translation Project List <trans(a)lists.fedoraproject.org>
On 04/27/2012 07:56 PM, Kévin Raymond wrote:
> Nice that some translators noticed that :)
> I have been pinging them for weeks…
> Through IRC, mailing lists…
> Please join the last thread at
I am afraid that we couldn't complete the translation for Fedora 17 if
it is still unavailable till May.
Fedora Project Contributor
trans mailing list
So we're going to "write a book at FUDCON".
Participation in this crowd-sourcing experiment will not be limited
people physically at FUDCON; anyone, anywhere on Earth with a FAS
account and internet access will be able to participate.
I want to make the book something as accessible as possible, as the main
things here are to trial the approach and give people an opportunity to
use the system. So something deeply technical like "Advanced SELinux
Policy Writing Guide" is not a good candidate.
So I'm thinking of a book along these lines:
It contains user stories ("my first Fedora"), anecdotes ("the best and
the worst"), use cases ("What I'm doing with Fedora"), a chapter on
Downloading and Installing (with links to more detailed documentation),
what to try ("cool things in Fedora"), and where to go for more
information / help.
What do you think?
On Fri, Apr 27, 2012 at 1:53 PM, Silvio <perplesso82(a)gmail.com> wrote:
> There's a way to edit the screenshots included in documentation to be
> translated in the specific language?
> For example, how can i edit figures in Resource Management Guide for
> Italian translation?
> ....If there's a way, obviously!
I this is a DocBook/Publican option, there is a RFE against transifex for that.
Please see https://github.com/transifex/transifex/issues/3
I am CCing docs, as they could have more info
Could someone please send a summary of all guides that we should
translate for F17? (I could then forward to translators). The
meetings#guide_status wiki page is not too explicit.
The ready (beta) ones and the one that should be ready soon.
A wiki link should do it, but that would be really appreciated to have
docs member telling translators what is or will be up to date.
As a translator coordinator and a docs member/publisher, even by
reading (not all) meeting minutes, I have a hard time to know the
guide status… I can't even imagine for other translators.
The Beta release notes should be ready now, you agree?
I don't know if you guys are aware of this last minute change, but the
FESCo decided yesterday to drop the firewalld feature for F17, as it
appear to be not ready. jjmcd, please update the release notes ;).
Thanks all for your hard work, what is going to be set for FUDCon KL
should be really great!