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.
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.
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.orghttps://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.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: SRPMs fail to build in Koji
https://bugzilla.redhat.com/show_bug.cgi?id=513907
Summary: SRPMs fail to build in Koji
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: high
Component: publican
AssignedTo: jfearn(a)redhat.com
ReportedBy: eric(a)christensenplace.us
QAContact: extras-qa(a)fedoraproject.org
CC: jfearn(a)redhat.com, fedora-docs-list(a)redhat.com,
mmcallis(a)redhat.com
Classification: Fedora
Description of problem: SRPMs fail to build in Koji due to the following error:
Processing files: fedora-security-guide-en-US-1.0-16.fc12.noarch
error: Two files on one line: /usr/share/applications/Fedora
error: File must begin with "/": Projectfedora-security-guide-en-US.desktop
Version-Release number of selected component (if applicable): 0.44-0.fc11
Possible Fix: Remove the %{?vendoropt} from
desktop-file-install %{?vendoropt}
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications %{name}.desktop
or remove %{vendor} all together.
I'll be testing this soon to see if I can provide a patch.
--
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.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Publican migration
https://bugzilla.redhat.com/show_bug.cgi?id=504064
Summary: Publican migration
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
Figure out steps for a migration of each guide; track that in each guide's
Trac. Installation Guide migration branch in git; task in progress, possible
work at http://fedoraproject.org/wiki/FedoraEvents/FAD/FAD_SCaLE
--
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.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Toolchain next steps
https://bugzilla.redhat.com/show_bug.cgi?id=504063
Summary: Toolchain next steps
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
Sorting out what fedora-doc-utils does, where to use Publican, etc. --
Principals to discuss status, progress, direction on IRC.
--
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.
One of my tasks has been to review the schedule. Of course, we all
should be looking at it. I've been struggling some to make sense of it.
There are a couple of issues, but even a few issues can make it very
confusing.
You should all be aware that John has posted the schedule at
http://poelstra.fedorapeople.org/schedules/f-14/
If you look at f-14-docs-tasks.html it can be very confusing since
release notes, announcements and guides tasks are all mixed together.
The report, f-14-docs-tree-tasks.html is a lot easier to digest. Until
you have your head around that one, the docs combined with translation
and releng are totally confusing, so look at the tree tasks first.
It is a pity that you don't seem to be able to get a Gantt chart out of
taskjuggler, but if you download the two files from John's "source"
directory (f-14.tjp and reports.tji) and open them up in taskjuggler,
you can see the dependencies in the source. To do that:
1) Select the tasks tab on the left
2) Highlight the task you wish to examine (note that in general
the tasks are folded into higher level tasks)
3) The task will be highlighted in the source on the right, and
if there is a dependency, it will say "depends" on the right
under the highlighted task name
It still isn't super-simple since Docs is only a tiny part of the whole
release, and of the hundreds of "external to docs" tasks, there are
perhaps a dozen that actually matter to us directly, and they don't
always show up within the folded group (e.g. Beta Release Notes), so it
isn't always obvious why a particular task has to happen on a particular
day without a fair amount of digging.
Rudi and I will be getting updates to John, so if you notice anything
that seems out of place please let us know.
Thanks,
--McD
One of the wiki pages identified as "needing love" was the one
documenting the workflow we use:
https://fedoraproject.org/wiki/Docs_Project_workflow
I've made a start at updating that, trying to be a bit more graphical.
(OK, I'm an engineer; I tend not to read the manual but I do look at the
pictures!)
We definitely need more detail underneath this, but I would like some
feedback on whether this is a helpful approach. All of the old
material, some of it badly out of date, is still there but commented
out.
Some of the things I thing we need:
- Guidance on editing the wiki
- Guidance on applying for groups
- Guidance on conversion to XML, both manual and via the python tool
- Howto XML -> Publican -> docs.fp.o
Probably lots of others.
Any feedback appreciated.
--McD
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Need to package OpenWYSIWYG
https://bugzilla.redhat.com/show_bug.cgi?id=516794
Summary: Need to package OpenWYSIWYG
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: high
Component: project-tracking
AssignedTo: fedora-docs-list(a)redhat.com
ReportedBy: eric(a)christensenplace.us
QAContact: eric(a)christensenplace.us
CC: stickster(a)gmail.com
Blocks: 504066
Classification: Fedora
Download: http://code.zikula.org/scribite/downloads
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee 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: Need to package FCKeditor
https://bugzilla.redhat.com/show_bug.cgi?id=516793
Summary: Need to package FCKeditor
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: high
Component: project-tracking
AssignedTo: fedora-docs-list(a)redhat.com
ReportedBy: eric(a)christensenplace.us
QAContact: eric(a)christensenplace.us
CC: stickster(a)gmail.com
Blocks: 504066
Classification: Fedora
Download: http://code.zikula.org/scribite/downloads
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.