Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain why we're using English in GitHub Issues & PRs #108

Closed
Tracked by #99
zainfathoni opened this issue Jul 17, 2021 · 2 comments · Fixed by #201
Closed
Tracked by #99

Explain why we're using English in GitHub Issues & PRs #108

zainfathoni opened this issue Jul 17, 2021 · 2 comments · Fixed by #201
Labels
documentation Improvements or additions to documentation

Comments

@zainfathoni
Copy link
Member

zainfathoni commented Jul 17, 2021

The reasons we're using English in GitHub Issues & PRs:

  1. It's more natural for software engineers to communicate in English because it involves many technical terms in English. Trying to translate them into Bahasa Indonesia posing a risk of miscommunication, while keeping them in English requires us to do a lot of italic formatting, according to PUEBI.
  2. It accustoms the contributors, which are mostly Indonesian, to communicate in English. It is important to increase our English reading and writing skills because the vast majority of the global open-source communities are using Engish as the main language.
  3. It makes this project easier to be recognised globally. So if we need to get more support from the global communities, they could easily understand what we are doing and help us out with their access and competence. e.g., providing us free credits for their services, advocating us to global leaders, or contributing directly to our codebase.
@zainfathoni zainfathoni added the documentation Improvements or additions to documentation label Jul 17, 2021
@zainfathoni zainfathoni added this to To do in Kanban Board via automation Jul 17, 2021
@zainfathoni zainfathoni added this to Needs triage in Prioritization via automation Jul 17, 2021
@zainfathoni zainfathoni added this to the Further Optimizations milestone Jul 17, 2021
@zainfathoni zainfathoni moved this from Needs triage to Low priority in Prioritization Jul 17, 2021
@andriawan
Copy link
Collaborator

i'm not quite understand the reason behind this mas @zainfathoni. Could you enlighten me mas @zainfathoni ?

@zainfathoni
Copy link
Member Author

I have updated the description with my explanation, @andriawan. 😁

Kanban Board automation moved this from To do to Done Jul 20, 2021
Prioritization automation moved this from Low priority to Closed Jul 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Development

Successfully merging a pull request may close this issue.

2 participants