Re: Import from Launchpad
2008-02-05 klockan 08:54 skrev Danilo Šegan: > "Social" as in involving people and communication, versus "technical" > problem (since it's completely possible to restrict access to any of > the languages in Ubuntu to whoever you wish). There is no way we > could have fixed the problem without people approaching us and telling > us something is wrong. Upstream Gnome people don't want/need to get involved in Ubuntu-specific launchpad translations stuff---they might as well use another distribution, so the incentive for participating in an Ubuntu community process is pretty much non-existent. Therefore it is unreasonable to ask upstream people to get involved with downstream distributions. Coordinating the upstream translations and keeping those up-to-date and of a high quality is already time consuming enough for most of us. mvrgr, Wouter -- :wq mail [EMAIL PROTECTED] web http://uwstopia.nl if this is right :: i'd rather be wrong :: rather be blind-- incubus signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
On Tue, Feb 05, 2008 at 08:54:52AM +0100, Danilo Šegan wrote: > Yesterday at 20:22, Djihed Afifi wrote: > > > +1 from me for Khaled Hosny to get launchpad team coordinatorship. He > > sent an email earlier. > > I've emailed current coordinator so I am waiting for response. > > >> Solving social problems is really up to social elements: people. > > > > I hope that you don't mean that this is a social problem. > > "Social" as in involving people and communication, versus "technical" > problem (since it's completely possible to restrict access to any of > the languages in Ubuntu to whoever you wish). There is no way we > could have fixed the problem without people approaching us and telling > us something is wrong. There have been *loads* of complaints on planet gnome about this. I know various questions have been asked directly as well. However, just because someone needs to communicate the problem doesn't make it social. If some language doesn't want Ubuntu to change their strings (especially as they have real evidence that the quality decreases), then this advice should be followed. If I read https://bugs.edge.launchpad.net/rosetta/+bug/188907/comments/8, then it is a problem within Ubuntu that the quality is subpar. Currently the efforts are focussed on improving that quality instead of following the wish of the GNOME translator teams. e.g. with remarks such as | 'However, that might also remove bug fixes' I further don't understand the response to | - Upstream teams get bug reports about strings that are correct | upstream but have been changed in launchpad You are suggesting to push launchpad bugs to GNOME Bugzilla and that GNOME teams should check things in Ubuntu. While the issue is that GNOME Bugzilla gets complaints because Ubuntu changed the translation. Meaning: quality decreased and GNOME people get bugged about things they aren't responsible for. | Since we can't accept the simple solution of disallowing Ubuntu | translations through Launchpad This pushes the problem towards GNOME translator teams. Now they have to coordinate with one distribution. I have seen some of the translations that occurred for the Dutch language. The quality was *really* bad. Meaning: the translation contained stuff like 'Paste' was translated into 'Insert' (forgot the exact translation, but it didn't make any sense), etc. Theoretically Ubuntu might want to change the translation somehow... but I wonder if that really occurs in practice. Especially with some of the really bad translations that have I've seen. > I am pretty sure you are aware that even GNOME has had it's own share > of bad translation coordinators for certain languages, and they have > only been changed when someone else stepped forward. I don't see how this is relevant. This is about fixing a problem that occurs for certain languages where Ubuntu overrides the upstream languages. -- Regards, Olav ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
On Mon, Feb 04, 2008 at 03:14:30PM +0100, Danilo Šegan wrote: > On January 25th, Kenneth Nielsen wrote: > > > Yeah it was done by filtering svn-commit-lists. And yeah I certainly > > understand that it is a bad idea if many people do it, which is why I think > > it is a good idea if it is done on a GNOME server and sent out centrally > > That shouldn't be too hard to do in damned-lies. I can help someone > work on that :) KDE has something like commit-filter. Suggest someone sets that up on a server somewhere. I don't see the requirement to have it on a GNOME server. This pushes the burden on a non existent sysadmin team. -- Regards, Olav ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-keyring not updating properly [DL]
hi, actually it's a fault from both gnome-keyring and DL if you ran intltool-update -m in the po subdirectory of gnome-keyring you will see that there's missing files in POTFILES.in dunno why DL didn't show this error in the pages :-/ so, yes, file a bug cheers, El dt 05 de 02 del 2008 a les 01:54 +0100, en/na Jorge González González va escriure: > Hi, > > the module gnome-keyring is not being updated properly in DL: > http://l10n.gnome.org/module/gnome-keyring > if you see the module statistics there are few translations at 98% > although there is no string left to translate, not empty nor fuzzy, and > when I download the po file to translate the only fuzzy string marked in > Spanish there isn't any. > I guess it's a DL problem, if not I guess we should report it to > bugzilla. > > 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
Hi Olav, Today at 10:03, Olav Vitters wrote: > On Tue, Feb 05, 2008 at 08:54:52AM +0100, Danilo Šegan wrote: >> Yesterday at 20:22, Djihed Afifi wrote: >> >> > +1 from me for Khaled Hosny to get launchpad team coordinatorship. He >> > sent an email earlier. >> >> I've emailed current coordinator so I am waiting for response. >> >> >> Solving social problems is really up to social elements: people. >> > >> > I hope that you don't mean that this is a social problem. >> >> "Social" as in involving people and communication, versus "technical" >> problem (since it's completely possible to restrict access to any of >> the languages in Ubuntu to whoever you wish). There is no way we >> could have fixed the problem without people approaching us and telling >> us something is wrong. > > There have been *loads* of complaints on planet gnome about this. I know > various questions have been asked directly as well. However, just > because someone needs to communicate the problem doesn't make it social. Ok, I'll keep this simple. Launchpad already provides locking of entire language translation for eg. Ubuntu. So, there are no technical obstacles to doing that. It's Ubuntu's social arrangements you need to get involved into if you want Ubuntu's community to decide to lock translations for all languages. All my answers have been strictly from Launchpad's perspective, understanding that it'd be hard to convince Ubuntu community to lock all their translations. Maybe I've should not have used the word 'social'. I tried to contrast it with 'technical' above, hoping that would clarify it. Btw, Planet GNOME is not an efficient communication/collaboration mechanism. > If some language doesn't want Ubuntu to change their strings (especially > as they have real evidence that the quality decreases), then this advice > should be followed. Now, we've seen requests coming from GNOME and KDE asking for this. They are not representatives of a language, but (usually) largest translator communities for a language. However, entire Ubuntu contains much more than GNOME and KDE (GNOME and KDE being roughly 30% of all necessary translation work). At the moment, we don't provide categorization such as GNOME/KDE translations in Launchpad, so we can't lock their translations specifically. We do plan to provide it, but it involves work. So, it's possible to lock entire language, but there are no representatives of "entire language". If all major translators for a language come to an agreement, they can ask Ubuntu translation team for that language to lock the translations. Whether they'll do that or not is not up to technology (i.e. Launchpad) to decide. > If I read > https://bugs.edge.launchpad.net/rosetta/+bug/188907/comments/8, then it > is a problem within Ubuntu that the quality is subpar. Currently the > efforts are focussed on improving that quality instead of following the > wish of the GNOME translator teams. It is. I am not directly involved in Ubuntu translation, I am only a Launchpad developer. Ubuntu has a huge community and they have a community decision process which I am not too familiar with. What I can talk about is how we plan to approach the practical problems Ubuntu's mass popularity caused (possibly together with early Launchpad), and come up with practical solutions. A practical solution is not removing Launchpad from the picture, because as a tool, it provides what it is designed to provide. > e.g. with remarks such as > | 'However, that might also remove bug fixes' > > I further don't understand the response to > | - Upstream teams get bug reports about strings that are correct > | upstream but have been changed in launchpad > > You are suggesting to push launchpad bugs to GNOME Bugzilla and that > GNOME teams should check things in Ubuntu. While the issue is that GNOME > Bugzilla gets complaints because Ubuntu changed the translation. > Meaning: quality decreased and GNOME people get bugged about things they > aren't responsible for. As Johannes correctly read my response (in the bug report), I misunderstood the note. I thought it was about "you" wanting to get bug reports automatically when someone notices a problem in GNOME translation using Launchpad. So, I never suggested what you've seemed to have understood. However, Ubuntu, afaik, strongly encourages people to submit bugs to Launchpad, and bug triagers forward them upstream only if they are really upstream. Still, Ubuntu has a huge bunch of users who read no documentation, so GNOME ends up with spurious bug reports. I note again that I am not directly involved in Ubuntu, so I can't tell you how to fix this problem. This reminds me of the times bug-buddy got xml-rpc submission support, when it was included in Ubuntu, leading to hundreds of incomplete bug reports. > | Since we can't accept the simple solution of disallowing Ubuntu > | translations through Launchpad > > This pushes the problem towards GNOME translator teams. Now
Re: Import from Launchpad
On Tue, Feb 05, 2008 at 02:50:17PM +0100, Danilo Šegan wrote: > >> > I hope that you don't mean that this is a social problem. > >> > >> "Social" as in involving people and communication, versus "technical" > >> problem (since it's completely possible to restrict access to any of > >> the languages in Ubuntu to whoever you wish). There is no way we > >> could have fixed the problem without people approaching us and telling > >> us something is wrong. > > > > There have been *loads* of complaints on planet gnome about this. I know > > various questions have been asked directly as well. However, just > > because someone needs to communicate the problem doesn't make it social. > > Ok, I'll keep this simple. Launchpad already provides locking of > entire language translation for eg. Ubuntu. So, there are no > technical obstacles to doing that. Not my intention. > It's Ubuntu's social arrangements you need to get involved into if you > want Ubuntu's community to decide to lock translations for all > languages. All my answers have been strictly from Launchpad's > perspective, understanding that it'd be hard to convince Ubuntu > community to lock all their translations. Ok, just for the GNOME parts of a language. > Maybe I've should not have used the word 'social'. I tried to > contrast it with 'technical' above, hoping that would clarify it. > > Btw, Planet GNOME is not an efficient communication/collaboration > mechanism. I know. However, it was raised directly various times. Perhaps not to the right person/team. However, I do think the issue was known. > > If some language doesn't want Ubuntu to change their strings (especially > > as they have real evidence that the quality decreases), then this advice > > should be followed. > > Now, we've seen requests coming from GNOME and KDE asking for this. > They are not representatives of a language, but (usually) largest > translator communities for a language. However, entire Ubuntu > contains much more than GNOME and KDE (GNOME and KDE being roughly 30% > of all necessary translation work). At the moment, we don't > provide categorization such as GNOME/KDE translations in Launchpad, so > we can't lock their translations specifically. We do plan to provide > it, but it involves work. I mean: lock a language for GNOME. E.g. lock 'dutch' for 'GNOME' only. Not the whole of GNOME. Not the whole Dutch translations, just the combination. > So, it's possible to lock entire language, but there are no > representatives of "entire language". If all major translators for a > language come to an agreement, they can ask Ubuntu translation team > for that language to lock the translations. Whether they'll do that > or not is not up to technology (i.e. Launchpad) to decide. Ok, so we need a fix for that. > > If I read > > https://bugs.edge.launchpad.net/rosetta/+bug/188907/comments/8, then it > > is a problem within Ubuntu that the quality is subpar. Currently the > > efforts are focussed on improving that quality instead of following the > > wish of the GNOME translator teams. > > It is. I am not directly involved in Ubuntu translation, I am only > a Launchpad developer. Ubuntu has a huge community and they have > a community decision process which I am not too familiar with. > > What I can talk about is how we plan to approach the practical > problems Ubuntu's mass popularity caused (possibly together with early > Launchpad), and come up with practical solutions. A practical > solution is not removing Launchpad from the picture, because as a > tool, it provides what it is designed to provide. Launchpad is fine for other programs. However, it should provide the locking mechanism for a specific language for a project (as said above). I think you are saying that it is being worked on. If so, good. [..] > However, Ubuntu, afaik, strongly encourages people to submit bugs to > Launchpad, and bug triagers forward them upstream only if they are > really upstream. Still, Ubuntu has a huge bunch of users who read no > documentation, so GNOME ends up with spurious bug reports. I note > again that I am not directly involved in Ubuntu, so I can't tell you > how to fix this problem. I'm just trying to show what impact the current situation has on e.g. the Dutch translation team. It is not about where the bug reports are filed. It is the bad quality and the impression that a GNOME translation team caused it. > This reminds me of the times bug-buddy got xml-rpc submission support, > when it was included in Ubuntu, leading to hundreds of incomplete bug > reports. That was due to bug-buddy sucking. We did want those bugreports.. but we failed to have a process that added the debug symbols. It still sucks btw, but fortunately 'you' handle the mess now. > > | Since we can't accept the simple solution of disallowing Ubuntu > > | translations through Launchpad > > > > This pushes the problem towards GNOME translator teams. Now they > > have to coordinate with one
Re: Import from Launchpad
Today at 9:41, Olav Vitters wrote: > On Mon, Feb 04, 2008 at 03:14:30PM +0100, Danilo Šegan wrote: >> On January 25th, Kenneth Nielsen wrote: >> >> > Yeah it was done by filtering svn-commit-lists. And yeah I certainly >> > understand that it is a bad idea if many people do it, which is why I think >> > it is a good idea if it is done on a GNOME server and sent out centrally >> >> That shouldn't be too hard to do in damned-lies. I can help someone >> work on that :) > > KDE has something like commit-filter. Suggest someone sets that up on a > server somewhere. I don't see the requirement to have it on a GNOME > server. This pushes the burden on a non existent sysadmin team. My point was that we'd need not filter the commits list: damned lies is already getting notified about all the commits, and it even knows if a po file has been updated or not. It can make the best deduction whether there's been something wrong going on or not. Having it separately is completely doable as well, of course :) Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
> Ubuntu provides changes to the base GNOME. They need to be updated as > well. At the moment, Launchpad can't separate these two, and it will > take quite some technical effort (read: design, coding, testing, > fixing) to achieve that separation. Until that happens (let's call > that 'the correct solution'), you can do two things, depending on how > much you care about *GNOME translations in Ubuntu* (so, if you are not > an Ubuntu user, it's no bad thing that you don't care too much about > this): That would be fine if we didn't get Ubuntu translation bugs into bugzilla, which we actually get. That's one of the main problems. However I'm right now an Ubuntu user and I see some of my translations overwritten, the sad thing is that some of them have mistakes in Ubuntu and not in the Upstream and, again some, don't follow the whole style guide that the rest of the desktop follows. -- [EMAIL PROTECTED] http://aloriel.no-ip.org IM: [EMAIL PROTECTED] ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
Hi, > > If some language doesn't want Ubuntu to change their strings (especially > > as they have real evidence that the quality decreases), then this advice > > should be followed. > > Now, we've seen requests coming from GNOME and KDE asking for this. > They are not representatives of a language, but (usually) largest > translator communities for a language. However, entire Ubuntu > contains much more than GNOME and KDE (GNOME and KDE being roughly 30% > of all necessary translation work). At the moment, we don't > provide categorization such as GNOME/KDE translations in Launchpad, so > we can't lock their translations specifically. We do plan to provide > it, but it involves work. Even if you don't provide categorization for GNOME/KDE/WHATEVER, could you lock some modules, let's say the ones in GNOME svn? and would you be willing to do it? Cheers. -- [EMAIL PROTECTED] http://aloriel.no-ip.org IM: [EMAIL PROTECTED] ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
Hi Wouter, Today at 9:24, Wouter Bolsterlee wrote: > 2008-02-05 klockan 08:54 skrev Danilo Šegan: >> "Social" as in involving people and communication, versus "technical" >> problem (since it's completely possible to restrict access to any of >> the languages in Ubuntu to whoever you wish). There is no way we >> could have fixed the problem without people approaching us and telling >> us something is wrong. > > Upstream Gnome people don't want/need to get involved in Ubuntu-specific > launchpad translations stuff---they might as well use another distribution, > so the incentive for participating in an Ubuntu community process is pretty > much non-existent. That's ok. I am expecting people who do care about Ubuntu to get involved in the process, not those who don't. If they are involved with upstream, even better. > Therefore it is unreasonable to ask upstream people to get involved with > downstream distributions. Coordinating the upstream translations and keeping > those up-to-date and of a high quality is already time consuming enough for > most of us. Ubuntu provides changes to the base GNOME. They need to be updated as well. At the moment, Launchpad can't separate these two, and it will take quite some technical effort (read: design, coding, testing, fixing) to achieve that separation. Until that happens (let's call that 'the correct solution'), you can do two things, depending on how much you care about *GNOME translations in Ubuntu* (so, if you are not an Ubuntu user, it's no bad thing that you don't care too much about this): 1. Help Ubuntu translators get their act straight where they are really in error. 2. Ignore the issue. Plan is for Launchpad to help with option 1, but upstream teams can very well choose the other option. Again, we'll be working on 'the correct solution' as well, but not in the near term. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Evolution-webcal and libsoup
Well, but it's branched now. :) I just made the gnome-2-20 branch for evolution-webcal. -- dobey On Tue, 2008-02-05 at 15:56 +0100, Wouter Bolsterlee wrote: > 2008-02-05 klockan 15:38 skrev Dan Winship: > > I don't maintain evolution-webcal, I just happen to have made the last > > commit to it. Dobey is the maintainer. > > Well, but you are the one who broke the stable builds ;) > > mvrgr, Wouter > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Evolution-webcal and libsoup
thanks, DL updated in rev. 732 cheers, El dt 05 de 02 del 2008 a les 10:02 -0500, en/na Rodney Dawes va escriure: > Well, but it's branched now. :) > > I just made the gnome-2-20 branch for evolution-webcal. > > -- dobey > > > On Tue, 2008-02-05 at 15:56 +0100, Wouter Bolsterlee wrote: > > 2008-02-05 klockan 15:38 skrev Dan Winship: > > > I don't maintain evolution-webcal, I just happen to have made the last > > > commit to it. Dobey is the maintainer. > > > > Well, but you are the one who broke the stable builds ;) > > > > mvrgr, Wouter > > > > ___ > gnome-doc-list mailing list > [EMAIL PROTECTED] > http://mail.gnome.org/mailman/listinfo/gnome-doc-list -- 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
Hi Olav, Today at 15:44, Olav Vitters wrote: >> Maybe I've should not have used the word 'social'. I tried to >> contrast it with 'technical' above, hoping that would clarify it. >> >> Btw, Planet GNOME is not an efficient communication/collaboration >> mechanism. > > I know. However, it was raised directly various times. Perhaps not to > the right person/team. However, I do think the issue was known. The issue was known and being handled. Work-arounds have been put in place and most teams who have made use of them have found them sufficient so far (i.e. the problem is that because we didn't communicate how you should organise your team in the *past*, people let everybody in, thus causing the issue—now that most teams are moderated and consisted of reviewers only, and it's a one time job for people to revert translations to upstream provided one, it's mostly solved if anyone went through the burden of reverting translations). We have relied on translation teams to cooperate and coordinate with upstreams in this process, though. > E.g. lock 'dutch' for 'GNOME' only. Not the whole of GNOME. Not the > whole Dutch translations, just the combination. Understood. But I've explained this since the very start: doing that is a technically hard problem and we can't do that right now, nor in the near future. > Launchpad is fine for other programs. However, it should provide the > locking mechanism for a specific language for a project (as said above). > I think you are saying that it is being worked on. If so, good. This is the problem I have with the majority of comments. Everybody is talking about locking and nothing but the locking. There are different solutions to this problem. So, I will be assuming that this is what GNOME translators are asking for: "make sure that upstream translations are used whenever they are better than the ones submitted through Launchpad." That's something I'd gladly think about solving. And I am pretty sure that can be done without 'locking'. > [..] >> However, Ubuntu, afaik, strongly encourages people to submit bugs to >> Launchpad, and bug triagers forward them upstream only if they are >> really upstream. Still, Ubuntu has a huge bunch of users who read no >> documentation, so GNOME ends up with spurious bug reports. I note >> again that I am not directly involved in Ubuntu, so I can't tell you >> how to fix this problem. > > I'm just trying to show what impact the current situation has on e.g. > the Dutch translation team. It is not about where the bug reports are > filed. It is the bad quality and the impression that a GNOME translation > team caused it. It's a two edged sword. We can either try to give credit to upstream translators, which is what I think is more important, or we can try to shield them from everything. And as I mentioned, the same thing has been happening with any patched tarball. People have only mostly learned not to report kernel bugs to the main kernel development list. But it still happens: people using distro-patched kernels report bugs where they shouldn't. I don't know what I can do to convince you that Ubuntu has been pushing hard for people to report problems using Launchpad instead of external bug trackers. >> I understand that my response was long and that you failed to notice >> that I said we'll deal with the problem technically as well. However, >> it's a complicated one, and it will take time. > > Good! :-) > > How long do you expect this to be implemented and put into production? A really long term (we already have agenda for the next few months, and this one is a really complex bit touching many bits of infrastructure). I cannot give any time estimate because we haven't even discussed or planned this. Instead of waiting for proper locking, I'd rather use other solutions to the same problem. > Some of those patches I can understand. Mandriva only adds the bare > minimum of patches (probably focusses more on KDE). However, patches are > sometimes needed. And the same holds for translations — changes are sometimes needed. ;) >> problem of any other distribution. The specific problem of Ubuntu is >> that they are also patching translations. This reiterates the same >> problems in a new context. So, the problem is that some of those >> "patches" are bad. That's something we can work on. We can't work on >> the premise that all patches are bad. > > Except that for translations it seems like a free for all. Distributions > are free to change things. However, quality control shouldn't go out the > window. Plus the people who change stuff should be guided + know what > they are doing. A terrible translation is worse than no translation at > all. This is a problem with how Ubuntu translation was organised (or disorganised) in the early stages. It's still far from perfect, and far from the GNOME level, but we are working with Ubuntu community on improving that. > But if it has been proven that the Dutch GNOME team i
Re: Import from Launchpad
Today at 16:11, Jorge González wrote: > Even if you don't provide categorization for GNOME/KDE/WHATEVER, could > you lock some modules, let's say the ones > in GNOME svn? and would you be willing to do it? No. Launchpad has no knowledge of GNOME svn in relation with the packages in Ubuntu, *and* many of the core GNOME packages have been patched and contain new strings exclusive to Ubuntu. As an aside: Launchpad has ability to import projects from GNOME svn and can later do the locking per project. However, such projects have nothing to do with Ubuntu, where translation is based on Ubuntu packages (Ubuntu is considered a single 'project'). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
On Tue, Feb 05, 2008 at 04:54:56PM +0100, Danilo Šegan wrote: > Today at 9:41, Olav Vitters wrote: > > > On Mon, Feb 04, 2008 at 03:14:30PM +0100, Danilo Šegan wrote: > >> On January 25th, Kenneth Nielsen wrote: > >> > >> > Yeah it was done by filtering svn-commit-lists. And yeah I certainly > >> > understand that it is a bad idea if many people do it, which is why I > >> > think > >> > it is a good idea if it is done on a GNOME server and sent out centrally > >> > >> That shouldn't be too hard to do in damned-lies. I can help someone > >> work on that :) > > > > KDE has something like commit-filter. Suggest someone sets that up on a > > server somewhere. I don't see the requirement to have it on a GNOME > > server. This pushes the burden on a non existent sysadmin team. > > My point was that we'd need not filter the commits list: damned lies > is already getting notified about all the commits, and it even knows > if a po file has been updated or not. Oh right, I thought you meant the server. > It can make the best deduction whether there's been something wrong > going on or not. > > Having it separately is completely doable as well, of course :) Then it would be usable by the developers as well (some would like to see e.g. their commits in all modules, all commits in their project not by them, etc)... but damned-lies would work as well. -- Regards, Olav ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String changes in gnome-build
Hi! I fixed http://bugzilla.gnome.org/show_bug.cgi?id=503526 which introduces some new fuzzy strings in gnome-build. Regards, Johannes signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Malay Team
Can somebody change information at this page http://l10n.gnome.org/teams/ Email change to [EMAIL PROTECTED] and remove http://gabai.sf.net since it dont exist anymore. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
