Re: Q3 GNOME quarterly report
Am Donnerstag, den 24.11.2011, 01:40 +0100 schrieb Gil Forcada: > El dc 23 de 11 de 2011 a les 22:26 +0100, en/na Christian Kirbach va > escriure: > > Am Mittwoch, den 09.11.2011, 21:26 +0100 schrieb Kenneth Nielsen: > > > Den 09-11-2011 20:16, Gil Forcada skrev: > > > > El dc 09 de 11 de 2011 a les 16:47 +0100, en/na Kenneth Nielsen va > > > > escriure: > > > >> Den 09-11-2011 16:14, Nguyen Thai Ngoc Duy skrev: > > > >>> On Wed, Nov 9, 2011 at 6:50 PM, Kenneth > > > >>> Nielsen wrote: > > > Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: > > I tend to strongly disagree here; very little conclusions can be drawn > > from looking at the numbers of commits, even considering the total number > > of strings > > updated in a 6 month release cycle. > > Commits can be anything between adding yourself to the list of > > translators and adding a new, entirely translated file of fivethousand new > > strings, > My point in this was that for "real" and meaningful statistics we > already have damned-lies, so if you want to see any data regarding a > language, module or release set go there and figure it out. The point is, damned-lies gives a nice statistical overview of the current translation state, but it does not provide any histroy, unless I am mistaken. Anyways, I do not want to argue. For the sake of providing just some numbers, feel free to go ahead. -- Christian Kirbach ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Am Sonntag, den 27.11.2011, 11:17 +0100 schrieb Chusslove Illich:
> > [: Christian Kirbach :]
> > [...] very little conclusions can be drawn from looking at the numbers of
> > commits [...] Is it not just the plain number of words in strings
> > translated that matter? Or less precise, the number of strings translated?
>
> meaningful metrics ("number of words translated") is not straightforward to
> define either.
Agreed, considering partial string updates amongst others.
> At any rate, I've tried to define a measure of "nominal number of newly
> translated words" (NNTW) between paired PO messages (and also how to pair
> $ cd gnome-games
> $ rev1=$(git rev-list -n 1 --before='2011-07-01' master)
> $ rev2=$(git rev-list -n 1 --before='2011-10-01' master)
> $ poediff -U -c git -r $rev1:$rev2 po/
> nominal newly translated words: 10030
I have taken a brief look at pology.
This looks like a sophisticated approach to me.
--
Christian Kirbach
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
> [: Christian Kirbach :]
> [...] very little conclusions can be drawn from looking at the numbers of
> commits [...] Is it not just the plain number of words in strings
> translated that matter? Or less precise, the number of strings translated?
Notwithstanding that this particular thread is concerned with giving numbers
for the sake of giving numbers (which gives me creeps :), certainly very
little can be seen from number of commits. But, on the other hand,
meaningful metrics ("number of words translated") is not straightforward to
define either. Given an older and a newer PO file, one must differ between
completely new messages, modified messages (what is a modified message?),
and messages to which only translation was modified (review modification).
For example, if a paragraph-length message got only one-two words changed in
original, it should not be counted as translated from scratch. Then, more
basically, how to define a "word", given that messages contain various
constructive elements (formatting directives, accelerator markers, markup),
which are not words proper but do require attention and hence add to
translation effort.
At any rate, I've tried to define a measure of "nominal number of newly
translated words" (NNTW) between paired PO messages (and also how to pair
messages from two PO files). Algorithmic details are somewhat convolved, but
the general idea is that NNTW represents equivalent effort of translating
clean text from scratch. The tool which calculates NNTW is part of Pology (
http://pology.nedohodnik.net/ ), a PO diffing script run in special mode on
two PO files or directories of PO files:
$ poediff -U foofile-older.po foofile-newer.po
$ poediff -U foodir-older/ foodir-newer/
It can also run directly on a Git repository:
$ cd gnome-games
$ rev1=$(git rev-list -n 1 --before='2011-07-01' master)
$ rev2=$(git rev-list -n 1 --before='2011-10-01' master)
$ poediff -U -c git -r $rev1:$rev2 po/
nominal newly translated words: 10030
How PO messages are paired can be checked in the PO diffing section of
Pology user manual, and how NNTW is computed on pairs in
cats_update_effort() function in poediffpatch.py file in Pology sources.
--
Chusslove Illich (Часлав Илић)
signature.asc
Description: This is a digitally signed message part.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
On Thu, Nov 24, 2011 at 2:40 AM, Gil Forcada wrote: > My point in this was that for "real" and meaningful statistics we > already have damned-lies, so if you want to see any data regarding a > language, module or release set go there and figure it out. I second that. Number of lines in a "git diff" does not show much in a git commit. .po files keep track of the filename and line number where the English string came from. If the programmer adds a line to the top of a file all the strings in the .po file will have their line number changed. At least you need to filter out changed lines that start with a "#" (a comment) if you plan to use that metric. This makes .po commits huge (lots of useless diffs) even when you're translating just one new string. -- . ..: Lucian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
El dc 23 de 11 de 2011 a les 14:20 +0100, en/na Andre Klapper va
escriure:
> On Thu, 2011-11-17 at 08:19 +0100, Gil Forcada wrote:
> > I created a dummy script that counts how many commits has been made[1]
> > during a period of time.
>
> Oh nice!
>
> > It still misses lots of things:
> > - use the correct branch for that period of time
> > - per-language metrics
> > - documentation commits
> > - ...
> >
> > The rough number just using the master branch from 2011-06-01 to
> > 2011-09-01 is: 2132 commits.
> >
> > Feel free to hack on it. As you can see on the code everything is done
> > by the fantastic git log command:
> > git log --abbrev-commit --pretty=oneline --since @{2011-06-01} --until
> > @{2011-09-01} po | wc -l
>
> You missed the 3rd quarter by one month. :)
From which period to which period goes then?
>
> > [1] https://gitorious.org/gnome-various/gnome-l10n-metrics
>
>
> I tried similar stuff for my "Projects in need" talk at GUADEC 2010.
> My (untidy & probably partially wrong) scripts are available at
> http://people.gnome.org/~aklapper/guadec2010/ .
I did know that you have been doing quite a few of these. Thanks, I will
take a look at it :)
> For any commits in /po and those git branches either defined by the
> jhbuild 3.4 moduleset or git master if not listed in jhbuild, I get 6182
> commits for Q3/2011 for GNOME Git.
I only used the modules on
http://l10n.gnome.org/languages/ca/gnome-2-32/ui/ and only for UI (/po)
maybe this is the source or my 2132 and yours 6182?
> The shell script that I used is attached.
I will take a look tomorrow. Thanks!
P.D. if you happen to come to Berlin maybe we can arrange a statistics
hackfest at my flat :)
Cheers,
> andre
>
>
> PS: For those generally interested in open source community metrics
> there is https://www.theopensourceway.org/wiki/Metrics_working_group
> though not sure how active it is.
>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n
--
Gil Forcada
[ca] guifi.net - una xarxa lliure que no para de créixer
[en] guifi.net - a non-stopping free network
bloc: http://gil.badall.net
planet: http://planet.guifi.net
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
El dc 23 de 11 de 2011 a les 22:26 +0100, en/na Christian Kirbach va escriure: > Am Mittwoch, den 09.11.2011, 21:26 +0100 schrieb Kenneth Nielsen: > > Den 09-11-2011 20:16, Gil Forcada skrev: > > > El dc 09 de 11 de 2011 a les 16:47 +0100, en/na Kenneth Nielsen va > > > escriure: > > >> Den 09-11-2011 16:14, Nguyen Thai Ngoc Duy skrev: > > >>> On Wed, Nov 9, 2011 at 6:50 PM, Kenneth Nielsen > > >>> wrote: > > Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: > > > > >> commit should roughly equal the following number of strings: > > >> > > >> number_of_updated_strings_per_cycle/(number_of_modules * > > >> number_of_updates_per_module_in_a_cycle) > > >> > > > point was exactly, that the number of commits should make a perfectly > > reasonably metric for _comparisons_ of activity, which can be used for > > the kind of "general terms" measurements that you are talking about. > > Hi > > I tend to strongly disagree here; very little conclusions can be drawn > from looking > at the numbers of commits, even considering the total number of strings > updated > in a 6 month release cycle. > Commits can be anything between adding yourself to the list of > translators > and adding a new, entirely translated file of fivethousand new strings, > I do not > see the benefit of looking at the number of commits. Correct me if I am > wrong. > > Is it not just the plain number of words in strings translated that > matter? > Or less precise, the number of strings translated? > My point in this was that for "real" and meaningful statistics we already have damned-lies, so if you want to see any data regarding a language, module or release set go there and figure it out. But the quarterly reports are meant to be a general overview of the projects, so a general overview of i18n and l10n teams is how many commits have been made. Just take the QA team as an example: they can say that in a given quarter there has been 500 bugs closed and 4000 open. What does that mean for QA team? Mostly nothing because half of the 500 closed could come from a project which was abandoned and half of the 4000 open could be from a project imported. It is just giving numbers for the sake of giving numbers. To feel that something is moving and that there are translators working all year long trying to improve each of them their own language statistics and quality. Cheers, -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Am Mittwoch, den 09.11.2011, 21:26 +0100 schrieb Kenneth Nielsen: > Den 09-11-2011 20:16, Gil Forcada skrev: > > El dc 09 de 11 de 2011 a les 16:47 +0100, en/na Kenneth Nielsen va > > escriure: > >> Den 09-11-2011 16:14, Nguyen Thai Ngoc Duy skrev: > >>> On Wed, Nov 9, 2011 at 6:50 PM, Kenneth Nielsen > >>> wrote: > Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: > >> commit should roughly equal the following number of strings: > >> > >> number_of_updated_strings_per_cycle/(number_of_modules * > >> number_of_updates_per_module_in_a_cycle) > >> > point was exactly, that the number of commits should make a perfectly > reasonably metric for _comparisons_ of activity, which can be used for > the kind of "general terms" measurements that you are talking about. Hi I tend to strongly disagree here; very little conclusions can be drawn from looking at the numbers of commits, even considering the total number of strings updated in a 6 month release cycle. Commits can be anything between adding yourself to the list of translators and adding a new, entirely translated file of fivethousand new strings, I do not see the benefit of looking at the number of commits. Correct me if I am wrong. Is it not just the plain number of words in strings translated that matter? Or less precise, the number of strings translated? -- Christian Kirbach ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
On Thu, 2011-11-17 at 08:19 +0100, Gil Forcada wrote:
> I created a dummy script that counts how many commits has been made[1]
> during a period of time.
Oh nice!
> It still misses lots of things:
> - use the correct branch for that period of time
> - per-language metrics
> - documentation commits
> - ...
>
> The rough number just using the master branch from 2011-06-01 to
> 2011-09-01 is: 2132 commits.
>
> Feel free to hack on it. As you can see on the code everything is done
> by the fantastic git log command:
> git log --abbrev-commit --pretty=oneline --since @{2011-06-01} --until
> @{2011-09-01} po | wc -l
You missed the 3rd quarter by one month. :)
> [1] https://gitorious.org/gnome-various/gnome-l10n-metrics
I tried similar stuff for my "Projects in need" talk at GUADEC 2010.
My (untidy & probably partially wrong) scripts are available at
http://people.gnome.org/~aklapper/guadec2010/ .
For any commits in /po and those git branches either defined by the
jhbuild 3.4 moduleset or git master if not listed in jhbuild, I get 6182
commits for Q3/2011 for GNOME Git.
The shell script that I used is attached.
andre
PS: For those generally interested in open source community metrics
there is https://www.theopensourceway.org/wiki/Metrics_working_group
though not sure how active it is.
--
mailto:ak...@gmx.net | failed
http://blogs.gnome.org/aklapper | http://www.openismus.com
po-commits
Description: application/shellscript
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
El dc 16 de 11 de 2011 a les 22:11 +0100, en/na Gil Forcada va escriure:
> El dc 16 de 11 de 2011 a les 18:30 +0100, en/na Petr Kovar va escriure:
> > Hi guys,
> >
> > On Wed, 09 Nov 2011 21:26:23 +0100
> > Kenneth Nielsen wrote:
> >
> > (...)
> >
> > > I think we are talking a bit past each other. My point with the first
> > > point was exactly, that the number of commits should make a perfectly
> > > reasonably metric for _comparisons_ of activity, which can be used for
> > > the kind of "general terms" measurements that you are talking about.
> > >
> > > The last part was just general ramblings about how precise metrics could
> > > be achieved, in case that is required for this purpose or in general.
> >
> > I think that this kind of activity metrics would be very useful to have in
> > the report, but then again, I don't have the spare time needed to study how
> > to actually get the data, unfortunately.
> >
> > However, I believe there is still some time left to contribute to the final
> > form of the quarterly report, so please feel free to edit / fix / add
> > whatever you want to our report that is on:
> >
> > https://live.gnome.org/GnomeMarketing/QuarterlyReports/2011/Q3
> >
> > I know it's not perfect. But I tried nevertheless. :-)
> >
> > And last, but not least, thanks much to all of you who have contributed with
> > your comments and suggestions. Much appreciated!
>
> Thanks to you for assembling it!
>
> Cheers,
>
> > Cheers,
> > Petr Kovar
> > ___
> > gnome-i18n mailing list
> > gnome-i18n@gnome.org
> > http://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
Hi,
I created a dummy script that counts how many commits has been made[1]
during a period of time.
It still misses lots of things:
- use the correct branch for that period of time
- per-language metrics
- documentation commits
- ...
The rough number just using the master branch from 2011-06-01 to
2011-09-01 is: 2132 commits.
Feel free to hack on it. As you can see on the code everything is done
by the fantastic git log command:
git log --abbrev-commit --pretty=oneline --since @{2011-06-01} --until
@{2011-09-01} po | wc -l
So no black voodoo was required :)
Cheers,
[1] https://gitorious.org/gnome-various/gnome-l10n-metrics
--
Gil Forcada
[ca] guifi.net - una xarxa lliure que no para de créixer
[en] guifi.net - a non-stopping free network
bloc: http://gil.badall.net
planet: http://planet.guifi.net
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
El dc 16 de 11 de 2011 a les 18:30 +0100, en/na Petr Kovar va escriure: > Hi guys, > > On Wed, 09 Nov 2011 21:26:23 +0100 > Kenneth Nielsen wrote: > > (...) > > > I think we are talking a bit past each other. My point with the first > > point was exactly, that the number of commits should make a perfectly > > reasonably metric for _comparisons_ of activity, which can be used for > > the kind of "general terms" measurements that you are talking about. > > > > The last part was just general ramblings about how precise metrics could > > be achieved, in case that is required for this purpose or in general. > > I think that this kind of activity metrics would be very useful to have in > the report, but then again, I don't have the spare time needed to study how > to actually get the data, unfortunately. > > However, I believe there is still some time left to contribute to the final > form of the quarterly report, so please feel free to edit / fix / add > whatever you want to our report that is on: > > https://live.gnome.org/GnomeMarketing/QuarterlyReports/2011/Q3 > > I know it's not perfect. But I tried nevertheless. :-) > > And last, but not least, thanks much to all of you who have contributed with > your comments and suggestions. Much appreciated! Thanks to you for assembling it! Cheers, > Cheers, > Petr Kovar > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Hi guys, On Wed, 09 Nov 2011 21:26:23 +0100 Kenneth Nielsen wrote: (...) > I think we are talking a bit past each other. My point with the first > point was exactly, that the number of commits should make a perfectly > reasonably metric for _comparisons_ of activity, which can be used for > the kind of "general terms" measurements that you are talking about. > > The last part was just general ramblings about how precise metrics could > be achieved, in case that is required for this purpose or in general. I think that this kind of activity metrics would be very useful to have in the report, but then again, I don't have the spare time needed to study how to actually get the data, unfortunately. However, I believe there is still some time left to contribute to the final form of the quarterly report, so please feel free to edit / fix / add whatever you want to our report that is on: https://live.gnome.org/GnomeMarketing/QuarterlyReports/2011/Q3 I know it's not perfect. But I tried nevertheless. :-) And last, but not least, thanks much to all of you who have contributed with your comments and suggestions. Much appreciated! Cheers, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Den 09-11-2011 20:16, Gil Forcada skrev: El dc 09 de 11 de 2011 a les 16:47 +0100, en/na Kenneth Nielsen va escriure: Den 09-11-2011 16:14, Nguyen Thai Ngoc Duy skrev: On Wed, Nov 9, 2011 at 6:50 PM, Kenneth Nielsen wrote: Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: Translation teams (or at least Vietnamese) tend to commit in bulk, the commit in bulk? across modules??? I mean they are not small and beautiful commits like source code patches (or I'm too accustomed to git programming style in this regard). Ahh, then I understand. But as long as we agree on that, commits are still a somewhat useful activity metric. If you are updating a fully translated desktop and ends up with a fully translated desktop, then a commit should roughly equal the following number of strings: number_of_updated_strings_per_cycle/(number_of_modules * number_of_updates_per_module_in_a_cycle) For non-100% languages there should also be a growth factor in there somewhere. But the point is, that as long as non of those numbers changes dramatically from one cycle to the next, number of commits should still make a reasonable number for translator activity _comparison_ between cycles. In any case, if we want a real number bad enough. I should certainly be possible to pull the po-file from before and after the commit and use a podiff tool to count the changes. Actually my idea was mostly to get a general feeling on how much do we commit in general and maybe on per language, that way if we start seeing less and less commits from the French team we can ask them about that or trying to help them in some sense. And also, as the quarterly reports are meant to be an overview of each team, this kind of metrics are quite useful in general terms (obviously not as a qualitative/quantitative metric for the translation project team). I think we are talking a bit past each other. My point with the first point was exactly, that the number of commits should make a perfectly reasonably metric for _comparisons_ of activity, which can be used for the kind of "general terms" measurements that you are talking about. The last part was just general ramblings about how precise metrics could be achieved, in case that is required for this purpose or in general. Regards Kenneth ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
El dc 09 de 11 de 2011 a les 16:47 +0100, en/na Kenneth Nielsen va escriure: > Den 09-11-2011 16:14, Nguyen Thai Ngoc Duy skrev: > > On Wed, Nov 9, 2011 at 6:50 PM, Kenneth Nielsen > > wrote: > >> Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: > >>> > >>> Translation teams (or at least Vietnamese) tend to commit in bulk, the > >> > >> commit in bulk? across modules??? > > > > I mean they are not small and beautiful commits like source code > > patches (or I'm too accustomed to git programming style in this > > regard). > > Ahh, then I understand. But as long as we agree on that, commits are > still a somewhat useful activity metric. If you are updating a fully > translated desktop and ends up with a fully translated desktop, then a > commit should roughly equal the following number of strings: > > number_of_updated_strings_per_cycle/(number_of_modules * > number_of_updates_per_module_in_a_cycle) > > For non-100% languages there should also be a growth factor in there > somewhere. > > But the point is, that as long as non of those numbers changes > dramatically from one cycle to the next, number of commits should still > make a reasonable number for translator activity _comparison_ between > cycles. > > > In any case, if we want a real number bad enough. I should certainly be > possible to pull the po-file from before and after the commit and use a > podiff tool to count the changes. Actually my idea was mostly to get a general feeling on how much do we commit in general and maybe on per language, that way if we start seeing less and less commits from the French team we can ask them about that or trying to help them in some sense. And also, as the quarterly reports are meant to be an overview of each team, this kind of metrics are quite useful in general terms (obviously not as a qualitative/quantitative metric for the translation project team). Cheers, > Regards Kenneth > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Den 09-11-2011 16:14, Nguyen Thai Ngoc Duy skrev: On Wed, Nov 9, 2011 at 6:50 PM, Kenneth Nielsen wrote: Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: Translation teams (or at least Vietnamese) tend to commit in bulk, the commit in bulk? across modules??? I mean they are not small and beautiful commits like source code patches (or I'm too accustomed to git programming style in this regard). Ahh, then I understand. But as long as we agree on that, commits are still a somewhat useful activity metric. If you are updating a fully translated desktop and ends up with a fully translated desktop, then a commit should roughly equal the following number of strings: number_of_updated_strings_per_cycle/(number_of_modules * number_of_updates_per_module_in_a_cycle) For non-100% languages there should also be a growth factor in there somewhere. But the point is, that as long as non of those numbers changes dramatically from one cycle to the next, number of commits should still make a reasonable number for translator activity _comparison_ between cycles. In any case, if we want a real number bad enough. I should certainly be possible to pull the po-file from before and after the commit and use a podiff tool to count the changes. Regards Kenneth ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
On Wed, Nov 9, 2011 at 6:50 PM, Kenneth Nielsen wrote: > Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: >> >> Translation teams (or at least Vietnamese) tend to commit in bulk, the > > commit in bulk? across modules??? I mean they are not small and beautiful commits like source code patches (or I'm too accustomed to git programming style in this regard). -- Duy ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Den 09-11-2011 09:45, Nguyen Thai Ngoc Duy skrev: On Wed, Nov 9, 2011 at 2:07 PM, Gil Forcada wrote: We could try to ask the git statistics gurus to make some numbers on how many commits the whole translations teams have been made, so that it can be shown in the quarterly reports... I would like to do that, I have to find how to do it thought :) Translation teams (or at least Vietnamese) tend to commit in bulk, the commit in bulk? across modules??? number of commits does not really reflect the amount of work nor progress. The following command will print the number of commits that touch po/vi.po on branch master git rev-list master -- po/vi.po | wc -l ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Hi Petr, At this momment, the Spanish team is the only one which has reached the 100% in Gimp Documentation, thanks to the good work of Ignacio Ant, who has done a great work translating this documentation. Concerning word statistics, it isn't working properly. I think its not a good idea to inculde it in the report. Cheers 2011/11/8 Petr Kovar > Hi list, > > It's the time of year again when the next GNOME quarterly reports are due, > this time for Q3 2011, i.e. from July to September. > > What do you think should be included in the update from the i18n team? > > Your thoughts, suggestions or comments are most welcome! > > Thanks, > Petr Kovar > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
On Wed, Nov 9, 2011 at 2:07 PM, Gil Forcada wrote: > We could try to ask the git statistics gurus to make some numbers on how > many commits the whole translations teams have been made, so that it can > be shown in the quarterly reports... I would like to do that, I have to > find how to do it thought :) Translation teams (or at least Vietnamese) tend to commit in bulk, the number of commits does not really reflect the amount of work nor progress. The following command will print the number of commits that touch po/vi.po on branch master git rev-list master -- po/vi.po | wc -l -- Duy ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
Op Di, 2011-11-08 om 22:10 +0100 skryf Petr Kovar: > Hi list, > > It's the time of year again when the next GNOME quarterly reports are due, > this time for Q3 2011, i.e. from July to September. > > What do you think should be included in the update from the i18n team? > > Your thoughts, suggestions or comments are most welcome! Hi Petr I'm not sure exactly what the timing is, but I think the end of the Outreach Program for Women was in the third quarter of the year. That might make it appropriate to mention the completion of the first localisation intern as part of the outreach program. Priscilla worked on Zulu localisation and improved things from about 4% coverage to about 10% coverage. Thank you for the work on the report. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/firefox-maybe-now-most-popular-africa ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Q3 GNOME quarterly report
El dt 08 de 11 de 2011 a les 22:10 +0100, en/na Petr Kovar va escriure: > Hi list, > > It's the time of year again when the next GNOME quarterly reports are due, > this time for Q3 2011, i.e. from July to September. > > What do you think should be included in the update from the i18n team? > > Your thoughts, suggestions or comments are most welcome! Some possible notes: - GNOME 3.2 was released and all teams were busy on that? - few improvements on Damned-Lies (word statistics for example) We could try to ask the git statistics gurus to make some numbers on how many commits the whole translations teams have been made, so that it can be shown in the quarterly reports... I would like to do that, I have to find how to do it thought :) Cheers, > Thanks, > Petr Kovar > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Q3 GNOME quarterly report
Hi list, It's the time of year again when the next GNOME quarterly reports are due, this time for Q3 2011, i.e. from July to September. What do you think should be included in the update from the i18n team? Your thoughts, suggestions or comments are most welcome! Thanks, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: 2010 Q3 GNOME Quarterly Report
Looks really good to me! -- Og B. Maciel GNOME Foundation Board of Directors omac...@foresightlinux.org ogmac...@gnome.org ogmac...@ubuntu.com GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
2010 Q3 GNOME Quarterly Report
Hi all, It's October, so we are asked to provide a GNOME Localization update for the upcoming 2010 Q3 GNOME Quarterly Report. The draft that I've made up so far follows. If you think something is not correct or missing (I have a feeling it might not be perfect), please feel free to share your feedback and suggestions, or simply edit the text directly at: http://live.gnome.org/GnomeMarketing/QuarterlyReports/2010/Q3 (This page is a change from the past when it was required to send update drafts directly to Stormy.) Thanks! Best, Petr Kovar --- Localization On July 29, Andre Klapper represented the GNOME Translation Project at the AGM meeting at GUADEC with a Project update report. At GUADEC, he also gave a talk on "Identifying software projects and translation teams in need" where he provided an overview of interesting data combined & gathered from Damned Lies, GNOME Bugzilla and other relevant sources. Gil Forcada, with the feedback from other community members, conducted the GNOME I18N Survey by sending a questionnaire on August 13 to every GTP language coordinator, and collecting answers for two weeks. Out of 120 coordinators, 36 answered. The rationale behind the survey was to know each other within the GNOME translation community better, and thus to find ways the GTP can improve the overall experience of translating GNOME. The sent questionnaire consisted of more than 20 questions on various areas of community l10n in GNOME, e.g. inquiring about general team information, coordinatorship & membership, team workflow, QA processes, use & evaluation of GNOME Damned Lies infrastructure, collaborating with downstream translators, other translation teams, and language institutions, community knowledge sharing, etc. As for the GNOME development itself, GTP language teams have been busy working on providing l10n support for the new GNOME stable release 2.32, which was delivered on September 29. GTP has been also investigating approaches to help out language teams that seemed to be considerably short on manpower and/or proper coordinatorship, this included the Persian and Welsh teams. We also communicated with GNOME developers to try to solve i18n issues with translating strings within submodules, strings with constructed sentences, and some other problems that (re)appeared during the Q3 period. During Q4, apart from working on l10n support for the upcoming GNOME 3, GTP community aims for identifying issues with the current i18n & l10n infrastructure inside and outside the GNOME Project, like the Git commit functionality, and solving them, hopefully implementing the necessary GTP support for repositories hosted at git.gnome.org and elsewhere. This is to be done in conjunction with the Release Team's proposal for moduleset reorganization. --- ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
