docs March 2011

docs@lists.fedoraproject.org

25 participants
38 discussions

[Fwd: ACTION REQUIRED: Important changes to Fedora translation workflow]
by Dimitris Glezos 04 Mar '11

04 Mar '11

I'm forwarding jsmith's email to devel-announce, although we've already migrated most docs. -d -------- Original Message -------- Subject: ACTION REQUIRED: Important hanges to Fedora translation workflow Date: Thu, 3 Mar 2011 10:46:28 -0500 From: Jared K. Smith <jsmith(a)fedoraproject.org> Reply-To: devel(a)lists.fedoraproject.org To: devel-announce <devel-announce(a)lists.fedoraproject.org> Quick Summary --- The Fedora translation workflow has changed. If you are a developer of a package being translated by the Fedora Translation (L10n) Project, you must change your workflow slightly if you want translated strings to appear in your software package. Tools and assistance are available to make this workflow as simple as possible for developers. Read below for details. Details --- Over the past couple of weeks, we've made some improvements and infrastructure changes to the Fedora translation system. We've moved from a self-hosted version 0.7 instance of the Transifex software to a hosted version of the 1.1-dev version at Transifex.net. The upgrade from version 0.7 to version 1.0 (and beyond) introduces a number of important changes for developers and packagers. Please pay close attention to this email, particularly if your software package uses translations provided by the Fedora Translation team. While the changes aren't terribly complicated, they do have a bigger impact on the developer than they do on the translation team. The most visible change is that Transifex’s native integration with source code management systems has been replaced by a mechanism for automatic updates. Transifex now watches an HTTP view of a repository for change notifications. In addition, there is now a more secure command-line tool for project maintainers and translators. This new command-line tool has been packaged for Fedora in the "transifex-client" package. It is currently available in Rawhide (pre-F16), and in the "updates-testing" repositories for Fedora 13, 14, and 15, and EPEL 5 and 6. Here's the new workflow: This series of steps only needs to be run once for a project. * The developer installs the "transifex-client" package: yum --enablerepo=updates-testing install transifex-client * The developer runs the "tx init" command in the top level folder of the project. * The developer runs the "tx set" command according to the transifex-client user guide found at: http://help.transifex.net/user-guide/client/client-0.4.html. This creates a small config file, .tx/config, which can be committed in the repository for re-use, if desired. This series of steps are run on as as-needed basis: * The developer updates and commits his or her POT file to the project's repository at string-freeze time or as needed. * Transifex watches an HTTP link to that POT file and auto-updates its English strings regularly, *OR* the developer can also push the POT file to Transifex (either manually or as part of a build script) by using the "tx push" command. * Translators work inside Transifex. Translated strings are stored inside of Transifex, and are *not* pushed automatically to the developer's repo. * Before rolling a release, the developer runs 'tx pull' (either manually or from a build script) to fetch the latest translation files from Transifex. Translation files do not need to live in the repo, although the developer may commit and store copies if desired. For more details on the features of the new version of Transifex and more help on using the transifex client, please refer to either http://help.transifex.net/user-guide/one-dot-zero.html or the Fedora-specific wiki page at https://fedoraproject.org/wiki/FAQ_on_migration_to_transifex.net. If you have technical questions, feel free to ask questions in the #fedora-l10n or #transifex IRC channels or on the devel mailing list. -- Jared Smith Fedora Project Leader _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- trans mailing list trans(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/trans -- Dimitris Glezos Transifex: The Multilingual Publishing Revolution http://www.transifex.net/ -- http://www.indifex.com/

1 0

[Help files] - Should help be local or internet based?
by Jose Manimala 03 Mar '11

03 Mar '11

Hello docs team, Need some help/advice. I am working with FES[1] on getting a desktop entry file that points firefox to the domain http://help.fedoraproject.org/ and acts as the first point of contact for the user to search for help channels used by fedora. Would it be better to have an offline version of the website as the first stage(an html doc) and then for more goto http://help.fedoraproject.org/. Is this redundant or would just a desktop entry file to http://help.fedoraproject.org/ suffice? ~~~~~~~~ [1] - https://fedorahosted.org/fedora-engineering-services/ticket/17 Thank you Jose

3 3

Docs Meeting Notes for March 3, 2011
by Zach Oglesby 03 Mar '11

03 Mar '11

Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2011-03-03/fedora-meeting.2… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2011-03-03/fedora-meeting.2… Log: http://meetbot.fedoraproject.org/fedora-meeting/2011-03-03/fedora-meeting.2… Meeting summary --------------- * roll call (zoglesby, 00:01:13) * Follow up on last week's action items (zoglesby, 00:02:41) * LINK: https://fedoraproject.org/wiki/Fedora_15_Alpha_release_notes (zoglesby, 00:05:39) * LINK: http://nb.fedorapeople.org/docs.pdf (nb, 00:07:54) * ACTION: jjmcd to look into docs.old to make sure nothing needs saved (zoglesby, 00:11:33) * Fedora 15 Schedule (zoglesby, 00:11:47) * Release Notes (zoglesby, 00:13:59) * Guide Status (zoglesby, 00:16:42) * ACTION: zoglesby to email list asking maintainers to create transifex.net accounts (zoglesby, 00:19:38) * LINK: http://alt.fedoraproject.org/pub/alt/stage/15-Alpha.RC2/ (nb, 00:23:41) * LINK: http://alt.fedoraproject.org/pub/alt/stage/15-Alpha.RC2/ (nb, 00:23:43) * Outstanding BZ Tickets (zoglesby, 00:23:54) * LINK: http://tinyurl.com/lbrq84 (zoglesby, 00:24:31) * GNOME Docs Hackfest (zoglesby, 00:26:42) * ACTION: zoglesby to email list about Open Help Conference (zoglesby, 00:29:54) * Open floor discussion (zoglesby, 00:30:34) Meeting ended at 00:32:53 UTC. Action Items ------------ * jjmcd to look into docs.old to make sure nothing needs saved * zoglesby to email list asking maintainers to create transifex.net accounts * zoglesby to email list about Open Help Conference -- Zach Oglesby GPG Key: F20C4707 zoglesby on irc.freenode.net https://fedoraproject.org/wiki/User:Zoglesby

1 0

Meeting Reminder
by Zach Oglesby 02 Mar '11

02 Mar '11

Reminder that we have a Docs meeting at 00001 UTC in #fedora-meeting https://fedoraproject.org/wiki/Docs_Project_meetings * Follow up on last week's action items (10 minutes) ** jjmcd and nb to discuss redirect ** zoglesby to start working on Alpha Release Notes ** zoglesby to mail devs about alpha release notes ** zoglesby and rudi identify any issue with trans migration and docs.fp.o ** jjmcd to look into docs.old to make sure nothing needs saved * Fedora 15 Schedule (5 min) * Release Notes (15 min) ** Leadership ** Schedule *** #link https://fedoraproject.org/wiki/Release_Notes_schedule * Guide Status (10 minutes) ** Ready for F15? ** GNOME 3 * Trans Migration (10 minutes) * Outstanding BZ Tickets (10 minutes) ** #link http://tinyurl.com/lbrq84 * Open floor discussion (5 minutes) -- Zach Oglesby GPG Key: F20C4707 zoglesby on irc.freenode.net https://fedoraproject.org/wiki/User:Zoglesby

1 0

Re: GNOME Docs Hackfest
by Christopher Antila 02 Mar '11

02 Mar '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If only this were a month later! I'm attending university only a 1.5-hour, $15 bus-ride from Toronto, and I would really enjoy taking part in the hackfest... but I can't justify leaving school for that long on those days :( Maybe next time. Christopher. > Date: Mon, 28 Feb 2011 10:39:23 -0500 > From: "Paul W. Frields" <stickster(a)gmail.com> > Subject: GNOME Docs Hackfest > To: "Fedora Documentation (Docs)" <docs(a)lists.fedoraproject.org> > Message-ID: <20110228153923.GK20632(a)localhost.localdomain> > Content-Type: text/plain; charset=us-ascii > > 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 > > ------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iQEcBAEBAgAGBQJNbcsiAAoJEInCktGVqZ8VUU8H/0SAVBGknYGrbBxOaf6e1+kj fljGApMPdXvGNXMYfOsSS2h8KRLHQ3+y2614dziEGayPARe1AOwQzoIuy2xwOAzN aL7MIN4yF/aO2k9e/CQGcZujTIpj26nJPmqpIVOitfGjAA89wYJNHxYVAwKM9Ojz aOeJpg/XpadxwMii9no1aLrGWjjCD6iqHiF00UgaHhPtK4KKTvU9PmpfTkvv8nYV ebLotw1WSMTDbpLTxT2nraPtObNp7vEs3TvgjO0v7qBqTe4+Hz8MH9l8HPmUMu9i ciojBqx2uR0u53fmkqSzf62+ej06FFwCFCf03ylc6v4dcWHDVdak/2IUXDJuFLo= =GBY+ -----END PGP SIGNATURE-----

2 1

Re: L10N migration to transifex.net
by Tom Callaway 01 Mar '11

01 Mar '11

On 02/28/2011 11:58 PM, Mike Hideo wrote: > How do we get a commitment that there will be a process to govern this > decision? What would you like? We can schedule a formal review process with the various community groups to discuss the future of L10N technologies after the F15 release, if that is what you're looking for. ~tom == Fedora Project

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs March 2011