From kde-i18n-doc  Thu Jul 18 08:27:27 2013
From: Sebastien Renard <renard () kde ! org>
Date: Thu, 18 Jul 2013 08:27:27 +0000
To: kde-i18n-doc
Subject: akademy l10n BoF wrap up
Message-Id: <1802697.5iGMBybEgE () eniokafox>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=137413658517601

Hello everybody,

We had a BoF during akademy 2013 (thanks Luigi for organization !). Her=
e is a=20
wrap up of main topics we discussed.

Attendees :
    Marta (Poland)
    Shinjo (Korea)
    Luigi (Italia)
    Luciano (Italia)
    S=E9bastien (France)
    Lasse (Finland)
    Adrian (Galicia)
    Claus (Danish, wikis)


l10n.kde.org website changes
----------------------------------------------------
* GSoC: integration with identity.kde.org, property assignment  for=20
translation files/modules

* More information here: http://community.kde.org/KDE_Localization/LTMT=


* Some comments:

=09- Translators will need an identity account to book a file. An optio=
n=20
could be to allow  "anonymous locking" by team coordinators (with note =
about=20
the name  of the unregistered user) for new unregistered users
=09- Booking file list won't be exactly the same as statistics file lis=
t; a=20
file is booked for all branch (stable and trunk or summit if used)


Proposal about 3-months releases:  is one month of string freeze enough=
?
-----------------------------------------------------------------------=
-----------------------------------------------
* Most people in Bof thought that it is not a big issue

* For teams that are using the summit workflow the change will be very =
small.

* Point of attention: late branch merging adding lots of translation la=
te in=20
the process (that is mostly due to git transition, not directly related=
 to=20
release length but it can be worst with short release cycle).


Integration of wiki translations in the gettext-based workflow
-----------------------------------------------------------------------=
---------------------------
* Two separate issues with current situation:
=09- most of wiki translators are not related to local translation=20
team.wiki-only people need integration into the team.=20
=09- bad quality (all teams in Bof testify that)

* We all agree on the following:
=09- We would like to unify wiki and legacy translation team for each=20=

country (consistency, quality...)
=09- We would like to allow each to choose between two organization mod=
es:
=09=09o Option 1: Integration in current worfklow: exporting of pot + b=
ulk=20
import from scripty, merging  and translation locked in wiki. Same work=
flow as=20
for some websites (www_www, okular, www_edu etc.)
=09=09o Option 2: use wiki for translation, no integration with scripty=
.=20
But unified team (mailing list, coordinator etc.)


Report a typo
----------------------
* It is not very easy for users to report a typo. Many way to do it (ma=
il to=20
translator, to mailing list, open a bug in bugzilla and guess that i18n=
 is for=20
translation etc.)

* Some team (Poland) use translation credit field to ask users to repor=
t typo=20
to team mailing list.

* We agree on the following:
=09- buzilla is not suitable to report typo / translation errors
=09- about application =3D> translation is too hidden
=09- a simple mail to locale l10n team is the easiest way to get useful=
l=20
feedback

* ...and we propose this:
=09- add a help menu entry "Report a typo" aside "Report a bug" (or ins=
ide=20
bug wizard first screen) that just open mail editor to locale translati=
on team
=09- team mailing list will be a string that each team will translate t=
o=20
locale mail point of contact (mailing list or individual email)
=09- cherry on the cake: automatically add information on catalogs load=
ed by=20
application in the report
=09- from the dev point of view, this could be overloaded to use differ=
ent=20
point of contact for third party application that use kde framework. Th=
at the=20
way it works today for the bug report part.

    =3D>kdelibs folks are ok to do that (at least David and Kevin are :=
p)


Things that could/should be handled automatically:
-----------------------------------------------------------------------=
------------
* Version numbers, documentation release dates, contributor names, emai=
ls, ...
* Strings used repeatedly throughout KDE
  =3D> some work  is currently done for doc release date by Luigi


Fixing typo or missing directly in code:
-------------------------------------------------------------

* We all agree on the fact that translators should be officially allowe=
d to fix=20
English strings and add or update context directly in code without prio=
r=20
developer agreement.

* This should be done for simple things (string changes, adding or chan=
ging=20
context). Any other change must involve developers collaboration.

    =3D> this is already done but just need to be said and written ;-)


Cheers
--=20
S=E9bastien