https://bugzilla.redhat.com/show_bug.cgi?id=849678
Bug ID: 849678
QA Contact: docs(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com,
stickster(a)gmail.com
Assignee: nobody(a)fedoraproject.org
Summary: Virtiualization Administration Guide does not have a
BZ component
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: lnovich(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: docs-requests
Product: Fedora Documentation
Description of problem:
No component exists for this manual. Please open one ASAP as I need to file
bugs against it.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
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.
Hi all:
In response to BZ#808103[1] I've just committed a change to the Feedback
section of the Publican Common Content for the Fedora brand. This adds
(actually, requires) a direct link to the Bugzilla product and component
for the book in question. This is quite an invasive change that will
require attention from the Localisation team. We will need their help
for Publican 3.0 shortly anyway, so I figured that if we needed to make
invasive changes, now is the time to do it!
If you'd care to run your eyes over the text, I'd welcome any
suggestions for improvement in the next day or so before I request help
from translators.
Cheers
Rudi
[1] https://bugzilla.redhat.com/show_bug.cgi?id=808103
Docs Team,
In order to improve upon the QA procedure[0] we've developed over the
past few releases, we need someone to shepherd tickets through the
process. As such, we've come up with a description of what a "QA
Wrangler" would do (see the bottom of link 0). Now all we need is a
volunteer. If you're willing to fill this roll, please reply on list.
If there are multiple people interested, we can let them fight it out
or come up with a way to rotate or separate duties.
[0] https://fedoraproject.org/wiki/Docs_QA_Procedure
--
Ben Cotton
Fedora Docs Leader
Hello! I am Eduardo Mayorga Tellez from Nicaragua. I have recently joined the Fedora Project and currently I collaborate doing translations. I've used Linux for 4 years and Fedora since two years ago. I'd like to help in the documentation because I think I can help other users to use no-experienced user the operating system.
Regards.
You'll Never Walk Alone