On Tue, May 17, 2011 at 5:10 AM, noriko noriko@fedoraproject.org wrote:

Kévin Raymond さんは書きました:

...

Hi guys,

I know that release time is a really busy time for everyone, but this release was not really funny for every projects.

First of all, release notes was not easy to find in transifex, as there were not linked to the Fedora Documentation project. This is why there are only 4 languages mostly translated[1] while last time for Fedora 14 release, we had 10 languages 100% translated.

I've heard that there was some issue for making a link at tx.net. Docs team has been required to learn Tx and move their documentation to within very short time frame, thus it is not hard to imagine that book owners have experienced the hardest time. So I echo your concern completely that F15 has less documentation localized than F14. Good new is that the release note now should be appeared under Fedora Documentation.

...

We should work closer between docs and l10n teams.

Indeed, it will be nice if l10n team can be notified by docs team when especially release note is ready for translation. Besides, it also is encouraged that translators join #fedora-docs channel on freenode to discuss any concern.

I do. My apologies to all translators, I've been there to follow the release notes integration and was finally told that an announce would be done in the mailing list, but didn't notice that it was not done.

...

I can't see neither Dutch, nor Chinese nor French release notes version under docs.fpo[3]. Would it be linked in GA time ?

This is left for docs team to answer...

...

What about packages already available in our F15 systems? Those files are not up to date. Should we fill a trac ticket to get a rebuild? There should be an issue building the french one, I can't build it locally but I don't really know publican (a tag should be missing in the po file).

What does 'package' refers to?

It refers to the package which should be embedded in the iso file, that's why the deadline was important. https://admin.fedoraproject.org/pkgdb/acls/name/fedora-release-notes

Software translation deadline was over. Any  string freeze break should be reported. For publican, there is Publican User Guide. This might help. http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/...

In fact my issue is coming from the po file, there should be a missing tag in a string, but msgmerge didn't help. Gonna see later on.

...

In an other hand, docs maintainers created two teams for french while only one is existing[4]. Could anyone fix it?

This should be able to fix by Transifex team once tx client is released. http://lists.fedoraproject.org/pipermail/docs/2011-May/013336.html

Both teams were created, hence tx push was working. But yeah, it could helps.

...

Last words, it seems that not all guides have moved to transifex.net, I can't find the security one[5]. Could someone check them?

Sometime ago, I read the post in docs lists, which said that this guide owner have had no time for F15 and looked for help. I am just guessing that this guide might be given up for F15.

This email was also in order to see if some translators could join the docs team. This doc only need to be pushed in transifex.net, and to be built frequently. (I don't know the process, every book maintainer has to built its own book?). It doesn't need to be updated to the GNOME 3 environment (nor has been other guides pushed to transifex.net).

I understand that learning how to use the new transifex.net could takes time (I still see developers who didn't notice major changes).

So far, hard work has been done, thank you guys!

noriko

...

[1] https://www.transifex.net/projects/p/fedora-release-notes/r/all-resources/ [2] https://translate.fedoraproject.org/projects/p/docs-release-notes/c/f14/ [3] http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Notes/index.html [4] https://bugzilla.redhat.com/show_bug.cgi?id=699980 [5] https://bugzilla.redhat.com/show_bug.cgi?id=704849

Regards,

-- docs mailing list docs@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs

On Tue, May 17, 2011 at 6:10 AM, noriko noriko@fedoraproject.org wrote:

I've heard that there was some issue for making a link at tx.net. Docs team has been required to learn Tx and move their documentation to within very short time frame

FWIW, following the instructions we posted should Just Work™, since the client does all the hard work for you. Some issues were fixed (eg. large number of files).

If anyone needs any kind of help, please don't hesitate to ping me, #transifex or nb who has migrated a bunch of docs. We're always online and can help with the migration if needed. =)

This should be able to fix by Transifex team once tx client is released. http://lists.fedoraproject.org/pipermail/docs/2011-May/013336.html

So far translation has worked with special teams where needed. Some docs owners have been using the devel version of tx-client which has support for language mapping since March.

easy-install --upgrade transifex-client

http://help.transifex.net/user-guide/client/#customizing-the-language-mappin...

Hope this helps!

-d

We are missing the underlying issue here.

Whenever you make a significant change in a project, any project, you need to identify the new or affected tasks and adjust the schedule accordingly.

The Board decided not to do that. Whether they were fixated on a specific release date, felt somehow magic would happen, or were simply clueless I can't say. But the board decided not to schedule the tasks necessary to accommodate the tx change, so those tasks never happened.

Now it's a surprise?

--McD

On Wed, May 18, 2011 at 6:00 AM, John J. McDonough wb8rcr@arrl.net wrote:

Whenever you make a significant change in a project, any project, you need to identify the new or affected tasks and adjust the schedule accordingly.

Honestly, I think what was needed was done.

We started enough time before the Docs string freeze and announced in public the current issues & plan. Docs was on the call to give a +1 and the Board's opinion was taken into account as well. We migrated one project of this type and prepared very detailed migration instructions for the rest. One person in Docs was identified to migrate more projects and act as the local expert. To override the locale naming issue, new teams were created and the tx-client was adapted early on.

Yes, we could be more active in monitoring the docs migration process, but I don't see how the Board could help with that. There was plenty of time to ask questions and manage things, IMHO.

-d

The Board decided not to do that.  Whether they were fixated on a specific release date, felt somehow magic would happen, or were simply clueless I can't say.  But the board decided not to schedule the tasks necessary to accommodate the tx change, so those tasks never happened.

Now it's a surprise?