docs December 2013

docs@lists.stg.fedoraproject.org

17 participants
38 discussions

Upgrading section of Installation Guide
by Adam Williamson 18 Dec '13

18 Dec '13

(pjones, there's a paragraph about bootloader stuff in the middle of this mail which could use your input - skip straight to that :>) Hi, folks. Just looking over the Upgrading section of the F20 install guide as part of my hurried project to try and co-ordinate our fedup messaging... I believe these parts: "Some upgraded packages may require the installation of other packages for proper operation. If you choose to customize your packages to upgrade, you may be required to resolve dependency problems. Otherwise, the upgrade procedure takes care of these dependencies, but it may need to install additional packages which are not on your system. Depending on how you have partitioned your system, the upgrade program may prompt you to add an additional swap file. If the upgrade program does not detect a swap file that equals twice your RAM, it asks you if you would like to add a new swap file. If your system does not have a lot of RAM (less than 256 MB), it is recommended that you add this swap file." from https://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/ch-u… are old holdovers from preupgrade and no longer applicable or relevant; I think they should simply be removed. https://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/ch18… : The --debuglog stuff seems kind of extraneous, since you never explain to people what it's for or what to do with the log. I'd either add a note about what this does and why they might want to look at the log etc, or just drop that parameter from the instructions. The stuff about updating the bootloader on UEFI is specific to the Fedora XX->Fedora 18 transition where grub2-efi was introduced. F17 and earlier are now EOL and we do not really support upgrades from EOL releases. I would suggest we simplify this section and basically write it considering only upgrades from 18 or 19, at least in the main body. I don't _believe_ we have made any changes to the efibootmgr stuff between F18 and F20, or that it is necessary to 'refresh' the grub2 configuration - I think UEFI upgrades at least between F18 and F20 should not require or even recommend any form of manual intervention with grub; it should all be in order after a fedup. pjones, can you correct me if I forgot anything? (I need to check how this works out in the real world, for sanity - had a couple of reports this morning of UEFI fedup not working properly at all, but the _theory_ is what should be reflected in the installation guide text, I guess). So, I'd recommend replacing "This is not mandatory, but is recommended for BIOS systems and strongly recommended for EFI systems." with "This is not necessary for UEFI systems. It is not mandatory, but is recommended, for BIOS systems." and then dropping everything from "To update GRUB on EFI systems..." to "After the next reboot, your system will be using grub2-efi." The 'fedup can only upgrade from Fedora 17 and above' note is also now fairly EOL-y. The "If the contents of your /etc/fedora-release" note is I believe a holdover from anaconda-based upgrades and can be removed. We could add a little 'EOL upgrades' section at the bottom, perhaps, which explains that EOL upgrades are not supported but you can try if you're adventurous enough, and maybe suggest reading the installation guides for the relevant Fedora releases to find specific instructions like bootloader migration? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 1

As I read the release notes,
by Leslie S Satenstein 17 Dec '13

17 Dec '13

May I comment on the following.... 1.3.3.2. CPU Accelerated Graphics Systems with older or no graphics acceleration devices can have accelerated desktop environments using LLVMpipe technology, which uses the CPU to render graphics. LLVMpipe requires a processor with SSE2 extensions. The extensions supported by your processor are listed in the flags: section of /proc/cpuinfo Could you add that this information is only available if the user already has installed, a previous version of Linux Can he do something about this SSE2 test after installation? Regards Leslie Mr. Leslie Satenstein An experienced Information Technology specialist. Yesterday was a good day, today is a better day, and tomorrow will be even better.lsatenstein(a)yahoo.com SENT FROM MY OPEN SOURCE LINUX SYSTEM.

1 0

remove Ryu in relnote
by Alick Zhao 16 Dec '13

16 Dec '13

Hi all, According to [1], Ryu has not been added into F20. However, it is mentioned in the release notes. Please consider to remove it from the release notes. Credit goes to Christopher Meng. [1] https://bugzilla.redhat.com/show_bug.cgi?id=998540 -- Alick Fedora 18 (Spherical Cow) user https://fedoraproject.org/wiki/User:Alick

2 1

Fedora Docs Meeting Reminder 16DEC2013 1400UTC
by Pete Travis 15 Dec '13

15 Dec '13

The regular meeting of the Fedora Documentation Project will, as usual, take place on Monday in #fedora-meeting on freenode. (Intellectual) Refreshments to be served in #fedora-docs before and after. -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

man-pages de license change
by Robert M. Albrecht 15 Dec '13

15 Dec '13

Hi, the upstream project for the german man-pages translation died quite some time ago and was now rebootet. The new upstream made a license change to GPLv3+. Anything to worry about for Fedora ? cu romal

2 1

Anaconda Addon Development Guide almost finished, needs review
by Vratislav Podzimek 10 Dec '13

10 Dec '13

For a few last months I've been line after line putting together the Anaconda Addon Development Guide [1] -- a short and straightforward guide describing how an addon for the Anaconda installer can be implemented, tested, deployed and packaged. I believe it is now almost finished, but it needs review and probably a lot of tweaks based on the feedback, I'll hopefully get, before I'll propose it as a part of the official Fedora project documentation. So comments, suggestions, issue reports or patches [2] are more than welcomed! [1] http://vpodzime.fedorapeople.org/anaconda-addon-development-guide/ [2] https://github.com/vpodzime/anaconda-addon-development-guide -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

1 0

Fedora Docs Meeting Reminder 1400UTC 9Dec2013
by Pete Travis 09 Dec '13

09 Dec '13

You have the time and date from the subject line, so you know when to join #fedora-meeting on freenode for the weekly meeting. -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

Is there daily build of F20 Release Notes
by Alick Zhao 06 Dec '13

06 Dec '13

Hi all, Is there daily build of latest F20 Release Notes set up? For the last release we have [1], but I find it has not been updated for Fedora 20. The translators may wish to use the daily build to proofread the latest translated release notes. Thanks! [1] http://fedorapeople.org/groups/docs/release-notes/

3 2

Push .pot files to Transifex for 2 documents
by Jérôme Fenal 04 Dec '13

04 Dec '13

Hi, Can you please push the latest pot files to Transifex for : - docs/readme-burning-isos.git, - secure-coding.git (which BTW should be moved to the docs subtree). The first one should be pushed forcing a complete update, it seems that the repo has not changed in 5 months, but the latest push (a month ago or so) did not change some resource appearing in Tx. Worse than that, it seems that the git repo is totally discordant with Tx. And Tx seems to be more up to date. So I'm really wondering where is the git repo for this readme/guide, or if I missed something? ;-) Regards, J. -- Jérôme Fenal

3 3

any reason why f19 virt deployment and admin guide is not listed at docs page?
by Robert P. J. Day 03 Dec '13

03 Dec '13

just noticed that this guide: http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Vir… doesn't show up as official fedora 19 documentation here: http://docs.fedoraproject.org/en-US/index.html is that because it's "draft" status? will it be an official part of the fedora 20 documentation? rday

1 0

Fedora Docs Meeting Summary 2DEC2013
by Pete Travis 02 Dec '13

02 Dec '13

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by randomuser at 14:09:34 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-12-02/fedora_docs.2013… . Meeting summary --------------- * Roll Call (randomuser, 14:09:34) * Release Notes / Changes (randomuser, 14:11:24) * release notes rpm should be out by wednesday, publishing to docs.fp.o then too (randomuser, 14:12:09) * TODO: bugs are filed against docs-requests to identify updates [to] docs based on F20 Changes (randomuser, 14:20:44) * Guide Check-in (randomuser, 14:22:18) * Docs FAD 2014 (randomuser, 14:27:56) * there is an upcoming Docs FAD at some point (randomuser, 14:28:15) * Sparks sent a message to Robyn regarding funding but hasn't heard back yet. (Sparks, 14:29:35) * It appears that we won't have any problem with the Raleigh site but nothing official has been requested yet. (Sparks, 14:30:03) * LINK: http://whenisgood.net/docsfad2014 (Sparks, 14:30:55) * LINK: https://fedoraproject.org/wiki/Docs_FAD_2014 (Sparks, 14:31:34) * agreed: bcotton will attend FAD whether he wills it or not (randomuser, 14:33:02) * post docs FAD topic ideas to the list so we can attend prepared (randomuser, 14:36:38) * outstanding BZ tickets (randomuser, 14:36:48) * LINK: http://tinyurl.com/lbrq84 (randomuser, 14:36:55) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=627417 (randomuser, 14:38:58) * open floor discussion (randomuser, 14:41:02) Meeting ended at 14:52:24 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

Fedora Docs Meeting Reminder 2Dec2013 14:00UTC
by Pete Travis 02 Dec '13

02 Dec '13

The weekly Fedora Docs meeting will take place at 1400UTC this Monday in #fedora-meeting on freenode. We have a lot to talk about, if attendance merits - an upcoming release, plans for the future, and a FAD in the works. Attend if you can! -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

Flashback: Fedora Docs CVS
by Pete Travis 30 Nov '13

30 Nov '13

I spent some time this afternoon playing around with the Fedora Docs CVS archive. The ambassador team is rewarding commemorative t-shirts to long-time contributors, and between the CVS logs and git logs with help from ohloh[1] I'll sort out who has been the most active over the last 10 years. The script found: 143 branches 11720 total commits 108 unique committers Top committers: 5011 pfrields 962 kwade 610 elliss 560 jtr 373 zepires 361 tombo 331 mdious 299 transif 231 bbbush 223 raven 172 fab 146 tfox 139 hyuuga 123 diegobz 118 kmilos 116 glezos 106 mwiriadi 100 warrink It represents a *massive* amount of work, and a strong foundation for our documentation today. Thanks to the Fedora Docs team of then, now, and tommorrow! [1] https://www.ohloh.net/p/8544 -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs December 2013