docs December 2010

docs@lists.fedoraproject.org

13 participants
17 discussions

[Bug 627417] New: docs.fp.o landing page needs 'Start here' note!
by Red Hat Bugzilla 21 Jan '15

21 Jan '15

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: docs.fp.o landing page needs 'Start here' note! https://bugzilla.redhat.com/show_bug.cgi?id=627417 Summary: docs.fp.o landing page needs 'Start here' note! Product: Fedora Documentation Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: docs-requests AssignedTo: eric(a)christensenplace.us ReportedBy: nathan.thomas(a)peacenik.co.uk QAContact: fedora-docs-list(a)redhat.com CC: stickster(a)gmail.com, kwade(a)redhat.com, nb(a)fedoraproject.org Classification: Fedora Description of problem: We have a large variety of documentation guides serving a wide range of different users. It may be difficult for users arriving at docs.fp.o to know where to start, especially if they are new to Fedora/Linux and are unfamiliar with some of the technical terms. A note on the landing page suggesting a sensible starting point for new users could help alleviate this problem. Eg: "New to Fedora? You can try Fedora on your PC without touching your existing installation by following the Live Image Guide." The end of the Live Image guide helpfully points users to the Installation guide if they want to install :) -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 11

[Bug 654484] New: New Bugzilla component for Storage Administration Guide
by Red Hat Bugzilla 15 Dec '14

15 Dec '14

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.

1 6

[Bug 450331] New: lack of documentation on restoring from bare-metal (UUID problem)
by Red Hat Bugzilla 03 Apr '13

03 Apr '13

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=450331 Summary: lack of documentation on restoring from bare-metal (UUID problem) Product: Fedora Documentation Version: devel Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: docs-requests AssignedTo: kwade(a)redhat.com ReportedBy: czar(a)acm.org QAContact: stickster(a)gmail.com CC: fedora-docs-list(a)redhat.com Description of problem: ref: https://bugzilla.redhat.com/show_bug.cgi?id=449299 There is a lack of documentation on restoring a system from bare metal. I have found (see reference) that restore the root ("/") is not as simple as as just executing the restore command when running in rescue mode. With the current emphasis being place on use of UUIDs in both Fedora and RHEL, the whole business of UUIDs need to be better documented. Version-Release number of selected component (if applicable): Fedora 9 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 14

[Bug 595695] New: Direct links to RNs broken.
by Red Hat Bugzilla 31 Aug '12

31 Aug '12

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Direct links to RNs broken. https://bugzilla.redhat.com/show_bug.cgi?id=595695 Summary: Direct links to RNs broken. Product: Fedora Documentation Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: docs-requests AssignedTo: eric(a)christensenplace.us ReportedBy: eric(a)christensenplace.us QAContact: fedora-docs-list(a)redhat.com CC: stickster(a)gmail.com, kwade(a)redhat.com Classification: Fedora Description of problem: * Previously, the release notes were located at http://docs.fedoraproject.org/release-notes/ * Their location has changed to release specific URLs. * A link to the release notes is provided in fedora-bookmarks. * fedora-bookmarks are imported by the browser only on *first launch* so as to not overwrite user modifications. The new bookmarks layout causes two problems: 1. Nobody filed a fedora-bookmarks bug so Fedora 13 (and anyone on F-11 or F-12 etc) will default to going to http://docs.fedoraproject.org/release-notes/ which is a 404. Since the bookmarks can only be imported on first launch, we cannot push an update to fix this if the user has launched the browser (which is extremely likely). 2. Even if I were to fix the bookmarks page to point directly to a specific release version (which again would take effect only if someone would yum update before launching Firefox), then if anyone updated to F-14, the bookmark would not change and would still point to e.g. F-13. So, I do not think that we should put version specific information into our bookmarks URLs. To solve both of the above problems, I believe we should try to do some User-Agent detection and redirection. Fedora browsers have an RPM NVR attached to them. For example: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.2.4) Gecko/20100517 Fedora/3.6.4-1.fc13 Firefox/3.6.4 This tells us that the user's installed language is es-ES and it's a Fedora browser, specifically running F-13. We should then redirect queries to http://docs.fedoraproject.org/release-notes/ to http://docs.fedoraproject.org/es-ES/Fedora/13/html/Release_Notes/index.html If we cannot figure any information out about the Fedora release or language (or there are no relnotes in that language), I propose the default redirect should be to the en-US version of the latest Fedora release notes. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 11

[Bug 504066] New: CMS for docs.fp.org
by Red Hat Bugzilla 26 Jun '11

26 Jun '11

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: CMS for docs.fp.org https://bugzilla.redhat.com/show_bug.cgi?id=504066 Summary: CMS for docs.fp.org Product: Fedora Documentation Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: project-tracking AssignedTo: kwade(a)redhat.com ReportedBy: mel(a)redhat.com QAContact: kwade(a)redhat.com CC: fedora-docs-list(a)redhat.com Classification: Fedora Zikula chosen, working on test instances and project plan with Zikula team -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 57

Musicians' Guide Links Are Broken
by Christopher Antila 27 Apr '11

27 Apr '11

Hello: As per this bug 665663 (see below [0]), all of the links to tutorial files in the Fedora 14 Musicians' Guide are broken. Most of the chapters work on the idea that users will download some files to start the tutorial, then use those files to develop their own fully-completed project. Without these files, users can only complete some of the tutorials - many of the chapters are useless, because the URLS are incorrect! I'll fix this in the master branch tonight, but should I fix it in the published document as well? Thanks, Christopher. [0] https://bugzilla.redhat.com/show_bug.cgi?id=665663

2 1

A new guide for newbies
by Dilip P Kumar 18 Jan '11

18 Jan '11

Hello Everyone. I am a newbie, and unfortunately, have been a newbie for a very long time now. The two biggest hurdles that are stopping me from making any progress are 1. I am afraid I might break something 2. I can't figure out where I can fit in the docs team. To solve the first problem, I want to ask if it is possible to start a "Hello World" doc: A doc meant exclusively for newbies, that never gets published for any release, where everyone is welcome to jump in and get comfortable with the process without worrying about breaking something. Every newbie who joins can be asked to create a chapter in his name, where he can post information about himself, what he likes to work on, and to say "hello world". This will be a good place to get familiar with the system. Further, the doc can be about the process, where to start, what tools to use and all instructions that a newbie will need. This will have the added bonus that a newbie who reads it and doesn't understand something will be able to correct it from his own experience, without bothering everyone else. Taking this one step further, this doc can also act as a guinea pig for all changes in the publishing process. In the current discussions about the QA process, a suggestion was put forward to try out a new method on one doc and see if it scales up. This can be the guide to be experimented upon for all such trials. Can this be done? --Dilip

4 4

Applying for docs-publisher groups.
by Jesús Franco 18 Jan '11

18 Jan '11

As i've learned with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=651650 No matter if a guide is 100% translated, it won't be published automatically, *someone* should publish the work done. I'd like to join the publishers group in order to let people access to last up-to-date translations we are working on (including peer reviews). I'm reading this howto, but i wonder if with the new Publican version (2.3), we are actually forced to logout an then login with en_US locale to avoid buggy links in the published guide: http://fedoraproject.org/wiki/Publishing_a_document_with_Publican Any other guide i should read to understand better the publishing process? Thanks in advance, Jesús Franco http://identi.ca/tzk http://fedoraproject.org/wiki/User:Tezcatl

3 3

Join the Docs group
by john＠ringusup.com 28 Dec '10

28 Dec '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, My name is John Owens, username "johnowenschina". I have many years of experience in technical writing. My native language is English, but I also speak, read and write Chinese. I would like to join the docs group. Best regards, John Owens -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Charset: UTF8 Version: Hush 3.0 wpwEAQMCAAYFAk0axm4ACgkQR2aLzPeiEVkBpwQAiA9isNbVMt3MIdO2z8iMq7Hsqq2F 0528NgsVz0AXlAjBRPcOI34v4r0O/ywmW041pSitx+BxLCuryMxv8zEdVwf5vHD2KRw5 jJ67BByt2fES0pdnTHoeE5KoygNUwwxCgDAS6oK1f86TbtyJEjr0wG2jmtqq4PVgkp5x 4YB1rVQ= =HdnR -----END PGP SIGNATURE-----

1 0

Not available for tonight's meeting
by Eric Christensen 22 Dec '10

22 Dec '10

I will not be available for tonight's Docs meeting. If someone would like to step up to run the meeting please do so. Otherwise we can postpone it until next week. --Eric

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 December 2010