docs January 2014

docs@lists.stg.fedoraproject.org

22 participants
51 discussions

pushing translated guides to docs.fedoraproject.org
by Gianluca Sforna 09 Jan '14

09 Jan '14

It seems I wrongly assumed completed translations would be pushed automatically from transifex to the docs site. In particular, I was looking for the burning ISO guide which I recently brought to 100% Maybe the IT team could help with the process by pushing ours once completed? -- Gianluca Sforna http://morefedora.blogspot.com http://identi.ca/giallu - http://twitter.com/giallu

3 3

Re: Docs FAD 2014
by Christopher Antila 08 Jan '14

08 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Pete: Even waiting another week, I still don't know, and it looks like I won't really know for several weeks still. However, if you pick a date, I could at least tell you the date at which I'll find out whether I'm available for that date... Christopher > ----- Original Message ----- > From: Pete Travis > Sent: 12/31/13 05:25 PM > To: docs(a)lists.fedoraproject.org, jjmcd(a)fedoraproject.org > Subject: Re: Docs FAD 2014 > > On 12/02/2013 12:39 PM, Christopher Antila wrote: > > Hi: > > > > On 2 December 2013 13:12:51 Eric H. Christensen wrote: > > > If you want to come to the FAD, please complete the following items by > > > Sunday, December 8th: > > > > > ... > > > 3) Add your available times to the whenisgood page[2]. > > > > I took a conservative approach, and said I would be unavailable for > > weekends > > when I'm not yet sure whether I'll be available. Please don't plan > > around me, > > but I suggest meeting later rather than sooner. > > > > > > Christopher > > I'm looking at the schedule results again, and there's much more > availability later in february and in March than in January. Do you > have a better idea of your plans, Christopher? > > I also noticed that somehow the weekend of 14Feb-17Feb wasn't on the > list; perhaps that was intentionally removed, but I added it for now > just in case, but it might be too soon for me. I have a coworker on > leave for health reasons probably through the second week of February. I > should probably put in for any time off by the end of this week, so > everyone please discuss. > > Of the six respondents so far, everyone except Christopher above is > available for 22Feb and after; exceptions are Laura on Saturdays - who > may hang out anyway as long as we don't put her to work - and Petr Kovar > on Sundays and Mondays - if we were even going to have a Monday session. > > John, you haven't responded to http://whenisgood.net/docsfad2014 yet - > any idea what's in store for you? > > Eric, any news on the logistics front? > > -- > -- Pete Travis > - Fedora Docs Project Leader > - 'randomuser' on freenode > - immanetize(a)fedoraproject.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCgAGBQJSzhcLAAoJEAWCcTQ3FNFMaokP/0zy1e/hg7NjTVnDBRimVBoN jdHyeIyIu5sLnkByAAnmWC+l+24F3o5yNBpzCBQJ6mS9nE6ktD0VwqQJ6A3vr//6 n+2g/PFttqomdZ2fIf8s15mLzOFaF9938QoviCE4w93dhz9zvB29ATzwiGJMDh9w 0yUA/23IZ03HrAKcKzTHGCCcF6Z3h/7X7TxbGbLvPocKRc+eImnxWwxzvZPZ+XLY 6anot5hV/OrkVxHqMox006UGDE2Mlpwn+uGt5PWIpHE82BBwOEcLRTVVCnjVG6/D JiZab4B8NplmUcZKaWOiPMPJzrLi1IZTxsCakLgu+DFEYnzJPooedJWRhGFrsN5x CaU9GK2LOc6tpnUsUG+NfkUAHsBU/8Rr4soMhPp1ql+IDv1ZjafExv+P7ZyGOhGN vHcLQfZHWf4N0XEqHqZoD3G9DIVsMU6qP6J8T4+Nz6gHatUPHqR7giriyRWO4knE Hg6wG14yxHGGUQyTftob5C6IMLxIySUmJFul7Tv2lpe57MVg3LYBq4W9eC/1KXEN elUfLnBb9DHVUsO18nsjKajnpDFEgGCDjwHw1M774bJjAOU/Jpg8GZDIir4oGWZn wCxGktpjomV4Csky5LNX4MtK0Aib3+Pmpcc1mvArdP1yEyGO1aQtx8pCxHN8slzT 6WsfYL1uZUC1Aq07y6RX =h+Dn -----END PGP SIGNATURE-----

1 0

Re: About System Administrator's Guide
by Christopher Antila 08 Jan '14

08 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Rashdaul: I'm the QA contact for the System Administrator's Guide. I haven't done much, but I would be happy to help with proofreading and bugfix verification on request. Christopher > ----- Original Message ----- > From: Rashadul Islam > Sent: 12/31/13 05:54 PM > To: immanetize(a)fedoraproject.org > Subject: About System Administrator's Guide > > Hi, > > I have highlighted my name on the Docs Project Guides > Table<https://fedoraproject.org/wiki/Docs_Project_guides_table>. > I am looking for all cooperation as I am new to maintain the System > Administrator's Guide. > > Thank you Pete for the opportunity. > > -rashadul > Key fingerprint = E27F 7100 0BA2 7212 CD3C A11F 7A38 DF4E F4EB A95C -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCgAGBQJSzhWqAAoJEAWCcTQ3FNFMJywP/0OkqEMaUCBJGr2AI0WiPJ7j Xf2oapW2AsKUhX8euaYqgwdifDZmxf+BTamDD2SeGGvkhGGdQ4DJwJSeYFX5fCMs mqUEgaxIsnkjuOJ1oWMUW6WczifLQKrJ63SH6Xkf0ey4e2C13OIT2jf/t4ybV3sq OhIJ3lFtT6riObF3i804OIHyJ99RAtgvk1WGvPaPecjB3zOelBEB7ia2wkLb/GN+ /NUD26wr3kUparqHsk8Fer5YRIi7W0jGF+yoHRy0FfSzNrOgq/Vw2N7P5BUFfaQx p8d7792hp6UFi2fbceriRyE53/qEh6T2RdcuJprCZcpggWeKiDf7vMaYlNGZKrnJ invDRQ/HHsDn3TQXQi05GopmMVzvTQb6O3jcw/D/6FXfs4TWZ7SZL2CZCYSQF3pQ Ua2t355lduv9z8jylek+EsiJowEOoFJ0ptsz8Y4mYOnrp3A2m601UW+Vo2dZqHlh N88efQeRYDAxwWc1uPnlQnpXQKbab8x+Lb8X3KaeY0pW1fGi4OTQaitOybl489rp Dj9F0itQZHSor3hXiUlFhzjwiPC47u2OP0WS1xkU6JJiI4qsloTbTI3qXbTz/q0+ qxeMn+ficYBQgEf9LSgQHpf4Udne8DQJAi95YIWQ5FMVXHnyvrzEueLcV7AqVeBG E+m3ez8cjD41p7x18zwj =zj4s -----END PGP SIGNATURE-----

1 0

Re: Lowering the participation barrier for Fedora Docs
by Mike Ruckman 08 Jan '14

08 Jan '14

On Mon Nov 18 23:53:46 UTC 2013 Pete Travis wrote: >First off, I feel obligated to point out >that you've very nearly written your post in functional >ReStructuredText! Okay, moving on... >The idea of accepting contributions in varying formats then converting >them for publishing is definitely worth investigating. Let's add >"Identify formats that can be converted to DocBook with fedora-shipped >tools" to the list! >The idea of rolling release documentation is growing on me, as I >consider it. There's no reason to hold back from publishing something >as soon as the feature hits the repos. If we work with a continuous >release model we'll ship updates to Guides that lag behind release date >instead of waiting for the next release. If we're coordinating >efforts, it might be more intuitive to focus effort on features than >release number as well. I wonder if we can get something like this: >docs.fedoraproject.org >----------------------------------- >- Fedora Documentation > -- Fedora 20 Release Notes > -- Fedora 20 Installation Guide > -- System Administrator's Guide # continuous release > -- Burning ISO Images to Disc # continuous release > -- etc... >- Legacy Fedora Documentation > -- Everything that isn't continuous release or that is targeted to >an EOL release >- etc... > > >-- >-- Pete Travis > - Fedora Docs Project Leader > - 'randomuser' on freenode > - immanetize at fedoraproject.org QA is actively working on updating their wiki space and writing tutorials for new contributors - which might be useful for the Docs team when it comes to writing guides (at least, I hope they'll be useful :) ). I second Pete's ideas here. Pandoc [1] is a great tool for converting between different forms of markup - which would make life a whole lot easier when it comes to people submitting short articles/tutorials. If there was an easy, plain-text, means of writing tutorials and submitting them, rolling release documentation and tutorials would be fairly straight-forward to implement. Anyway, just a thought! PS - Sorry for splitting the thread, I wasn't subscribed when it started... // Roshi [1] http://johnmacfarlane.net/pandoc

1 0

Self-Introduction: Mike Ruckman
by Mike Ruckman 08 Jan '14

08 Jan '14

Hey Docs Team! My name is Mike Ruckman (roshi on freenode and FAS) and I work for Red Hat on Fedora QA. I'm spending a lot of my time planning out and editing the QA area of the wiki - trying to make things easier for new people to join the QA effort. Because a lot of my life is spent reading and writing docs, keeping pace with the Docs project seemed like a natural step :) Nice to meet you all! // Roshi wiki: http://fedoraproject.org/wiki/User:Roshi blog: http://roshi.fedorapeople.org/ twitter: http://twitter.com/roshi_fedora

1 0

[Installation Guide] Update to remove references to versioned package documentation directories.
by Simon Clark 06 Jan '14

06 Jan '14

Following instructions in https://fedoraproject.org/wiki/Changes/UnversionedDocdirs change the per package documentation directory in /usr/share/doc to unversioned, just containing the package's name (previously it contained both the package's name and its version). --- en-US/Boot_Init_Shutdown.xml | 2 +- en-US/Grub.xml | 2 +- en-US/Kickstart2.xml | 2 +- en-US/pxe-server.xml | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml index 1f15e22..d0bb832 100644 --- a/en-US/Boot_Init_Shutdown.xml +++ b/en-US/Boot_Init_Shutdown.xml @@ -207,7 +207,7 @@ Once the second stage boot loader has determined which kernel to boot, it locates the corresponding kernel binary in the <filename>/boot/</filename> directory. The kernel binary is named using the following format — <filename>/boot/vmlinuz-<replaceable><kernel-version></replaceable></filename> file (where <filename><replaceable><kernel-version></replaceable></filename> corresponds to the kernel version specified in the boot loader's settings). </para> <para> - The bootloader is also used to pass arguments to the kernel it loads. This allows the system to operate with a specified root filesystem, enable or disable kernel modules and system features, or configure booting to a specific runlevel. For instructions on using the boot loader to supply command line arguments to the kernel, refer to <xref linkend="ch-grub" />. Specific kernel parameters are described in <filename>/usr/share/doc/kernel-doc-*/Documentation/kernel-parameters.txt</filename>, which is provided by the <package>kernel-doc</package> package. For information on changing the target at the boot loader prompt, refer <xref linkend="s1-grub-targets" />. + The bootloader is also used to pass arguments to the kernel it loads. This allows the system to operate with a specified root filesystem, enable or disable kernel modules and system features, or configure booting to a specific runlevel. For instructions on using the boot loader to supply command line arguments to the kernel, refer to <xref linkend="ch-grub" />. Specific kernel parameters are described in <filename>/usr/share/doc/kernel-doc/Documentation/kernel-parameters.txt</filename>, which is provided by the <package>kernel-doc</package> package. For information on changing the target at the boot loader prompt, refer <xref linkend="s1-grub-targets" />. </para> <para> The boot loader then places one or more appropriate <filename>initramfs</filename> images into memory. The <filename>initramfs</filename> is used by the kernel to load drivers and modules necessary to boot the system. diff --git a/en-US/Grub.xml b/en-US/Grub.xml index 399aa83..d30ef58 100644 --- a/en-US/Grub.xml +++ b/en-US/Grub.xml @@ -1034,7 +1034,7 @@ chainloader +1 <itemizedlist> <listitem> <para> - <filename>/usr/share/doc/grub-<replaceable><version-number></replaceable>/</filename> — This directory contains good information about using and configuring GRUB, where <replaceable><version-number></replaceable> corresponds to the version of the GRUB package installed. + <filename>/usr/share/doc/grub/</filename> — This directory contains good information about using and configuring GRUB. </para> </listitem> diff --git a/en-US/Kickstart2.xml b/en-US/Kickstart2.xml index 11f72f6..8339601 100644 --- a/en-US/Kickstart2.xml +++ b/en-US/Kickstart2.xml @@ -338,7 +338,7 @@ Boot loader configuration <listitem> <para> - <command>--enablehesiod</command> — Enable Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in <filename>/usr/share/doc/glibc-2.x.x/README.hesiod</filename>, which is included in + <command>--enablehesiod</command> — Enable Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in <filename>/usr/share/doc/glibc/README.hesiod</filename>, which is included in the <filename>glibc</filename> package. Hesiod is an extension of DNS that uses DNS records to store information about users, groups, and various other items. </para> </listitem> diff --git a/en-US/pxe-server.xml b/en-US/pxe-server.xml index 7b764ec..7a7e70f 100644 --- a/en-US/pxe-server.xml +++ b/en-US/pxe-server.xml @@ -63,9 +63,9 @@ configure it according to the instructions found in the <package>syslinux</package> package documentation. For more information, refer to your local files - <filename>/usr/share/doc/syslinux-<replaceable>version</replaceable>/syslinux.doc</filename> + <filename>/usr/share/doc/syslinux/syslinux.doc</filename> and - <filename>/usr/share/doc/syslinux-<replaceable>version</replaceable>/pxelinux.doc</filename>.</para> + <filename>/usr/share/doc/syslinux/pxelinux.doc</filename>.</para> </section> <section id="sn-cobbler-setup-distro"> <title>Setting Up the Distribution</title> -- 1.8.4.2

2 2

Fedora Docs Meeting Summary 6JAN2014
by Pete Travis 06 Jan '14

06 Jan '14

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by randomuser at 14:00:11 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-06/fedora_docs.2014… . Meeting summary --------------- * Roll Call (randomuser, 14:00:12) * Follow up on action items (randomuser, 14:04:34) * ACTION: randomuser to clean up his mess with the release notes bugs (randomuser, 14:05:01) * new writer check-in (randomuser, 14:05:44) * Guide status (randomuser, 14:10:18) * Guide writers interested in getting help with guides should build todo lists (randomuser, 14:11:00) * LINK: https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Project_… (randomuser, 14:11:09) * DocsFAD2014 (randomuser, 14:52:46) * it looks like the 3rd or 4th weekend in feb or 1st or 2nd weekend of march right now (randomuser, 14:55:59) * if you have an opinion on the date beyond the whenisgood pool that came up with the above window, use the mailing list! (randomuser, 14:56:35) * LINK: http://whenisgood.net/docsfad2014 (randomuser, 14:58:25) * LINK: https://fedoraproject.org/wiki/Docs_FAD_2014 (randomuser, 14:58:39) Meeting ended at 15:01:14 UTC. Action Items ------------ * randomuser to clean up his mess with the release notes bugs Action Items, by person ----------------------- * randomuser * randomuser to clean up his mess with the release notes bugs * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * randomuser (75) * lnovich (27) * nb (20) * Capesteve (19) * pbokoc (10) * jhradilek (10) * iWelcome (8) * zodbot (4) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

Docs meeting tomorrow
by John J. McDonough 06 Jan '14

06 Jan '14

I will be unable to make the meeting tomorrow. It isn't that I don't love you anymore, but we are under a winter storm warning which the NWS classifies as a "RARE" event and life threatening. I will be in a conference call with the State Police at meeting time, and on the air with ARES ops right after that. --McD

2 2

Fedora Docs Meeting Reminder 5Jan2014 1400UTC
by Pete Travis 06 Jan '14

06 Jan '14

Join the first meeting of the new year, Monday 5 January at 1400UTC in #fedora-meeting on freenode. Attendees will receive complimentary comments and all the paper hats they can fold. -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

Self-introduction: Simon Clark
by Simon Clark 04 Jan '14

04 Jan '14

Hello. My name is Simon Clark (user sclark on Freenode and FAS) and I would like to join the documentation project. My answers to the standard questions on the wiki are as follows: - What other projects or writing have you worked on in the past? This is the first time I have worked on a documentation project of this size, although I have written smaller scale documentation before in Dockbook and Latex. I have not used Git before but have worked with SVN. This will also be my first experience of using Publican. - What level and type of computer skills do you have? I have been a desktop Linux user since the 1990s. I have also been a sysadmin on Linux/Unix servers, and some other OS, for small companies and for departments in larger organisations. - What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. A lot of work in my day job has focused on requirements management for large information systems, which has given me plenty of experience in discussing technical subjects with non-technical users. I can write code but I don't get much practice and so it takes me a long time to achieve what I want. - What makes you an excellent match for the project? We will have to find out how good a match I am, but I start as a willing volunteer with a few hours a week to offer and an interest in learning to help with the documentation. - GPG KEYID and fingerprint: pub 2048R/7541F31D 2013-12-31 Key fingerprint = ADC9 D703 11F7 8CAA 88BB BC55 EF2F D1F7 7541 F31D uid Simon Richard Clark <simon.richard.clark(a)gmail.com> sub 2048R/E92429CC 2013-12-31 As a newcomer to this type of project, I would like to start with something reasonably straightforward. I have read some of the recent meeting minutes and mailing list archives and followed some of the conversations on #fedora-docs. It seems to me that reviewing guides for the Unversioned Docdirs change and taking on some smaller items from BZ might be a good place to start. Does that sound OK? Simon

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs January 2014