[Bug 627417] New: docs.fp.o landing page needs 'Start here' note!
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: 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.
8 years, 4 months
[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.
8 years, 5 months
[Bug 450331] New: lack of documentation on restoring from bare-metal (UUID problem)
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 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.
10 years, 2 months
[Bug 595695] New: Direct links to RNs broken.
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: 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.
10 years, 9 months
[Bug 504066] New: CMS for docs.fp.org
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: 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.
11 years, 11 months
A new guide for newbies
by Dilip P Kumar
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
12 years, 4 months
Docs Project meeting summary for 25 Nov 2010
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2010-11-25/fedora_docs.20...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2010-11-25/fedora_docs.20...
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2010-11-25/fedora_docs.20...
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by Sparks at 00:00:18 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2010-11-25/fedora_docs.20...
.
Meeting summary
- ---------------
* Roll Call (Sparks, 00:00:18)
* rudi will not be with us tonight but did pass along some information
that I'll bring up a little later. (Sparks, 00:03:39)
* Follow up on last week's action items (Sparks, 00:05:32)
* Completed - Sparks to add creating and publishing links to the Docs
wiki page (Sparks, 00:05:45)
* ACTION: jjmcd to try to draw more discussion on desktop publication
on the list (Sparks, 00:06:45)
* ACTION: rudi will update wiki page on publication to desktop
(Sparks, 00:06:56)
* Removing redirects on docs.fp.o (Sparks, 00:07:28)
* When Fedora 13 was released we had just upgraded to the latest
version of Publican which changed all of our links on docs.fp.o. The
search engines hadn't had enough time to catch up with the new URLs
so we added links to act as redirects so the old URLs would still
work. (Sparks, 00:07:35)
* fedora-bookmarks package contains links that use the redirects
(Sparks, 00:08:22)
* ACTION: jjmcd to follow up on fedora-bookmarks updates (Sparks,
00:22:01)
* New Publican version (Sparks, 00:23:03)
* QA (Sparks, 00:26:27)
* LINK: http://fpaste.org/73OF/ (jjmcd, 00:44:18)
* Publishing Documentation to the desktop (Sparks, 00:51:19)
* Guide Status (Sparks, 00:51:59)
* Open floor discussion (Sparks, 00:59:04)
Meeting ended at 01:02:02 UTC.
Action Items
- ------------
* jjmcd to try to draw more discussion on desktop publication on the
list
* rudi will update wiki page on publication to desktop
* jjmcd to follow up on fedora-bookmarks updates
Action Items, by person
- -----------------------
* jjmcd
* jjmcd to try to draw more discussion on desktop publication on the
list
* jjmcd to follow up on fedora-bookmarks updates
* **UNASSIGNED**
* rudi will update wiki page on publication to desktop
People Present (lines said)
- ---------------------------
* Sparks (124)
* jjmcd (99)
* zoglesby (21)
* zodbot (4)
* jhradilek (3)
* Gearoid (2)
* sgordon (1)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJM7bdwAAoJEDbiLlqcYamxonoP/1eKff6j2dBCPN7aBikueHMX
lkZk1iaCh3c4vyNmu1Jrdovxrd2NxqdojA0NxlCVcIywwfQX8gkgRBO2+ruhCdg2
SUfWSU3KFnH8zHETLGSpzrQAtW0Bnd3cA5j+FHu7U0d32r+VGLKOZe7tehdh3hLW
UieZHMFeHzMRFBOF8WoO/kpJq0N6XEHDv3MZEGi85gw8XBugrszz7r8QwaeQqtrm
vYlZfrWMbxsgpJcVEH5wQwB46GYePUJN7MU+UCuQotpiDnpRWzNZ9xJxjzPbMqLM
WmQImfQ9n6s/7mXynczR7xWck+cGYz0rizBA/EwgZ4hCj8vMriB30kRZ3P0y1wt+
lzmwFpMUDPXIRXAsX8KRriKmZQw1YN4rS8DTvpyJuMCjwFfp3vdMPZ51biFdQLoJ
AR4INPDewvPI4iy0MQ5062g2uSX7Twci7u6F9AGehcO9UYGMQzf8EwpJDykKNDnq
R6tl2+Y/keZ1O4BsVU3IuqNERjhO2l7J8KoBWKmkLTGWIoJbW+hUBk7lY8odU8xw
1oXNvoimRjrR3cI//8JLDS0jE8xITmi/7u0IbAmHjGziZahG2i0iQW4FfgnNEwtH
e1uBrS6uTXmQb7WpTE+EM3Q2XRKjYgm6lrmXCnv00SzlMwoQDWATbOmRPHunCCTq
aBwwJ8JNWxNavHwYpSF9
=dj9C
-----END PGP SIGNATURE-----
12 years, 6 months
Fedora Docs Meeting Reminder
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
REMINDER: There will be a Fedora Docs Meeting today at 0001 UTC. The
agenda can be found at:
http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJM7WkLAAoJEDbiLlqcYamxGcsQAJkEzOztlJsU6kNJlEfSDKJa
DHE/js11g0ECPKHUlE/MhvzFe3Bovu6C7gnUcApjUXg6oTqf9/QaqDoQWOF8j3JS
2p9OBla3/x570phHzbNM6GVitpZ74wzxKjzcSNIYNJ9PhnmNRklB3wnqjJe0YkcD
ZIkm5cSCyTS8P/r8QmEI09hGRdGThy/tTft+WZpYdoJ8SpN4XmBo0BEC7NrJMtkz
y8kfRcrWOS2kCMzRnbXBRhFyhz6i/NQl+M0UulFVxLY18x+H6I86L4VsLw6zU+KJ
RgkXqrqDcMPwhBfk6hjllJBIR284xwmLnf82UI0F0scq3Q7x1y8N1JRxXCK6+7dM
39zAo1qzfl9pATQAZxQb5tNUZMfqNLrGYYtpjVDs3QC3pcLO0EpD6gCyslVIn61M
FMz4bEgvJc5M8g8oc3dvbfrmWNdFJ3/qL+qmSHaQcGp6R7GYQEke/kMaPyxr9AZv
v0QdXZdcIDMGSisohivmpkaq1O8Sh9YNY3/jjwCiIinRKxIvciR7o6RnlDEBhTVV
+R9FFv4GrKLAPK59r60eYp4CASs1bbZdeSaN9AJu9KAs6wgJIN9+CHs/xRATifJU
p1IgAkG3jYhs4EKQNm8Iy9JONTvArVxGF4buFdR8RLd4BIXpBJVLii8pZlC7uSRx
nXJTFxUclyN3ksqAdsoq
=P1qu
-----END PGP SIGNATURE-----
12 years, 6 months
QA Process
by Zach Oglesby
This email may be a little late, but at tonight's meeting I would like
to talk about possible ways to preform QA for docs, I have two
possible suggestions, and any others would be welcome.
The first possibility is to require all changes to be entered as
patches in bugzilla, each patch would then have to be verified by a QA
person prior to being included in the guide. I don't particularly like
this idea as a content writer, I don't really want to have to submit
tickets to bugzilla every time I make changes to a guide that I am the
POC on.
The second idea is to write to the proposed docs-qa list to inform the
QA team that a doc has been changed and need to be looked over. We may
be able to semi-automate this process by emailing the list when
commits are pushed a repo.
It may also be possible make use of both of these ideas depending on
the circumstance (patches from outside sources are checked via
bugzilla when a bug is submitted and internal work is done on the
docs-qa list).
Zach Oglesby
12 years, 6 months
