docs February 2011

docs@lists.stg.fedoraproject.org

35 participants
34 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

Migrating Docs to new Transifex server
by Dimitris Glezos 01 Mar '11

01 Mar '11

Hey all. As many of you already heard, we are migrating our Transifex server to fedora.transifex.net. For more info, please refer to the logistics and translation lists. We have already manually migrated the core Fedora apps (ones we are upstream and are affected by the string freeze). The Docs projects will need to migrate its projects as well. Compared to our old setup, we have changed the way project maintainers interact with Transifex. We now have a command-line client to push source files (POT) & pull translations (PO). Here are the instructions on how to manage your docs project. Create your project =================== As an example, I already migrated the release notes: http://www.transifex.net/projects/p/fedora-release-notes/ To create your project and setup your client, run the following. This only needs to be run once: - Login or Create account on Transifex.net - Create project: Transifex → Projects → Create → MyProjectName - Share teams with Fedora Project: Transifex → MyProjectName → Access Control → Outsource → "Fedora Project" - Push existing translations to the server: $ git clone http://git.fedorahosted.org/git/anaconda.git $ cd anaconda $ tx init $ tx set --auto-local -r anaconda.master 'po/<lang>.po' \ --source-lang en --source-file po/anaconda.pot Especially for docs, which have a bunch of POT files, we'll need multiple "tx set" commands like this, which we get by running the following: for POTFILE in `ls pot`; do FILE=$(basename "$POTFILE" .pot) tx set --auto-local -r fedora-docs-relnotes.$FILE --source-language=en \ --source-file pot/$FILE.pot "<lang>/$FILE.po" --execute done These commands will create a file called '.tx/config', which tells the client what translations to pull from the server and in which local files to put them. This will be needed by other Docs people to test, so you should commit this file in your repo. Feel free to open it, modify and check whether things look correct. Pushing source languages & pulling translations =============================================== Now we can simply push our source files to the server: $ tx push --source Pushing translations for resource fedora-docs-relnotes.Amateur_Radio: Pushing source file (pot/Amateur_Radio.pot) ... Since we want to pre-populate our translations too from our existing ones, we do this. $ tx push --translations Pushing translations for resource fedora-docs-relnotes.Amateur_Radio: Pushing 'da-DK' translations (file: da-DK/Amateur_Radio.po) ... Because Publican generates a bunch of unneeded (mostly empty) translation files, your push will take a million years and make our server hate you forever. When you are ready to publish a document, you'll need to pull fresh translations. To do this, simply run 'tx pull'. More info: http://help.transifex.net/user-guide/client/client-0.4.html#for-developers Your project in the Fedora 15 release ===================================== We track the Fedora 15 release here: http://www.transifex.net/projects/p/fedora/r/fedora-15/ To include your project in the Fedora 15 release (or a separate Fedora Docs), a Fedora L10n admin needs to do the following. If you're not a member of the Fedora L10n Admin team, just ping us and we'll include your project in the release. Transifex → Fedora Project → Release 15 → Edit → Resources → MyProject Downloading translations of a whole release =========================================== We encourage translators to translate using the online editor, since it offers many additional features than the offline one. However, we sometimes prefer to download translation files, either for offline translation or for backup. Translators can pull only the translation files they want for a whole release, without worrying about source code or other languages (including English). Here's how: $ cd my-translations $ tx set --auto-remote http://www.transifex.net/projects/p/fedora/r/fedora-15/ $ tx pull --language el $ ll translations/*/el.po translations/anaconda.master/el.po translations/usermode.master/el.po More info: http://help.transifex.net/user-guide/client/client-0.4.html#auto-remote http://help.transifex.net/user-guide/client/client-0.4.html#for-translators Hope this helps! -d -- Dimitris Glezos Transifex: The Multilingual Publishing Revolution http://www.transifex.net/ -- http://www.indifex.com/

9 17

GNOME Docs Hackfest
by Paul W. Frields 01 Mar '11

01 Mar '11

Shaun McCance (shaunm) came by IRC and was asking whether the Fedora Docs team would like to send someone to the GNOME Docs Hackfest coming up March 17-22 in Toronto. They have a bed available for either a male or female contributor in a room already generously provided by the GNOME Foundation. In other words, there's one open bed in a male-occupied, double occupancy room, and one in a female-occupied, double occupancy room. You'd only need to find funding for an airfare. I'm checking with the Community Architecture team to find out if they're willing to provide this funding. I brought this up in IRC and shaunm talked with various Docs people previously, but I haven't seen this covered in any agendas, meeting notes, or, more importantly, on the mailing list recently. Have you guys discussed this event, and if so, was something decided? I might have missed it! So if so, please point me in the right direction. :-) -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ Where open source multiplies: http://opensource.com

3 3

FAQ for migration to transifex.net
by Paul W. Frields 26 Feb '11

26 Feb '11

I set up a separate FAQ page for the migration to transifex.net, found here, and linked to it from the main migration information page: https://fedoraproject.org/wiki/FAQ_on_migration_to_transifex.net It would be great if interested folks would contribute questions we can answer for developers in one place. The page has been seeded with a few already. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ Where open source multiplies: http://opensource.com

1 0

L10N migration to transifex.net
by Zach Oglesby 25 Feb '11

25 Feb '11

Over the last few days it has been decided that we are going to move all of Fedora's translation efforts away from a self hosted solution and on to transifex.net. The migration over to tx.net also means a huge jump to version 1.1 from 0.7, with that we no longer have support for tx to commit to the git repo[1]. This is going to require a redesign of our workflow to insure that we are publishing the most up to date. The new system requires us to use a command-line tool, that is in the process of being packaged, and works much like git[1]. This means that we now have to pull in translations by hand, but tx.net can monitor the git repo (over HTTP) for changes that we make (you can also push via tx command). Trans.fp.o will be turned off on Feb 18th, so we need to make sure that we have all of the current trans worked saved and then we need to work on moving to tx.net. We still have a little time to get that part of this figured out since we are not due to make POT files until March 15th, but we need to start looking at what this means for publishing to docs.fp.o and for packaging into the release. It is important to remember that the pains that we may be dealing with are not because of the migration to tx.net but because of the upgrade to 1.1, which would have happend regardless. If anyone has any questions or concerns please don't hesitate to ask! I am going to add this to the agenda for tonights meeting as well. [1]: http://help.transifex.net/user-guide/one-dot-zero.html [2]: http://help.transifex.net/user-guide/client/client-0.4.html -- Zach Oglesby GPG Key: F20C4707 zoglesby on irc.freenode.net https://fedoraproject.org/wiki/User:Zoglesby

19 33

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs February 2011