-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jun 30, 2008, at 10:52 AM, Jordi Mallach wrote:
On Mon, Jun 30, 2008 at 08:16:56AM -0400, Barry Warsaw wrote:
Thanks Cristobal and Clytie for helping set this up. I encourage all
translators to give this a chance so we can decide whether to move to
it officially, try something else, or keep the status quo.
If it becomes "official", will we (language teams) have the option to
opt-out and work like we recently did for the 2.0.11 release, using a
Launchpad team and a bzr branch that can be pulled by you or Mark?
That means that our language would be locked or something, to avoid
work
duplication.
If we do adopt Pootle, I'd like to discourage teams from using
alternatives to it. If there are specific problems with Pootle in
general, or our implementation in particular, it would be best if we
could work with Cristobal and the Pootle devs to improve things. This
helps more free software benefit from our experience.
If it's really a problem, I suppose we could handle your team
specially in the short term, using a bzr branch as you describe.
If your team has a workflow problem with Pootle, then I suspect other
teams will have the same problems. If we can't make Pootle attractive
to all our teams then maybe Pootle isn't the answer for us.
Can you provide details on why you don't want to use it?
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkhsX60ACgkQ2YZpQepbvXFcWQCbBgWnhmbf1d8PpzSelTbugys/
E0AAoK474W3yJfYS0OfcHAml6mu+vIwJ
=kvAi
-----END PGP SIGNATURE-----
_______________________________________________
Mailman-i18n mailing list
Posts: [email protected]
Unsubscribe:
http://mail.python.org/mailman/options/mailman-i18n/archive%40mail-archive.com
