Starting Arabic Translation (progit2-ar)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- git
Research direction
Start by reviewing the existing progit2-ar/progit2 repository and the Pro Git contribution guidelines. The first decision is whether to revive that repository or create progit/progit2-ar-new; wait for maintainer guidance before beginning the Arabic translation. Done means establishing the agreed repository setup and producing a complete, high-quality Arabic translation.
Written by the indexing model from the issue text.
Description
Arabic is spoken by over 420 million people across more than 20 countries, making it one of the most widely spoken languages in the world. Despite this, there is currently no up-to-date, complete Arabic translation of the Pro Git book, which leaves a large community of Arabic-speaking developers without easy access to this essential resource.
I am aware that there is an existing repository progit2-ar/progit2 that was started for this purpose, but it appears to have been abandoned since 2017, with no recent activity or updates.
Before proceeding, I would like to know your preference regarding the repository setup:
Should I take over and revive the existing progit2-ar/progit2 repository (if that is possible and permitted), or
Would you prefer that I create a new repository progit/progit2-ar-new to start fresh with the translation?
I am committed to producing a complete, high-quality Arabic translation and will follow the contribution guidelines closely. Please let me know your preferred approach so I can begin accordingly.
- Dominant language
- CSS
- Stars
- 6.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from progit/progit2
-
Difficulty 1/5 Under an hour Newbie friendliness 87/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
AI-Agent/Queued Type/Bug
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
approved documentation
Difficulty 1/5 Under an hour Newbie friendliness 89/100
vitest-dev/vitest#12015 · 4 comments ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·