Re: Contact with Latinamerica

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: "Christopher Díaz" <christopher.diaz.riv@xxxxxxxxx>

Hi Christopher,
I've included the Git list to keep the discussion open to all the community. (we usually use reply all)

El dom, 30-07-2017 a las 19:01 +0100, Philip Oakley escribió:

Hi Philip,

Thank you very much for such a fast reply.


I can see two simple steps toward your goal that may help.

The first is to ensure that the open source tools do have
localisation
(l10n) of their command line messages, for which I'm sure Git's l10n
team
would be happy to have your communities support. -
https://github.com/git-l10n and
https://public-inbox.org/git/CANYiYbEJ3Gw=JvbhLBeFWBD7xLXxd=_fFdH3UX7
6H97ZU_3zKA@xxxxxxxxxxxxxx/#r


That would be amazing since the second step in order to help open
source communities is knowing how to use git (the first one is teaching
them a programming language in order to be able to understand the code,
we are taking care of that too). This is something that we will need to
teach practicaly all of the members to do if they don't already know.
I'll be in contact with the team.


You may also want to look at the https://git-scm.com/book/en/v2 free book which can be translated by volunteers, and is possibly one of the first ports of call for most users (top or near-top of search engine hits)

The other idea is to consider how Git's version message, or
something
similar, should report the users current i18n settings, and any links
to the
right (e.g. local) support groups. At present, I don't see any
obvious
command to help users (and those on the help forums and lists) know
what
i18n nationality / language names to use for discussions. Sometimes
it is
worth ensuring these baby steps are in place.


Another very simple step is to read and comment on the commit messages sent to the list, particulalrly for ease of readability and ease of translation/comprehension.

It is very easy to write sentences that are too long. And with too many conjunctions.

We do not notice when we do it, having only been taught to write long flowery sentences for essays and novels...

Proof-reading the commit messages will also allow the reader to do directed research on just the particular item (both the use of language and the code style)


Yes, thanks for taking this in consideration, the reallity here in
Peru, and I could say maybe in a lot of parts in Latinamerica is that
they don't produce technology since it is mucho more easy just to buy
something and the language doesn't help to make the learning curve
easier.

I'll contact the translation team and I hope you won't mind if we could
say here that we contribute to the git project. It would be a lot
easier for me in order to go to invite people to the community in
educational institutions if I could say that the community helps very
big open source projects like git. And if there are some legal
procedures that I need to accomplish in order to be able to say it
publicly, it would be very kind of you if you point me into the right
direction.

Welcome to the community! All it takes is one email (a journey of a thousand miles starts with the first step) [1]


Thanks for all the info
Christopher Díaz Riveros

[1] It's easy to feel overwhelmed by other who post.. can find the article but...



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux