[Fwd: Re: Help with the translatable Code of Conduct]

[David Planella]

(Forwarding Nico's e-mail and my response to the lists after getting his
permission)

-------- Missatge reenviat --------
De: David Planella
Per a: Nico Veenkamp
Assumpte: Re: Help with the translatable Code of Conduct
Data: Tue, 26 Oct 2010 09:49:57 -0400

El dt 26 de 10 de 2010 a les 14:24 +0200, en/na Nico Veenkamp va
escriure:
> David,
> 
> 2010/10/26 David Planella <david.planella at ubuntu.com>:
> > Hi all,
> >
> > I just wanted to remind you about the "Translatable Ubuntu Code of
> > Conduct and Leadership Code of Conduct" session on Friday at UDS. Most
> > especially, I wanted to reach out to the docs team to participate either
> > on the session itself or following up on this thread.
> 
> I subscribed to the blueprint and left my comments on your weblog. I
> also put them in this message.
> 
> David, saw your question on the list and subscribed to the Blueprint.
> I am not at UDS but look forward to see the result of the discussion
> regarding this blueprint.
> 

Hi Nico,

Thanks a lot for the feedback. I see you've replied to me only, which is
absolutely fine, but I'm just mentioning it in case you wanted to reply
to the lists as well, as I think your input would be very useful for the
discussion.

> Some remarks:
> as the CoC and LCoC are the very basis for our community I would state
> that whatever happens with any translations, if there are discussions,
> difference in opinions or maybe even people sueing each other, in the
> end the english version in plain text is the original one to refer to.
> 

That's a good point, and it brings up the question on what should be the
document to actually sign: the English one or the translated one? And
how can we check the quality of the translations?

> This means that whatever method you choose to get these files into
> gettext needs to be done again after each change in the original
> files. But once the process is in place, this should not be much of a
> problem.

Exactly. Absolutely, whenever there'd be a change in the original
document, the translatable templates would be updated.

>  Personally I would opt for Option 1 as this is known
> technology
> 
> Shipping it in docs could mean that the doc-team is responsible for
> its upkeep. I am not sure if that is the right place. I would suggest
> to make it it’s own package with the Community Manager as the package
> owner.

I was suggesting the docs team, as they've already got the skills and
the resources to support and publish localized documents. Having it in
ubuntu-docs would also give more visibility to the Code of Conduct.

The role of Jono as the Ubuntu Community Manager does not generally
involve Engineering work, so I don't think he should be maintaining the
document.

>  It should also be available on the Ubuntu website 

It's a good point, but right now the Ubuntu website lacks
internationalization infrastructure. I would really love to see the
website available in many languages, but right now there are
unfortunately no resources to work on this, and this would be a
requirement to have a localized CoC on the website.

> and the
> translated versions on their respective ubuntu-[language] websites.

Absolutely. Once the document is translated, each team can put it on
their local sites.

>  It
> should also be available on launchpad as you need to sign it to become
> a ubuntu member.
> 

Yes, I think you make a good point again, but I think we need to resolve
the question on which version (English or localized) would be the one to
sign.

> Hope this helps in the discussion.

It really does, many thanks for your feedback!

Regards,
David.

-- 
David Planella
Ubuntu Translations Coordinator
www.ubuntu.com / www.davidplanella.wordpress.com
www.identi.ca/dplanella / www.twitter.com/dplanella

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-translators/attachments/20101026/2b53b64c/attachment.sig>