Being a volunteer does not mean you don't have any 
[responsibilities](https://wiki.gnome.org/TranslationProject/TeamCoordinatorResponsibilities),
 
since you are still a coord. I am not asking for a change in the first 
place only because I can't find a better candidate for that position.

Anyway, thanks for appearing and pushing those things to Git. Don't hurry, 
take your time -- although I still think you should take a look at the GTK+ 
mess.

On Tuesday, November 10, 2015 at 2:24:42 PM UTC-5, Aron Xu wrote:
>
> It depends on the availability of my free time (and it's 3AM for me 
> atm), and please don't try to push some pressure to other people in 
> any mean, whatever you do in that direction will probably slow down 
> everything because we are all volunteers. 
>
> This is my last comment on this very thread. 
>
> Regards, 
> Aron 
>
> On Wed, Nov 11, 2015 at 3:03 AM, Mingye Wang <[email protected] 
> <javascript:>> wrote: 
> > Just saw your recent pushes to git on the list, great. Looking forward 
> to 
> > more updates. 
> > 
> > On Tuesday, November 10, 2015 at 8:34:16 AM UTC-5, Aron Xu wrote: 
> >> 
> >> I just want to reiterate that please be a bit more patient, or you 
> >> might be slowing things down (I know it's already quite slow). 
> >> 
> >> Regards, 
> >> Aron 
> >> 
> >> On Tue, Nov 10, 2015 at 7:28 AM, Mingye Wang <[email protected]> 
> wrote: 
> >> > Hi, 
> >> > 
> >> > Thanks for that reply. Now I finally got time to read it carefully. 
> >> > Apart from correcting your misunderstandings on the current master 
> >> > status, I have something more to say. 
> >> > 
> >> >> accept updates to released branches .. only if the master branch is 
> >> >> updated at the same time [sentence restructured] 
> >> > 
> >> > For versions, actually we don't lack people putting things onto 
> master, 
> >> > neither do we lack people porting pending changes on old branches 
> into 
> >> > master. We need people who backports master changes into the stable 
> >> > branches that are still being maintained officially by GNOME. 
> >> > 
> >> >> I don't really think releasing those ones are really meaningful... 
> >> >> Updates sent to old branches 
> >> > 
> >> > The branches marked as stable (not 'old stable') are older than 
> master, 
> >> > but they are still being maintained. GNOME 3.18.2 and GTK+ 3.18.3 has 
> >> > just been released, and I consider it a shame that without my 
> backported 
> >> > (upload master translations and let msgmerge do the job) GTK+ 3.18 
> >> > translation, users are going to be in some astonishment seeing 
> >> > translations for Copy and Paste were missing. 
> >> > 
> >> > It's nice to aim for the future, but why not make the current status 
> >> > better too with just a little effort? 
> >> > 
> >> >> limitations of manpower 
> >> > 
> >> > For selecting reviewers, you might want to start with translators who 
> >> > are more experienced (e.g. a lot) or are physically closer to you 
> (e.g. 
> >> > Bin Li). To be honest, with the online diff capacity, reviewing 
> changes 
> >> > is really not that time-consuming. 
> >> > 
> >> > Anyway, narrow down your candidate list first. Just focus on a few 
> >> > particular persons to check for, and then you can select nice 
> reviewers 
> >> > from them. For translations by those narrowed-down group of 
> translators, 
> >> > you can even simply go to there profile page and hand-run some easy 
> >> > sampling so you can determine if they're capable faster. You can 
> later 
> >> > find more reviewers by reading the comments from the first-batch 
> >> > reviewers. 
> >> > 
> >> > * * * 
> >> > 
> >> > I hope I am not getting too offensive.. Bai sent me some 
> shxt_linus_says 
> >> > PDF a couple of days ago and, well, it's somehow funny to read. 
> >> > 
>
> --
Regards,

Arthur2e5 
_______________________________________________
gnome-i18n mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Reply via email to