1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
<div>Wolfgang,</div><div><br></div><div>We need a mailing list in mageia server for discuss about translate process in portuguese (pt_br). I suggest <a href="mailto:br-mageia-i18n@mageia.org">br-mageia-i18n@mageia.org</a></div>
<div><br></div><div>Thanks,</div><div><br></div><div>Júnior</div><br><div class="gmail_quote">2010/12/1 Wolfgang Bornath <span dir="ltr"><<a href="mailto:molch.b@googlemail.com">molch.b@googlemail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
As announced in the latest blog entry (<a href="http://blog.mageia.org/?p=271" target="_blank">http://blog.mageia.org/?p=271</a> )<br>
the founders asked me to start building the i18n and documentation<br>
team organisation. As the documentation section is still under<br>
construction I will postpone the building of this team until open<br>
questions are answered (as a preview, Calenco (<a href="http://www.calenco.com" target="_blank">http://www.calenco.com</a>)<br>
will possibly be chosen as collaboration tool for that).<br>
<br>
So let's start right away with the procedure (please read to the end<br>
to get all infos):<br>
<br>
First I want to make a distinction between the translation of<br>
application menues/strings translation and floating text translation<br>
of documents. As everybody knows there are important differences in<br>
the workflow, the tools, etc. between these 2 sections of i18n,<br>
although there are many translators working in both areas. I want to<br>
focus on the application translation first because text translation<br>
depends on the documentation team's work, which is not yet ready to<br>
go.<br>
<br>
I suggest the following steps:<br>
<br>
- Announce team bulding on the i18n list (this mail here)<br>
<br>
- Let language teams organize themselves internally, name contacts/team leaders<br>
<br>
- First meeting on IRC<br>
<br>
<br>
The simple task of this team building process is to organize all the<br>
different language groups, find a way for general discussions,<br>
participate in regular meetings, choose the representatives which will<br>
report to the community council and/or be the contact for the council.<br>
This will be achieved in several steps:<br>
<br>
- setting an organisational structure for each language. This will be<br>
done inside each group. The task of the internal groups is to<br>
implement short communication ways inside each language group to<br>
coordinate work for the language in question. This way local<br>
discussions will not clutter the i18n mailing list. Another task may<br>
be to "hire" more people interested in this line of work. There are<br>
many translators out there who would help translating documents but<br>
not so many who woould do the "string work". We should find ways to<br>
improve this situation :)<br>
<br>
- - Each language group can set up their own mailing list or wiki<br>
page (example: French and German) for internal communication. If there<br>
is a necessity to set up a mailing list on the Mageia server pls tell<br>
me.<br>
- - Each language group selects 2 "contacts" which may be also the<br>
team leaders but not necessary. These contacts will meet regularly on<br>
IRC - please only one (1) person per language - with the contacts of<br>
other language groups to discuss and report from and to their language<br>
group<br>
<br>
I discovered that a large number of people who have put their names on<br>
the wiki page for translation work are not subscribed to this list. I<br>
can't possibly add more than 70 addresses to this mail, so I suggest<br>
that those who are subscribed may tell others they know in their<br>
language group about all this. We may find a better solution in the<br>
first meeting. I will of course copy this information on the top of<br>
the wiki page as well.<br>
<br>
I'd like to see the internal organisation done by Wednesday next week,<br>
at least a "get together" and the selection of the contacts and/or<br>
leaders. So, pls stick your heads together and talk to each other :)<br>
<br>
<br>
2. First meeting<br>
<br>
First meeting should be next week. As time/date I suggest Thursday,<br>
December 9, 2010, at 18:00 Paris time (GMT +1).<br>
<br>
I know that it is difficult to set a time/date which will suit<br>
everybody because we are living in different time zones. We may find a<br>
solution during discussing this in the meeting, a possible solution<br>
may be a changing time every other week, so everybody will find a time<br>
which suits him. Of course there will be meeting logs available in the<br>
wiki so everybody can follow the logs and discuss in his language<br>
group or in this list here.<br>
<br>
Meetings will be held in #mageia-i18n on Freenode.<br>
<br>
I will hold the chair for the first meeting, then we will see if<br>
anybody wants to do that or if I go on.<br>
<br>
Participants will be the contacts of the language groups but, again, -<br>
PLEASE - only one person per language. Meeting experiences have shown<br>
that there is a limit of participants above which an organized meeting<br>
is not possible (see full logs of the founders meetings to understand<br>
what I mean with "organized meetings") :)<br>
<br>
Suggested topics of the 1st meeting will be:<br>
<br>
- setting of team structures (internal per language, overall<br>
structure, naming of leaders and contacts to report to community<br>
council)<br>
<br>
- General i18n wiki page, mailing lists (wiki page should link with<br>
documentation wiki wrt i18n HowTos), what do we need?<br>
<br>
- collaboration tools for i18n<br>
- - Transifex is already set on the server. It may be good if<br>
somebody who knows it could give a bit of insight during the meeting<br>
<br>
Meeting should not be longer than 2 hours, exceptions possible. The<br>
first meeting I expect to be a little longer as we will set the first<br>
stones.<br>
<br>
Then we'll go from there.<br>
<br>
Comments welcome.<br>
<font color="#888888"><br>
--<br>
wobo<br>
</font></blockquote></div><br>
|
