-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 16 January 2013 09:38:03 Brendan Jones wrote:
On 01/15/2013 08:33 PM, Christopher Antila wrote:
> Now that Fedora 18 is released, I'm sure we're all wondering about the
> status of the Fedora Jam spin. I don't know anything about that.
>
> But I *do* know about the Musicians' Guide, which I published for Fedora
> 18
> earlier today.
>
>
https://docs.fedoraproject.org/en-US/Fedora/18/html/Musicians_Guide/index.
> html
Thanks for doing this Chris! I have no idea how the docs team works and
thought that maybe the ship had sailed for F18 - this is good news.
For future reference, here's how it works... and it's the same for any Guide
(like the User Guide).
An author can publish their document in any available languages at any time
for any release. Ideally, all of the Guides are updated before each release,
then published on the same day as the release itself. In reality, the Guides
are slowly updated, and *if* a Guide is published for a particular release, it
will usually show up anywhere from a month before to a month after the release
date.
We try to avoid updating the published books between releases. In my mind, the
real reason is that it would make translation much more difficult: if we always
keep the most recent English version in the translation system, it's changing
too fast to complete a single, consistent translation. On the other hand, we
could publish updated versions of the English only... but then that drifts
away from any published non-English version, and could lead to confusion for
readers who may be using both languages.
Furthermore, it leads to a situation that *looks like* the Fedora Project
holding up English as the best or most important language, when really I think
most of us simply mean to say that English is the language we happen to use.
At least for me, I would gladly write the Musicians' Guide concurrently in all
four languages I know, except I don't have the specialist vocabulary... the
reality is, English is the only language I can use well enough to write this
document, and that's the reason its primary language is English.
On the other hand, we can always use the "Draft Documentation" section for
intermediate updates.
Whew!
Christopher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJQ9yOeAAoJEGpo1cWDqVnYT1IP/1kusVD597V/5zyLuGIznc8w
9Lz7EEcYkGHd3Ub9WwakG1ZnPKA+4XLE9JeJfS0fySGd9stVY5uFvGysWQo46Wi3
A/xh1ttNO2qjMYdxrXrfmya6TTtNAs1fjIw+ueMItIRfPYYgPklAdvuBYFZQSNOr
j8t4nfD/lamF6QVSM11rrsHo4mdGWSnZr8PzRstY8V/bNqXPQCwAlS7zZsbPi6ki
j8HsH3IXuk7t4atJ5dbK8n00sIV56LAAIWFRhgWkmO69OAi76QiC4lgbB9T7ljyf
hiBurpABcwYwtxlh8x9kJHgV0eTZFsH62/Z2DsBX6NAk0/O8jCocgO9nQP1QN2g1
njA6PRd2Nvzjpt0jzpL8YUk9RQ1OM09RRx68/JIzyv83dNDM1n8rIYXuHdMJB5Fa
ANmovcYJt8YJ8FHFmHshu93fgHEx0lYzBwZ+X/yd0WMK/fbLJoY/Xjtj4vY5wAX7
BLUhh+4flXWTHha6Ie7t0evTDlGFpx8tcPyNH3qZnOW0E4NRN6TxnKkcrAEeuJAk
ZUtvkm3aUyyhwxybIujIFpck9/Vk4ZYPtScEbWvFfCzv03k7u6OUq/JGgHfsXVEQ
jdlAuxAJxWmCdbULOGhtoxdQ9WBo8htJPS04A5TGNt1CFBiXiqppHrYxUt271vhl
+cwZ1bKyhLnSc/Xv+d+1
=GbzM
-----END PGP SIGNATURE-----