Hello everyone. Thank you for all your interest in helping this book translation.

To prevent conflict, please write your name to each file you want to start working on. When you finish, check the corresponding checkbox.

• [x] 1-git-basics.asc (@anaufalm)
• [x] alises.asc (@anaufalm)
• [x] getting-a-repository.asc ()
• [ ] recording-changes.asc ()
• [ ] remotes.asc ()
• [ ] tagging.asc ()
• [ ] undoing.asc ()
• [ ] viewing-history.asc ()
• [ ] 1-git-branching.asc (@galuhsahid)
• [ ] basic-branching-and-merging.asc ()
• [ ] branch-management.asc ()
• [ ] nutshell.asc ()
• [ ] rebasing.asc ()
• [ ] remote-branches.asc ()
• [ ] workflow.asc ()
• [x] 1-git-server.asc (@iqbaladan)
• [ ] 1-distributed-git.asc (@mohdhaekal)
• [x] 1-github.asc (@azwarrangkuti )
• [x] 4-managing-organization.asc ()
• [ ] 1-git-tools.asc ()
• [ ] 1-customizing-git.asc (@Pastipas)
• [ ] 1-git-and-other-scms.asc ()
• [ ] 1-git-internals.asc ()
• [ ] 1-git-other-environments.asc ()
• [ ] 1-embedding-git.asc ()
• [ ] 1-git-commands.asc ()
• [ ] recording-changes.asc (@raja-rizki)

And let use this issue to discuss the translation. \o/

Note

To prevent confusion among our readers, please do not translate Git terminology. Let commit, fork, merge, etc. as it is.

Untranslatable Words

• fork
• commit
• pull
• push
• fetch
• rebase
• fork
• commit
• merge

I want to translate the third order ( 1-distributed-git.asc)

@mohdhaekal actually, you can edit comment content by yourself.

Thank you very much. I will do this all earnestly

@baguzzzaji You did the right thing. I just thought about preventing conflict and redundant works of translator.

Let me know if there is a mistake when we translate the sentences.

Hai @baguzzzaji Can i join in this translation project? How can I contribute it?

@azwarrangkuti sure you can! You can fork this repository, choose on which files you want to translate on the first comment above then do a PR.

@iqbaladan thanks, I will review your translation tonight.

Halo everyone, I want to take part in translating, which part can I work on?

Halo @baguzzzaji I want to joint the translation team? What should I do? this is my first attempt to do translation through GitHub, happy to get direction.

@Pastipas look at the first comment. There is a list of files to translate. You can choose any files you want to start working. Write your username to the right of the file name you choose (follow the example above).

@baguzzzaji thanks for the quick response, this is my first experience of doing translation with GitHub, so still try to get used to the work flow. Could you tell me how to add my account name to the list above? Thansk in advance for your generosity for input.

@Pastipas click on the pencil icon (Edit comment), then write your username @username inside the parenthesis.

@baguzzzaji thanks. I'll work on 1-github.asc.

@Pastipas sure. Can you write your name on the first comment above?

@Pastipas there's another one who already translates the file. Please choose another file.

@baguzzzaji I think would be better if we create a list of words that should not translated, like you stated above, for instance;

• pull
• push
• fetch
• rebase
• fork
• commit

etc...

Hi @baguzzzaji may i joint the translation team?

can i join to translate to indonesia, Thanksyou

@mirzazulfan @aldianrony1 please choose any files you want to translate. You can edit my comment above and write your username inside the parenthesis.

@baguzzzaji sorry for inconvenient as I left for some other work, just coming back. I noticed there are several other has joint the team. What is the situation now?Anyway, I am a little bit lack of technical knowledge working with computer, i have been tying to edit your comment in order to write my name in the file I am going to work. but couldn't managed it. I could find pencil icon at your comment, so i couldn't edit your comment. I only see the pencil icon at my comment string. Is that normal? is my computer having problem? how should i resolved this? thanks you in advance for the input and sorry again for inconvenient, I am so lame with technical thing. I will try to follow up the issue again tonight and work on the translation if there is still to translate. Thanks.

@Pastipas no worries. Which files are you planning to work? I will write it for you.

@baguzzzaji Thanks it's very kind of you. just coming back online, is some one working on customizing git.asc file? if not than I'll work on that.

I just wanted to chime in here, but it would also be interesting to translate git itself, if you feel technically up to the task. The repo is here and you just have to follow the guide.

@jnavila thanks for chime in, I'll look it up and I believe others will also be interested to look at it. Hope we up to technical need to work on that.

@jnavila That is awesome and should be interesting. Let see if we can contribute to it as well. @Pastipas I'll lend you my hand if you need to deal with technical-related stuff, don't hesitate.

@iqbaladan Thanks Mike, it's very kind of you, this is what we call team work. I just finish the translation for the Customizing Git.asc file for general part. I about to PR it, but i haven't got a reply for whether someone else work on it too. what should I do?

@Pastipas Just do PR, to see whether it can be merged or there is a conflict between base repo and your forking-repo. If everything is running well, there should be another open issue and new pull request. Finally, let @baguzzzaji review it before merging into the base repo.

@iqbaladan Thanks Broe, I push the PR as you suggested, it say welcome to pull request. should I hit new pull request to finish the PR process?

@Pastipas sorry for the late reply. If you have finished the translation, you can do a PR.

@Pastipas yes, simply hit that green button to see if there is a conflict or not.

Done and no conflict...I am proceeding to sub folder of the file