Re: Translation status pages
On Wed, September 14, 2005 15:37, Danilo Å egan wrote: Hi everyone, Maybe we should look into providing alternative status pages until Carlos responds. Anyone with a strong machine with a lot of unused CPU cycles on a fat-pipe willing to donate a couple of hours of runtime a day for our l10n-status pages? Just wondering... Why isn't this done on a gnome.org server? Does it use too much CPU? Maybe it'd be possible to only update the data when a po file gets committed? Vincent -- Les gens heureux ne sont pas pressés. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation status pages
Kt, 2005 09 15 12:46 +0200, Vincent Untz rašė: Just wondering... Why isn't this done on a gnome.org server? Does it use too much CPU? Maybe it'd be possible to only update the data when a po file gets committed? It will be useless then, it has to be updated when string changes happen in the code, as well. Žygis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation status pages
On Thu, September 15, 2005 12:57, ®ygimantas Beruèka wrote: Kt, 2005 09 15 12:46 +0200, Vincent Untz raÅ¡Ä: Just wondering... Why isn't this done on a gnome.org server? Does it use too much CPU? Maybe it'd be possible to only update the data when a po file gets committed? It will be useless then, it has to be updated when string changes happen in the code, as well. Right. I should not answer mails when I'm hungry :-) Vincent -- Les gens heureux ne sont pas pressés. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation status pages
Hi Vincent, Today at 12:46, Vincent Untz wrote: On Wed, September 14, 2005 15:37, Danilo Å egan wrote: Hi everyone, Maybe we should look into providing alternative status pages until Carlos responds. Anyone with a strong machine with a lot of unused CPU cycles on a fat-pipe willing to donate a couple of hours of runtime a day for our l10n-status pages? Just wondering... Why isn't this done on a gnome.org server? Does it use too much CPU? Maybe it'd be possible to only update the data when a po file gets committed? Well, we are definitelly going to request another machine from Gnome for all the status stuff: we currently have separate stuff for translation status (Carlos), doc status (Shaun) and doc translation status (myself). We have already discussed joining all our status stuff together (so we eg. do one CVS checkout, instead of three :), but we have not yet gotten around to implementing it. Since we also keep up with branches, this should turn out to be useful for jhbuild as well. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Seeking advice on team issues
I am writing this email because of my frustration with a situation in the Persian GNOME team. I am seeking the advice of other people in the GNOME project. The situation is getting on my mind, specially because a dear friend and colleague, Behdad Esfahbod, is on the other side of matter. It recently got much worth because he checked in a translation by himself to the GNOME CVS, without confirmation from me or other reviewers of the Persian team (that at the same time removed a copyright line, which made me more frustrated). I can't speak for Behdad, but I can explain some of the processes that has led to his objections, according to my interpretation of things. To understand these, you should know that I became the Persian translation coordinator only because I was the first translator (and the only translator for a while), not because I have been elected or anything. But nobody has challenged my role either, as far as I can tell. You should also know that Iran is not a signatory of any of the international copyright conventions, but has an national copyright law only protecting works first created in Iran. 1) Originally in the project, because of my worries over the copyright status of things (which was mostly based on my sad experience with the Persian KDE project) and my incomplete (but improving) understanding of the copyright law, we had random policies imposed by me on the project. I used FSF as the copyright holder. This is the first Persian translation ever checked in to the GNOME CVS: http://cvs.gnome.org/viewcvs/gtk%2B/po/fa.po?rev=1.1 Later, I decided to ask (require?) every volunteer translator to sign the famous FSF copyright disclaimer from the Translation Project and send it to the FSF offices in paper before I check in any translation from her or him to the GNOME CVS. We used FSF copyrights for a while, but after a while found that according to Iranian law, FSF will most probably be unable to use the protection of the Iranian copyright law, which would make the work practically public domain. I then decided to switch the copyright to the FarsiWeb project, which was then a non-profit project by Sharif University of Technology and Science and Arts Foundation. This was not a problem since again almost all contributors were members of the FarsiWeb project. We kept pointing project outsiders to the FSF disclaimer, but changed the copyright of the existing files to the FarsiWeb project in new CVS check-ins: http://cvs.gnome.org/viewcvs/gtk%2B/po/fa.po?rev=1.26 Later, we found that since that project is no legal entity and cannot be well-defined, it is not entitled to hold copyright over anything. At the same time, the university and the foundation had pushed the FarsiWeb project to become a spin-off company, which we founded in September 2003 (Behdad is a co-founder). We then transferred of rights to work we had created to this company, and we started to use the company copyright. We assumed that we can keep the work copyrighted in both Iran and outside Iran by using a double copyright line, one for the company and one for FSF: http://cvs.gnome.org/viewcvs/gtk%2B/po/fa.po?rev=1.39 After a while, I found ways to recruit people to do GNOME translation, including hiring a professional translator, Meelad Zakaria, to work on GNOME translation. After a period of his working on GNOME, he was becoming frustrated so we started to hold by-invitation translation parties in Sharif University campus. It was a great success and has led to activation of possible contributors (or them understanding that Persian l10n is not really that easy). During these parties, several friends and almost all company-employees contributed translations, which were later reviewed and checked in to the GNOME CVS. It was with these parties that we finally passed the first 50% frontier. Every person participating in these translation parties that was not a company employee has signed a copyright disclaimer in Persian, with a similar text to the FSF translation disclaimer, but additionally explicitly letting us transfer the rights to the FSF or any other organization we feel appropriate. Like the FSF disclaimer, we mentioned that this applies to translations of freely redistributable software programs. In my reading of the FSF disclaimer, which I have personally signed, it applies only to translations that we provide to the FSF itself (i.e. putting an FSF copyright notice on its header), but Behdad has claimed that we the people who have signed that disclaimer CANNOT claim copyright on any of our translations anymore. I am assuming that he claims every translation of a free software program I will do in my life after signing that disclaimer will be copyrighted by the FSF. But I guess I may not speak for him. An email of his about the matter is here: http://lists.sharif.edu/pipermail/farsi/2005-April/000328.html But all this has an allegedly dark side. People who contacted us over the Internet or did not reside in
Re: Seeking advice on team issues
Thanks a lot Roozbeh for raising the issue. I think it makes sense for people to wait until I write down my side of the story too. I'll do that before the end of the weekend. behdad On Thu, 15 Sep 2005, Roozbeh Pournader wrote: I am writing this email because of my frustration with a situation in the Persian GNOME team. I am seeking the advice of other people in the GNOME project. The situation is getting on my mind, specially because a dear friend and colleague, Behdad Esfahbod, is on the other side of matter. It recently got much worth because he checked in a translation by himself to the GNOME CVS, without confirmation from me or other reviewers of the Persian team (that at the same time removed a copyright line, which made me more frustrated). I can't speak for Behdad, but I can explain some of the processes that has led to his objections, according to my interpretation of things. To understand these, you should know that I became the Persian translation coordinator only because I was the first translator (and the only translator for a while), not because I have been elected or anything. But nobody has challenged my role either, as far as I can tell. You should also know that Iran is not a signatory of any of the international copyright conventions, but has an national copyright law only protecting works first created in Iran. 1) Originally in the project, because of my worries over the copyright status of things (which was mostly based on my sad experience with the Persian KDE project) and my incomplete (but improving) understanding of the copyright law, we had random policies imposed by me on the project. I used FSF as the copyright holder. This is the first Persian translation ever checked in to the GNOME CVS: http://cvs.gnome.org/viewcvs/gtk%2B/po/fa.po?rev=1.1 Later, I decided to ask (require?) every volunteer translator to sign the famous FSF copyright disclaimer from the Translation Project and send it to the FSF offices in paper before I check in any translation from her or him to the GNOME CVS. We used FSF copyrights for a while, but after a while found that according to Iranian law, FSF will most probably be unable to use the protection of the Iranian copyright law, which would make the work practically public domain. I then decided to switch the copyright to the FarsiWeb project, which was then a non-profit project by Sharif University of Technology and Science and Arts Foundation. This was not a problem since again almost all contributors were members of the FarsiWeb project. We kept pointing project outsiders to the FSF disclaimer, but changed the copyright of the existing files to the FarsiWeb project in new CVS check-ins: http://cvs.gnome.org/viewcvs/gtk%2B/po/fa.po?rev=1.26 Later, we found that since that project is no legal entity and cannot be well-defined, it is not entitled to hold copyright over anything. At the same time, the university and the foundation had pushed the FarsiWeb project to become a spin-off company, which we founded in September 2003 (Behdad is a co-founder). We then transferred of rights to work we had created to this company, and we started to use the company copyright. We assumed that we can keep the work copyrighted in both Iran and outside Iran by using a double copyright line, one for the company and one for FSF: http://cvs.gnome.org/viewcvs/gtk%2B/po/fa.po?rev=1.39 After a while, I found ways to recruit people to do GNOME translation, including hiring a professional translator, Meelad Zakaria, to work on GNOME translation. After a period of his working on GNOME, he was becoming frustrated so we started to hold by-invitation translation parties in Sharif University campus. It was a great success and has led to activation of possible contributors (or them understanding that Persian l10n is not really that easy). During these parties, several friends and almost all company-employees contributed translations, which were later reviewed and checked in to the GNOME CVS. It was with these parties that we finally passed the first 50% frontier. Every person participating in these translation parties that was not a company employee has signed a copyright disclaimer in Persian, with a similar text to the FSF translation disclaimer, but additionally explicitly letting us transfer the rights to the FSF or any other organization we feel appropriate. Like the FSF disclaimer, we mentioned that this applies to translations of freely redistributable software programs. In my reading of the FSF disclaimer, which I have personally signed, it applies only to translations that we provide to the FSF itself (i.e. putting an FSF copyright notice on its header), but Behdad has claimed that we the people who have signed that disclaimer CANNOT claim copyright on any of our translations anymore. I am assuming that he claims every translation of a free software program I will do in my life
Weekly translation status for Gnome 2.10
Translation status changes from 2005-09-08 to 2005-09-15. Total message count is stable at 0. Average change during this period was 0.000%. Top 5 movers of the week: Supported languages (more than 80% strings translated). Smallprint: this is automated report. Though, if something doesn't work as expected, don't curse the machine: it's Danilo's fault. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Weekly translation status for Gnome 2.12
Translation status changes from 2005-09-08 to 2005-09-15. Total message count is stable at 0. Average change during this period was 0.000%. Top 5 movers of the week: Supported languages (more than 80% strings translated). Smallprint: this is automated report. Though, if something doesn't work as expected, don't curse the machine: it's Danilo's fault. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
