[libsoup] Created branch gnome-2-30

2010-04-11 Thread Dan Winship
The branch 'gnome-2-30' was created pointing to:

 0df6a4c... Fix for proxies that close the connection when 407'ing a CO

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


DL commit (was: GNOME in Occitan)

2010-04-11 Thread Petr Kovar
Hi!

Claude Paroz , Sat, 10 Apr 2010 21:51:21 +0200:

> Damned-Lies is still not authorized to commit the file itself. So you
> still have to commit it yourself, then use the "Informer du commit" to
> archive the actions.

When we're at it, I wonder what exactly is the blocker for the DL
commit/push capability? As far as I understand it, everything needed has
been done on the side of DL developers, right?

Is there anything we, ordinary translators or coordinators, can do about
that, to (help to) push things forward?

I believe that for many teams & translators (incl. those who have
team commit access, but are otherwise limited in manpower and/or free time),
the lack of automated commit/push capability means a major obstacle in their
l10n workflow seamlessness at this time.

Thanks,
Petr Kovar
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: DL commit (was: GNOME in Occitan)

2010-04-11 Thread Claude Paroz
Le dimanche 11 avril 2010 à 18:11 +0200, Petr Kovar a écrit :
> Hi!
> 
> Claude Paroz , Sat, 10 Apr 2010 21:51:21 +0200:
> 
> > Damned-Lies is still not authorized to commit the file itself. So you
> > still have to commit it yourself, then use the "Informer du commit" to
> > archive the actions.
> 
> When we're at it, I wonder what exactly is the blocker for the DL
> commit/push capability? As far as I understand it, everything needed has
> been done on the side of DL developers, right?

Almost right. Some polishing may still be required, but it is mainly
there.
We are still waiting for some sysadmin to write a Git hook to make the
process more secure.
https://bugzilla.gnome.org/show_bug.cgi?id=599066
I've recently heard that somebody was on the job, so there is some hope!

> Is there anything we, ordinary translators or coordinators, can do about
> that, to (help to) push things forward?

Blog about it, bribe a sysadmin or a Git guru, buy some ice creams :-)

> I believe that for many teams & translators (incl. those who have
> team commit access, but are otherwise limited in manpower and/or free time),
> the lack of automated commit/push capability means a major obstacle in their
> l10n workflow seamlessness at this time.

We're probably all convinced of that here. Hopefully this issue will be
resolved soon.

Claude

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Translation update for GCompris 9.3

2010-04-11 Thread Bruno Coudoin
Hi translation teams,

GCompris is moving forward. There is a new activity and a few string
changes. We need your help to update your translations. 

Please take care that the translation is to be done under gnome's git
branch named 'gcomprixogoo'. 

We plan the new release for the April, 25th, two weeks from now.

Let me know if you need more time for the translation.

-- 
Bruno Coudoin
http://gcompris.net  Free educational software for kids
http://toulibre.org  Logiciel Libre à Toulouse
http://april.org Promouvoir et défendre le Logiciel Libre



___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n