docs September 2010

docs@lists.fedoraproject.org

31 participants
49 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 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

[Bug 513907] New: SRPMs fail to build in Koji
by Red Hat Bugzilla 23 Nov '10

23 Nov '10

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.

1 23

[Bug 504064] New: Publican migration
by Red Hat Bugzilla 29 Oct '10

29 Oct '10

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.

1 7

[Bug 504063] New: Toolchain next steps
by Red Hat Bugzilla 29 Oct '10

29 Oct '10

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.

1 11

jjmcd disappearing
by John J. McDonough 04 Oct '10

04 Oct '10

I need to be out of town on family business for an indeterminate period of time, and I will probably be netless for long periods of time. Fortunately, there aren't a lot of release notes tasks coming up, and most are pretty straightforward. I have been tracking the tasks on https://fedoraproject.org/wiki/Release_Notes_schedule If you can cover some of the tasks it would be helpful; be sure to note them done on that page so someone else doesn't try to duplicate your work. 10/4 Stop sending updated POs I will arrange for this to happen by editing my crontab 10/6 Remind L10N no more POTs Someone should send a note to trans(a)lists.fedoraproject.org reminding them that updated POTs will cease for a week. 10/6 Wiki Freeze This one is a little tedious, but easy. Go to each of the beats and delete {{Docs_beat_open}} if it exists, then insert {{Documentation_closed_beat| http://docs.fedoraproject.org/release-notes/f14/en-US/html/sect-Release_Not… where sect-Release_Notes-Printing.html is replaced with the appropriate section for the beat. 10/6 through 10/11 Go through the beats and update the XML as appropriate. There don't seem to have been a lot of updates, but the devel list was reminded of the freeze a couple days ago, so a rash of updates in the next few days wouldn't be a huge surprise. I think we need to rework the systemd stuff but I don't know what the actual status is, disappeared entirely or testable. Perhaps stickster can help here. Rahul and Lennart have been providing the information from dev. systemd is detailed in the System Daemons section, but it also has a mention in Overview. 10/11 Review the document, make final edits, and make a final set of POTs for L10N. Then let L10N know the POTs are available 10/12 Build GA htmls until 11-Oct This should still be happening, so no action is needed other than checking fedorapeople to be sure updated documents (or error logs) are continuing to appear 10/14 Remind L10N translation deadline - another note to trans-list 10/20 f-r-n.rpm - This actually needs to be done a few days earlier to be ready for the compose, but as late as possible to capture as many translations as possible. I hope to be back for this, but it is pretty straightforward. Instructions are at https://fedoraproject.org/wiki/Getting_the_release_notes_to_Bodhi and https://fedoraproject.org/wiki/Giving_a_document_karma Stay in close touch with nb to be sure the package makes it into the compose on time. Nick knows how to check where it is and how to move it along. If you have a language that is close to 100% but doesn't build, you can often simply correct the error in the po file. Most commonly a translator munged up a ulink tag, or removed the semicolon from a &PRODVER; or similar symbol. Emacs is real smart about po files, smarter than me, so I use gedit for this task. Thanks for all your help. --McD

2 1

LXDE update for the Fedora 14 Release Notes
by Eric Christensen 03 Oct '10

03 Oct '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christoph, Can you give me an update on what the differences are between Fedora 13 and 14 in regards to LXDE? Were there any updates? What is the version that will ship with F14? Thanks, Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMo9VKAAoJEDbiLlqcYamx0ucP/RWMRgk2y0HZMwoh7zzWuwdG BPwFBQmuYNlaKhnUOoz6qy2iPXM5QF1TOfg+Os/g7Fk7slE5J8HDMhVzXVFYPoap 67JunMY92amlPwysRen79aTvHbSoX9tNpRSF6nkRK/bP80A6VqYWzrDtk0FdLchw 0+8c7ybh5TG5GLZw5d5eYS71/1idftRxsjkLRDuiw7I39yd7S0daUikusWe4G7oP EWc6Kqk+FkOSDmRjx/cx+owFZJPtLNkpj5mVnfLbKabY3A2ugDcGiL9EMILkfC5L SKbXSt9l5Kkmr7M1tfPirh61WGwJQwcNorVuAmmS1y/Q01upY1Pg/yBcZHcka4R7 looAF5HjkqQocqMAnFc1KbmhSHTFSC48TTP2J8Bs9dzVq6CV0uydXlKXpPDOa7S+ z2iddk9aXqp/bLjyANwlFYm0Cqobno6cxj0c597PW/XsQ9t9stkfaVBwWxY0sYL/ X3hG8SLDAaiG66Eibrw/fDLuZLMESMhjp+HnLIEnXrVUV1f84Jm/nxVB47I1cdLE usoJQigJ5vcsTMjVeP99XICK8D8znaOzqtiNh7/dVUxMB9hqAUEW0Jl/I/aDUctR EGZsyNIEwlDuGlzA/q3hfCS6ssgEnCPBnU2KM995tYUXdpAQteQ1uGEuc1WsG+gp qtkYXSOYyuxe7WNrtywT =o3NV -----END PGP SIGNATURE-----

3 4

Making F14 Docs bits available to translators
by Eric Christensen 01 Oct '10

01 Oct '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Now is the time to get your F14 bits submitted to Transifex. Part of this is regularly building what does get translated into html (or html-single or whatever) and submit it to your fedorapeople site so they can see the final output. When you start doing this please let the translators know so they know where to find the bits! Fedora 14 is upon us! Thanks, Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMpNquAAoJEDbiLlqcYamxHNwQAIroFPw8/aLuO3pfRd0WGk58 QVDApaGH8EmQHREKQbxEz13Itsv17qTG/B+UHgUoGPZXQcAnOq8IYFa+oSMY/BLW crh3hOhy7yu+N9c8v8kecRqIAc1hs5tdXXUDDmNdklUMW15VYa8XZpoV2QXvgQfH DDdLrtMPvACHPUxDcI0mL1w+7nxv+wELsarlinBrkIcFvqZpj7hFxSdW1juS/V54 ixMEQJjhEn5Lx7DWve0/wXfhd3D8uisNvxogXRYx+pupWSi0plfaKD/MmpF5Vyaw yFAfGP7gv4zilKbMKTENAjLN/ykCaxN5AU0qNlogS0SU9VNbyIZgBtKzlnGcMepq phu1Wk8inYkdfwTQ2+XNv+eTQU2oSZtgpT9qePEIfMTtzE1qACBkPWvfQ3mLwnWQ iOTKvIQ+kA5hn5SzfKcJJTtNHDYdR3ySDmuGmrPFaQYWuU3BgDbSGbev9fqxl0Uz aR0KIa414YX39vG3Bwm6imZZ3LtdB3ABehaikt4a8yPAyncuE09Gzc0nDy3OZCIF OLSSySF7YtKuaDrL7itHi3u2WD2H0s+zoLUIR5l+/myFkfH04v+Yphyg1804p8QE Ej5pkhAIYesmKp7yp6tOCdzjPdnOjqAAR4y68HOa1EU7OxzsF0ssf3QuEtJiJ4cq F80L9ZIEyBK54SDaL4qj =XKRw -----END PGP SIGNATURE-----

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs September 2010