[Debian-l10n-commits] r1254 - /reports/todo/debconf8_i18n.txt

Wed Sep 17 18:40:56 UTC 2008

Author: bubulle
Date: Wed Sep 17 18:40:55 2008
New Revision: 1254

URL: http://svn.debian.org/wsvn/?sc=1&rev=1254
Log:
VERY LATE commit of my (hopefully last) updates. Please review

Modified:
    reports/todo/debconf8_i18n.txt

Modified: reports/todo/debconf8_i18n.txt
URL: http://svn.debian.org/wsvn/reports/todo/debconf8_i18n.txt?rev=1254&op=diff
==============================================================================

--- reports/todo/debconf8_i18n.txt (original)
+++ reports/todo/debconf8_i18n.txt Wed Sep 17 18:40:55 2008
@@ -144,8 +144,11 @@
 ---------------------------------------------
 The concept of an i18n "team" was discussed during that session.
 
+ Language coordinators
+ ---------------------
+
 First of all, we might want to establish the concept of team
-"coordinators" (or "leadeers"). The main point would then be to
+"coordinators" (or "leaders"). The main point would then be to
 officially establish a list of "official" leaders for each language
 supported in Debian ("supported" meaning there exists a localization
 effort for that language in one of the l10n areas that are specific to
@@ -156,15 +159,48 @@
 might want to change this.
 
 Most participants in the meeting agreed that it would help getting in
-touch with people who have a good knowledge in each laguage l10n
-activities, as well as a goo dknowledge of that language itself.
-
-The list of coordinators would then become public and the nominated
-persons would then have the duty, if they accept, to follow teh
-activities of Debian i18n efforts (reading the debian-i18n mailing
-list might be enough for this).
-
-.../...
+touch with people who have a good knowledge in each language l10n
+activities, as well as a good knowledge of that language itself.
+
+The list of coordinators would then become public on a wiki page and
+the nominated persons would then have the duty, if they accept, to
+follow the activities of Debian i18n efforts (reading the debian-i18n
+mailing list might be enough for this).
+
+Some roles have been mentioned for language coordinators:
+ * defining work methods for the team (for instance, that must be done
+   for the DDTP before any DDTP work  starts)
+ * act as a proxy between the translators and the core team
+ * act as a point of contact for Debian project contributors
+   who need to have input about a specific language
+ * participate to i18n IRC meetings
+
+ Core team
+ ---------
+
+The concept of a "core team" for i18n has also been decided. This is
+indeed formalizing something that already exists with the de facto lead taken by Christian Perrier on i18n and l10n activities in the project, as well as the work done by a few "key" people.
+
+That core team would, for the beginning, include Christian Perrier
+<bubulle at debian.org>, Felipe Augusto van de Wiel <faw at debian.org>,
+Nicolas FranÃ§ois <nicolas.francois at centraliens.net>, Michael Bramer
+<grisu at debian.org>.
+
+As of now, this is not a closed list but more formalizing what's
+already happening.
+
+Core team duties:
+ * be responsible for the infrastructure and coordinate developments
+ * organizing IRC meetings (reference: 
+   http://fedoraproject.org/wiki/L10N/Meetings)
+ * schedule regular public meetings of the core team
+ * maintain the list of language coordinators (add new ones, ping
+   existing ones, resolve disputes in case there is a conflict in an
+   l10n team)
+
+We need to find the right balance between a too formal process (which
+might scare people from "one-person" teams) and a too loosy one where
+nobody knows who's doing what.
 
 i18n work sessions 4: DDTP
 --------------------------
@@ -180,13 +216,13 @@
 descriptions (apt, aptitude, etc.) will display up-to-date versions
 and not old stuff from 2006.
 
-The discussion about the "openess" of the system is still strong. In out
+The discussion about the "openess" of the system is still strong. In our
 i18n community, we clearly have two visions:
 - "open to everybody with low constraints": this is the original design of
-the DDTP: everybody can show up and start translating. This allows for a
-quick growth of the amount of translations to the expense of their uality
+  the DDTP: everybody can show up and start translating. This allows for a
+  quick growth of the amount of translations to the expense of their qualityÂ ;
 - "control the quality": this is wished by the most structured teams
-and a concern bringed by many maintainers
+  and a concern bringed by many maintainers.
 
 Felipe explained how he tries to balance this for the Brazilian Portuguese
 team by basically controlling that nobody is translating outside the team
@@ -204,7 +240,7 @@
 situation where DDTP translation with PO files could be possible
 without hooking Pootle to this). Michael will work on PO import (PO
 export is alredy implemented and just needs to be automated).
-
+Using PO would of course be optional.
 
 
 i18n work sessions 4: Extremadura
@@ -223,13 +259,24 @@
 The presence of Neil Williams and at least one dpkg developer (for
 tdeb work) is wished.
 
+The meeting would be shared with the QA meeting. We might have some
+constraints in terms of number of participants, so we will need to
+reduce it to the strict minimum. Steve McIntyre mentioned that he
+cuold consider using Debian funds to sponsor some participation in
+case that could be needed.
+
+(post Debconf note: the meeting organization has started and is
+coordinated on event-extremadura-meetings at teams.debian.net, which
+anyone can subscribe to on http://teams.debian.net. The size
+constraints are quite strong)
+
 Achievements of Debcamp/Debconf
 -------------------------------
- * Thanks to the support of the ftp-masters, we could find a agreement on
+ * Thanks to the support of the ftpmasters, we could find a agreement on
    how to provide the translations of the package description in the
    archive. This was awaited for more than FIXME years.
    FIXME: section for the technical details?
-   FIXME: This is still a temporary solution for Lenny, and should be
+   This is still a temporary solution for Lenny, and should be
    changed to a solution were the translation are attached to packages to
    allow the transition of translation with the packages.
  * Several improvements were discussed before debconf for the coordination


