<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><div class="gmail_quote"><div dir="ltr">On Tue, Oct 10, 2017 at 1:08 AM Vinzenz Vietzke <<a href="mailto:vinz@vinzv.de" target="_blank">vinz@vinzv.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi there,<br>
<br>
I recently went through many parts of Xfce's i18n infrastructure and<br>
documentation. To make it short: lot's of old stuff, many things<br>
unmaintained but truly a lot of useful gems grown throughout the years.<br>
<br>
So following up is my proposal for reorganizing i18n in Xfce, split into<br>
two phases. I put it up on this list to reach more people.<br>
<br>
<br>
A. Short term<br>
<br>
1. Dump mailing lists. One list (xfce-i18n) is enough and for<br>
language-specific questions, discussions a short [LANG] tag added to the<br>
email topic should do the distinction job.<br>
Bonus: questions might be answered quicker as more people read them.<br></blockquote></div></div></div></div></blockquote><div><br></div><div><div style="font-family:tahoma,sans-serif" class="gmail_default">Yes, 1 Mailist is enough and most (just most not all) project I know use only one.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2. Before dumping email all lists subscribers directly and (of course)<br>
telling them about. Plus asking them if they are on this list alread<br>
and, which is even more important, if they would like to help out on<br>
Transifex.<br>
<br></blockquote></div></div></div></div></blockquote><div><br></div><div><div style="font-family:tahoma,sans-serif" class="gmail_default">There are cases of Transifex contributors not in any of the lists so if is possible send a mail</div><div style="font-family:tahoma,sans-serif" class="gmail_default">to the contributos on transifex too could help them know that there is a maillist or see that is</div><div style="font-family:tahoma,sans-serif" class="gmail_default">encouraged to at least be part if it.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3. Transifex needs coordinators for every language. If there is no one<br>
coordinating a language there should be some "super-coordinators" as<br>
backup. These persons shouldn't be devs or at least not core devs.<br>
Stacking work leads to problems.<br>
<br>
<br></blockquote></div></div></div></div></blockquote><div><br></div><div><div style="font-family:tahoma,sans-serif" class="gmail_default">Yes a super-cordinator could go in hand since there are some languages without cordinators</div><div style="font-family:tahoma,sans-serif" class="gmail_default">as you mentioned, also there are cordinators that are MIA too.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
B. Long term (mostly RFC)<br>
<br>
1. Ease up the introduction process. Someone dropping by at Transifex<br>
sees the need of some translation work in his language. If he decides to<br>
register at TX, to join team *and* do work: yeah, cool!<br>
But forcing him to additionally join the mailing list and introduce<br>
himself is a major blocking thing. I guess it's something from the<br>
pre-Transifex days where quality assurance had to be done manually. But<br>
with the split of translators & reviewers over TX this should be obsolete.<br>
<br></blockquote></div></div></div></div></blockquote><div><br></div><div><div style="font-family:tahoma,sans-serif" class="gmail_default">Well so far many aren't arealdy on the mailist so dropping it is ok.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
2. Wiki needs clean up. There are lots of really, really useful things.<br>
But as well there is lots of ancient, outdated stuff. Unfortunately most<br>
stuff is mixed so there needs to be manual work done.<br>
TBD: a process of cleaning up, either dumping everything and rebuilding<br>
or the other way around.<div style="font-family:tahoma,sans-serif;display:inline" class="gmail_default"></div><br>
<br></blockquote></div></div></div></div></blockquote><div><br></div><div><div style="font-family:tahoma,sans-serif" class="gmail_default">Wiki just need a way to anyone to contribute, I have tryed sign-in, log-ing but i failed... is</div><div style="font-family:tahoma,sans-serif" class="gmail_default">somewhat looked or need special permissions?<br></div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3. Revise the use of Transifex. It's not self hosted and it's<br>
proprietary but it does the job. There are up- and downsides of it so in<br>
the light of the Git hosting discussion TX should also be reconsidered<br>
*openly*.<br>
<br>
<br></blockquote></div></div></div></div></blockquote><div><br></div><div><div style="font-family:tahoma,sans-serif" class="gmail_default">I still remember why we move to transifex.</div><div style="font-family:tahoma,sans-serif" class="gmail_default">"Was because the self hosting was becoming so time consimong and we havent <br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">updated the stuff and it was breaking" or something like that...</div><div style="font-family:tahoma,sans-serif" class="gmail_default">Returning to self host will be like return to the same thing that we move to</div><div style="font-family:tahoma,sans-serif" class="gmail_default">reduce the burder over the maintainers.</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">Also I thing with all we could ended trying to chew more that our maws can handle, so</div><div style="font-family:tahoma,sans-serif" class="gmail_default">better see how the git-self-host-move go and then evaluate the option and the options of move</div><div style="font-family:tahoma,sans-serif" class="gmail_default">and where to move with the translations.<br></div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Generally speaking I'd step up for both doing "dirty jobs" as well as<br>
coordination work.<br>
Thanks for your time reading this!<br>
<br>
Looking forward to your comments,<br>
vinz.<br>
--<br>
Xfce.space | skyrocket your desktop usage<br>
<a href="https://xfce.space" rel="noreferrer" target="_blank">https://xfce.space</a><br>
______________________________<wbr>_________________<br>
Xfce4-dev mailing list<br>
<a href="mailto:Xfce4-dev@xfce.org" target="_blank">Xfce4-dev@xfce.org</a><br>
<a href="https://mail.xfce.org/mailman/listinfo/xfce4-dev" rel="noreferrer" target="_blank">https://mail.xfce.org/mailman/<wbr>listinfo/xfce4-dev</a></blockquote></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Xfce4-dev mailing list<br>
<a href="mailto:Xfce4-dev@xfce.org">Xfce4-dev@xfce.org</a><br>
<a href="https://mail.xfce.org/mailman/listinfo/xfce4-dev" rel="noreferrer" target="_blank">https://mail.xfce.org/mailman/<wbr>listinfo/xfce4-dev</a><br></blockquote></div><br></div></div>