L10N migration to transifex.net
kwade at redhat.com
Fri Feb 25 00:56:07 UTC 2011
On Thu, Feb 24, 2011 at 05:17:00PM -0700, Stephen John Smoogen wrote:
> The issue was that transifex has been an ongoing problem for the
> following reasons:
<snip important list of reasons/details>
Thanks for providing those details. I meant, and wrote it poorly I'm
sure, that I presume that the situation was much as you described, but
in the end there were people who did not feel/get communicated to. At
that point, Infra and others were saying, "OK, sorry if you didn't
hear about this before, it's been a long-standing problem, and we need
to solve it now before the barn burns down."
So, sorry for characterizing the communication as poor. I think what
I'm seeing could benefit from some change management that all know
about. A lot of times we have to result to a change management list
that goes something like, "OK, ask
$this_list_of_individuals_I_can_think_of, then email
$this_list_of_mailing_lists_I_can_think_of, and write a blog post."
Anyway, I'm sure there is a not-too-much-bureacracy way to do this. I
started this ...
... I'm sure there are others who deal with that all the time around
here, maybe there are some existing processes we can adopt,
incorporate, hug, etc.
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/docs/attachments/20110224/db03c3c2/attachment.bin
More information about the docs