Fedora Installation Guide
by Jérôme Fenal
Hi there,
The French team is considering making a special effort to advance French
translation of the Fedora Installation Guide.
We however have a number of issues which do not ease its translation :
- 877 different resources visible in Transifex, of which
- a lot are read-only and not accepting translations,
- a lot are one-liners, or to be correct, one stringers.
Could we please have a status about this guide (are there parts not to
translate), and can we expect a cleanup of its setup in Transifex (major
sections only, not more one-stringers)?
Regards,
--
Jérôme Fenal
10 years, 12 months
Meeting reminder, with apologies: 29 APR 2013 1400UTC
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There's a meeting scheduled for Monday, 29 April 2013, at 1400 UTC in #fedora-
meeting on freenode. Unfortunately, I have a scheduling conflict that will
probably prevent me from running the meeting. I'll do my best to attend, but
am not too optimistic about it.
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRfcVwAAoJEL1wZM0+jj2ZHOMH+wbzLd3Z7FZvP4A9Hr0tXCWE
Yv6x/WsrADMVqhtxwMOF3MdD2ifp7IhzowcTtq/pc/kddboYYA4mYbmIucExsoT9
JfDUz8NM7ql/Epw/YV4F0TNHxuSxza5BC0LCtjVYaGTBHZDHXhAvIZThPLF/1gAX
3zCSSBWBMXdH6KZfNJeBp+T4cJ3xkuNoP0NJqBGb4l+2eWDy/i9I0BR/P0OIA/2J
q9Sy2rNbEsU4WHM8SLRpIy7yTbTLNDX8PzMhZ4TyOfCnBP6Pcmi7hUw4+fyaz0El
1hEOE9fu0oRxaobDhqyBUJ1Rr7V/bCSVWrdtj8Sp9p0FT1gqNT0T7CgIOW6JvMk=
=ILFW
-----END PGP SIGNATURE-----
10 years, 12 months
release announcements, talking points, release notes, and how we group features into audiences or stories
by Robyn Bergeron
Hi,
(Sorry for evil double-posting :D)
I was taking a look at the oft-neglected Talking Points, which were
originally designed as a handy list of "new shiny" for each release
that could be handed off to Ambassadors as a quick reference list of
features to talk about, and have also at times served as a starting
point for choosing features to be highlighted in release videos,
interview stories / articles, blog posts, etc. It's entirely possible
that they have also been a reference point for writing release
announcements as well. Talking points tend to be very focused on
*totally new* things, and not generally on incremental improvements.
And so I figured I'd take a crack at it again - see
https://fedoraproject.org/wiki/Fedora_19_talking_points - though the
mail to mktg list is still yet-to-be-written (the content of this mail
sort of got in the way, ha). (For those unfamiliar, it's sort of an
iterative process, wherein a number of features are proposed, and
marketing whittles them down into a list, which is likely shorter than
perhaps the feature-related content in a release announcement might
be.)
A few things stood out as I was going through the list:
1: We have bucketized items into a handful of groups over time, in the
talking points as well as release announcements, as well as for docs
beats and eventually, release notes - User, Developer, Sysadmin (and
Cloud/Virt have popped up here and there in more recent releases for
announcements). Those lines seem to be increasingly blurry - there are
tools/apps that cross the dev and sysadmin roles, user and sysadmin
roles, etc. - and while these groups are probably good for
beats/release notes, esp. since content can just be duplicated /
retailored if absolutely necessary, I'm wondering the following:
Is bucketizing a bunch of stuff into "User, Sysadmin, Developer" the
best answer for marketing highlights of the release? It seems like...
well, a listing of car parts, but not really telling a story about the
car, for lack of a better metaphor. And it seems a lot like "we made
a bunch of improvements here and there" isn't as compelling as "we
have improved overall state of ($experience, $usecase, etc) and here's
how."
Looking at the list of features it seems like there are a few main
themes, for which I've suggested some marketing-i-fied
names/groupings, though (as you can see in the Talking Points link)
it's certainly open to other suggestions (or the option of leaving
as-is):
Develop and Distribute: Languages, compilers, and tools for developing
software, and tools for packaging software. (Could also be: Create,
develop, and distribute?)
Start and Recover: Enabling a variety of options for improving boot
times, as well as quicker recovery from system or software failure.
(Boot and Recover? Launch and Recover?)
Monitor and Manage: Systems and resource management, and tools for
diagnosis, monitoring, and logging.
2. Note that I'm not advocating for the "user, sysadmin, dev"
categories to change in docs-land; I think that these stories/themes
are likely to change with each release. But, given the intertwinement
of docs and marketing when it comes to the release announcement, it
seems like (if docs is crafting the tech-bits of the release
announcement) if we were to bucketize by stories, that we'd need to
get marketing to figure out what those stories are. And I don't just
mean the overarching stories, but also the individual feature stories,
in some cases; I can't tell you how many times I look at a feature and
say, wow, I wish I spoke that language, I wonder what the bigger
picture is, what this effectively enables? Maybe the talking points is
a launch point for that as well, in additoin to being the list that
gets handed off to ambassadors, and then can drive the story
collections in a release announcement, or in one-page release notes;
I'm not sure. Thoughts? The workflow, as often seems to be the case
between docs & mktg, is key.
Basically: Seeking feedback? Thoughts, anyone? :D
-Robyn
11 years
Publishing to web.git
by Pete Travis
I tried and failed to publish draft Technical Notes last night. The error,
from memory, was an sqlite related failure about a missing 'format'
table. Should I be checking out the 'Publican 3.1' branch of web.git ?
--Pete
11 years
Removing authors from cover of guides
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I've found that the Security Guide has so many authors/contributors now that they are running off the cover onto a second page. The authors are already listed on the copyright/license page; I propose that we remove the authors from the cover and leave them on the copyright page. Adding the list, with, perhaps, an inclusion of their contribution, to an appendix might also be a good idea.
Thoughts?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
iQGcBAEBCgAGBQJRcWWlAAoJEB/kgVGp2CYvkTEL/0kR/VhrstSZkPesW5Hgs18z
r3PcmesVQWy6U3ui+ii7y+pHrUJhwKjBmuFsaCaVqlog9yDkjc8YVomcu1D8CdS7
BT31A8g6v5q/22hhwPwG5ngtXWeo581xOR/7bKz0kXiQMwf0LunkNO1S1Eau4nmM
NOmSVgVXVEX6LVe0FqFXMckpiK6HaKHjCb/UdXofehzvZoSiEX6xEnYdCzHg740O
wW7i/SNzBFZkgUq4D8eKk4RaA2OIoQeho/XE3CjI0FBtZ8QS/SBWwWrnUmwjqAH3
G5d/EhVpBkRZON+PvCiKwrsfHWiEyfGdxSwIkf9SXvNt3AzZSzbDSxSKk8Ns7dC+
Q/PYs5JUXsb6R9wyihPUPI1tzJ7J0sUFVTYyB2wSl9iXD7GGkZ3cDFWrBYMM58RC
M/eAfDtJAPriRmkMth0ryF6VoNeGT8xtFzGCnv9PbHS/lFbQZxh/Rcw6IWD+enMT
RyPEOH0eoiohO/VX/QZCAdUk0yIvqOP+xB5TO0izQw==
=1sMZ
-----END PGP SIGNATURE-----
11 years
alpha announcement - eyeballs?
by Robyn Bergeron
Hi folks,
So there have been a few eyeballs on this thus far - but as always would love more:
https://fedoraproject.org/wiki/F19_Alpha_release_announcement
We talked about this a bit in the release readiness meeting 1.5ish weeks ago - IIRC the docs folks were going to borrow liberally from this, and the talking points, to copy over into the release notes.
In any case: At some point today tonight releng (specifically dgilmore) needs to get a "mail-friendly" copy of this to send out for the alpha announcement, so ... if you have feedback, now's the time :D
-r
11 years
Fedora Docs Meeting - 22 Apr 2013 1400UTC
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We're having a meeting soon, hope you can make it!
1400 UTC - 22 April 2013
#fedora-meeting on freenode
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRdNDMAAoJEL1wZM0+jj2Z574H/jjNPMVs8s6HJ8HaL9S+tNvE
sWTY5yaTeuVcylTqOGqaHSNpMjiLsITifDyOBc79zYtBiRYE8Us9TiY0OMTu6rbf
7Vy/S4WSG74O+7TYY1U7JcanbXInyNifIyJuT0EW5dd5CA5bkTm8MM+N7DY61A9n
pTGtgr/wGYu95HBeLQahRsjFZr3TzFLE2Bwjor4ZQcBEjSjlJNjrzCK8wv7Njqrp
8DAN4RaaKtgc/urcjAg8QIUNEmqZi9rnDmAHhz338YqvIJVtAh+vOhMsaHrzR5/i
v7RZJ8oKyT0zXpehr7Q2+9R5VMgShuvboAQwbvUD+KgNeLK1O0y0lLGsDCV4Xas=
=fEZU
-----END PGP SIGNATURE-----
11 years
Self introduction
by Jaroslav Skarvada
Hi,
I am Fedora developer / package maintainer and currently upstream for the
Tuned project. I am member of Power Management and Amateur Radio SIGs.
I recently got doc writers ACLs and I will focus especially on the
Power Management Guide improvements / updates from
the developer perspective. I will tightly cooperate with Jack Reed who
will beautify my ugly drafts :)
thanks & regards
Jaroslav
11 years
Halt translations on Security Guide
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I've done a bad thing with the translations for the Security Guide. Some things have gone wonky. I don't believe I've lost any data but for the mean time please don't start work on the Security Guide until I get this whole thing figured out.
Sorry for the trouble.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
iQGcBAEBCgAGBQJRbwjKAAoJEB/kgVGp2CYvJxcL+gN2lxP6CPgFE4ralmMoFIEG
vrKVcRmx3SmVOfBRMxl8Jo2lzGBEuDkjsK8h9Lyujzn9o0dEQJ/FRl1UKvCkk2c+
paKNTy1H04kqd2FOVdqxavR4iijmt1rHI8WxyEdiGfZU/TskQ3yRx6WV7mnIY6eQ
rahqpOmbQA/7qKXhvYYgasnfXEcNZD+T0XxwQ3hyiesiqAXFiAn5vN+Unobk63Cp
fQ24TmKp4FhXAyYdrzCwtjUkWuaevQa9NtO/4kMz3l4dTKc8tlzopRuohJTMoQHI
hmPDS+BTwEJ20Zyr/aw1iPO/umeqBG742o9IQcAcZeUaonR3MtwxY1Ni8OL1Mj4Q
wLI/xaCpXCWm6bGLPLyKfeSokrubDuXKDMRKEkcK43kZ+vCl8tqqbl1J6cM3EYkW
7IX5gU6XTCHNV4a3iC8rNmEPWiL2Rj/SF18ttwKtrnE/6qkO1EuHFElXwa85e8lY
3WlYgnnyyzrB3Ijki5EcLTk8AK23loCyWsTwRzeXRA==
=E/Q8
-----END PGP SIGNATURE-----
11 years
