Reviving the abandoned Greek repo
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
- javascript
- Domain
- documentation, localization
Research direction
Start by inspecting the javascript-tutorial/el.javascript.info repository, especially 1-js/01-getting-started/2-manual-specifications/article.md, to confirm the committed merge conflicts and assess the translation state. Review the scope of the Greek localization cleanup and the project’s process for contributor or maintainer access. Done would mean the branch is usable, affected translations are manually revised, and maintainers have reviewed the proposed ownership.
Written by the indexing model from the issue text.
Description
Hi everyone,
I was looking to contribute to the Greek translation of the JavaScript Tutorial (el.javascript.info), but I noticed that the repository has been inactive for several years.
More importantly, the current master branch appears to be broken, as there are unresolved git merge conflicts (like <<<<<<< HEAD) committed directly into live article files (e.g., in 1-js/01-getting-started/2-manual-specifications/article.md). Furthermore, many existing core translations are heavily machine-translated and need manual rewriting to meet proper technical engineering standards.
I am a full-stack developer and I would love to step up, take ownership of the Greek locale, clean up the broken master branch, and actively maintain/approve future PRs for the Greek community.
Could a core maintainer please review the state of javascript-tutorial/el.javascript.info and grant me the necessary contributor/maintainer access to revive this localization project?
Thank you for your time and for this amazing resource!
- Dominant language
- HTML
- Stars
- 25.5k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 javascript-tutorial/en.javascript.info
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Keyboard events: keydown filtering example can't block IME-composed input (Korean/Japanese/Chinese) Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
javascript-tutorial/en.javascript.info#3978 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in javascript-tutorial/en.javascript.info
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100