April 2014 - docs - Fedora Mailing-Lists

[Bug 654484] New: New Bugzilla component for Storage Administration Guide

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: New Bugzilla component for Storage Administration Guide https://bugzilla.redhat.com/show_bug.cgi?id=654484 Summary: New Bugzilla component for Storage Administration Guide Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: medium Priority: low Component: docs-requests AssignedTo: eric(a)christensenplace.us ReportedBy: r.landmann(a)redhat.com QAContact: fedora-docs-list(a)redhat.com CC: stickster(a)gmail.com, kwade(a)redhat.com, nb(a)fedoraproject.org Classification: Fedora Target Release: --- Please create a component for the Storage Administration Guide; default assignee should be ddomingo(a)redhat.com Cheers Rudi -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

9 years, 4 months

1
6
0 / 0

[Bug 839625] New: Configuring_an_IPA_Client_on_AIX instructs to configure sshd with 'GSSAPITrustDNS' which causes sshd to no longer start

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=839625 Bug ID: 839625 QA Contact: docs(a)lists.fedoraproject.org Severity: medium Version: devel Priority: medium CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com, stickster(a)gmail.com Assignee: nobody(a)fedoraproject.org Summary: Configuring_an_IPA_Client_on_AIX instructs to configure sshd with 'GSSAPITrustDNS' which causes sshd to no longer start Regression: --- Story Points: --- Classification: Fedora OS: Linux Reporter: chorn(a)redhat.com Type: Bug Documentation: --- Hardware: All Mount Type: --- Status: NEW Component: docs-requests Product: Fedora Documentation Description of problem: http://docs.fedoraproject.org/en-US/Fedora/17/html/FreeIPA_Guide/Configur... instructs to set 'GSSAPITrustDNS no' in /etc/ssh/sshd_config . Version-Release number of selected component (if applicable): current / fedora [15|16|17] instructions How reproducible: always Steps to Reproduce: 1. access webpage 2. implement change 3. try to start sshd Actual results: sshd no longer starts Expected results: sshd should start Additional info: - GSSAPITrustDNS is a ssh client option - its not mentioned in the manpage but recognized - http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Identit... mentions it as client option - http://freeipa.com/page/ConfiguringAixClients looks like the most current howto and does not mention the option at all. I think just removing the option from the webpage is the most simple way to resolve this (recheck whole howto with an AIX client for bonus) -- You are receiving this mail because: You are the QA Contact for the bug.

9 years, 6 months

1
7
0 / 0

[Fedora Infrastructure] #3860: Test box for Publican 3

by fedora-badges

#3860: Test box for Publican 3 ----------------------+----------------------------------- Reporter: sparks | Owner: sysadmin-main-members Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Systems | Version: Test Severity: Normal | Keywords: Blocked By: | Blocking: Sensitive: 0 | ----------------------+----------------------------------- The Docs Project needs a test system setup for our docs.fp.o replacement. It needs to be on a EL 6 box with the optional channel activated. -- Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/3860> Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure> Fedora Infrastructure Project for Bugs, feature requests and access to our source code.

9 years, 11 months

1
14
0 / 0

Working on bugs

by Simon Clark

Hello, I saw from this week's Docs Meeting logs that there was a discussion about the number of open bugs in BZ. I would like to help reduce this number but first I would welcome some guidance about the etiquette around picking bugs to work on. I have read the wiki page Fixing Documentation Bugs [1] and it says I should choose a bug, assign it to myself and update its status to ASSIGNED. Almost all of the open Fedora documentation bugs list a named Assignee, even those with status NEW and not ASSIGNED. Does BZ automatically list an Assignee for new bugs, based on the Product and Component? Is it OK to assign to myself any bug ticket with status NEW? What are the accepted practices here? Thanks, Simon [1] https://fedoraproject.org/wiki/Fixing_documentation_bugs

9 years, 11 months

2
2
0 / 0

Re: Some editing ideas for Fedora 21

by Leslie S Satenstein

Hi Christopher It works for me. I worked as tech writer and editor for topics about ERP. I had to write for French, an Spanish readers. The writer should never edit his own work beyond the first go-around. Regards Leslie Mr. Leslie Satenstein SENT FROM MY OPEN SOURCE LINUX SYSTEM. >________________________________ > From: Christopher Antila <christopher(a)antila.ca> >To: Leslie S Satenstein <lsatenstein(a)yahoo.com>; For participants of the Documentation Project <docs(a)lists.fedoraproject.org> >Sent: Wednesday, April 30, 2014 12:43 AM >Subject: Re: Some editing ideas for Fedora 21 > > >Leslie: > > >On 26 April 2014 16:33:53 Leslie S Satenstein wrote: >> May I also suggest that a the person reading this section of release notes >> is assumed to have prior Linux knowledge >> >> I took the Fedora 20 release notes and marked them up so that they read much >> better. By read much better, the opening paragraph of the attached document >> explains the "raison d'être". >> >> If the attachment is lost, please refer to my public link >> https://dl.dropboxusercontent.com/u/42050559/wip/ReleaseNotes%20Touchups.od >> t (release notes touchup) >> >> Hope to get your feedback, either favourable or other. > >A majority of the Release Notes content is written from scratch with every >release. On the other hand, the content in Chapter 1 is mostly carried from >one release to the next. > >Within the next couple of days, I'll review your comments about Chapter 1, >then return them in an ODT file. After this, you can incorporate your revisions >either into the Release Notes git repository or on the wiki, along with >updates for Fedora 21, to heave them included in the next release. > >Will this work for you? > > >Christopher > >

9 years, 11 months

1
0
0 / 0

Some editing ideas for Fedora 21

by Leslie S Satenstein

Hi Pete and Documentationalists. May I also suggest that a the person reading this section of release notes is assumed to have prior Linux knowledge I took the Fedora 20 release notes and marked them up so that they read much better. By read much better, the opening paragraph of the attached document explains the "raison d'être". If the attachment is lost, please refer to my public link https://dl.dropboxusercontent.com/u/42050559/wip/ReleaseNotes%20Touchups.odt (release notes touchup) Hope to get your feedback, either favourable or other. Regards Leslie Mr. Leslie Satenstein SENT FROM MY OPEN SOURCE LINUX SYSTEM.

9 years, 11 months

2
1
0 / 0

Fedora Docs Meeting Summary 28 April 2014

by Pete Travis

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by randomuser at 14:00:45 UTC. The full logs are available athttp://meetbot.fedoraproject.org/fedora-meeting/2014-04-28/fedora_docs.... . Meeting summary --------------- * Roll Call (randomuser, 14:00:46) * New Writers (randomuser, 14:04:28) * publican & publishing (randomuser, 14:10:58) * I worked a little on the ansible definition for the box - it was mostly all there already, but needed adaptation from my local environment to the production fedora environment (randomuser, 14:21:14) * this week, i will either need to get fedwatch scripts ( the part that makes the backend update automatically after a koji build) from jsmith, or stop being so lazy and improve the existing ones (randomuser, 14:21:23) * fedora.next product updates (randomuser, 14:21:26) * LINK: https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Projec... ? (randomuser, 14:30:56) * docker writers wanted! (randomuser, 14:34:42) * guide status (randomuser, 14:35:05) * outstanding bug list (randomuser, 14:48:22) * LINK: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNE... (randomuser, 14:48:30) * Open Floor (randomuser, 14:58:19) Meeting ended at 15:00:52 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * randomuser (90) * lnovich (27) * pbokoc (11) * Sparks (8) * mpduty (7) * rkratky (4) * zoglesby (4) * zodbot (3) * Capesteve (3) * jsmith (1) * jjmcd (1) * pkovar (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

9 years, 11 months

1
0
0 / 0

Question about the Docs Mission Statement

by Christopher Antila

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi: After writing my previous email, I was provoked to make a change to the formatting of the "Join the Docs Project" page, which used to have two redundant language-selection blocks.[0] I fixed that on the "mission statement" page, and revised the content a little---no big deal.[1] While adding an explanation to the "mission statement" Talk page, I realized there's actually a newer, more complete draft of the mission statement.[2] There are some points in the "revised final proposal" that aren't present in our actual mission statement. I'd like to change our mission statement to essentially match the "revised final proposal" on the Talk page. But I'm sure people talked about the Docs mission during the FAD in March. What do we think? Christopher [0] https://fedoraproject.org/wiki/Join_the_Docs_Project [1] https://fedoraproject.org/wiki/Docs_Project_mission_statement [2] https://fedoraproject.org/wiki/Talk:Docs_Project_mission_statement -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCgAGBQJTVXkqAAoJEAWCcTQ3FNFM3tEP/iAI7plEMN3j/SBhGjJxfuT/ zO8ZKX9YOS7aDN4nHBnb49AYS3RFPThUGjzuLR72D5MH1B9ZQ6WmFsyiamQHnMaF 4BlIK0VTk+Bh/HSF6KLAQeiN+s9XtDroMl/ZJc+ZDIh3Sk0PlLcDyYeVwy7glAVI 3ap4yCifYpTKpR82aALaO3MvTvUkh/TCr4fHrLtOtLe9YaugfI+kTqMsY8u76lwb GvC0vnwdAvZhPaEFahSkzWo0Kirq8IH7a46jkg6c1Wd/gixWCNfu7IVOWpy1skhq 4EE2WG6TlgwIycYRuJIzNRCw/Iy261opJvhhQJUq92GghfYVBAwHgWISnMT+iunA daIw9JpeDLo3lbA+vAQiXbcmcrP7lA0CnA5iPhuxnrduSQ0PUJf8+ol3yMAAi/Bu TwV2cPDwIQ3cmRhANSKb7F0AwoH1GtVvUMava8NMLTIuE3G20SLQiU9+E6o2T5NP AhVQEv/NNF937G2Dg+gPbpSj2eFP2rdNwqlTNuEwkupdJcNZ6dRd11PSYwjzx8x5 ZFte0aLA8JOZ8PBki1+m2RgOrSgILNQ1fUZ/OVuLzBgQ2hFbIgXlwIHEmDoStKxe xoJJcpwRH4S4RJc5X8A1jb18x57unb9oz0xQOuBZR0UACzwKzBAzX53TG+s2Ookc GFCB2Ix3JMlF321N86Lg =3u4m -----END PGP SIGNATURE-----

9 years, 11 months

2
2
0 / 0

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting

by Pete Travis

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2014-04-28 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: An hour of docs folks talking about what they are working on and what they'd like to work on. More information available at: [https://fedoraproject.org/wiki/Docs_Project_meetings](https://fedoraproje... Source: https://apps.fedoraproject.org/calendar//meeting/371/

9 years, 11 months

1
0
0 / 0

[Fedocal] Reminder meeting : Docs Office Hours ( Americas )

by Pete Travis

Dear all, You are kindly invited to the meeting: Docs Office Hours ( Americas ) on 2014-04-24 from 12:00:00 to 13:00:00 US/Mountain At fedora-docs(a)irc.freenode.net The meeting will be about: Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake. More information available at: [https://docs.fedoraproject.org](https://docs.fedoraproject.org) Source: https://apps.fedoraproject.org/calendar//meeting/323/

9 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs April 2014