pgadmin-org / pgadmin-org/pgadmin4
Proposal: Starting official Russian documentation (translation) for pgAdmin 4
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
Hello pgAdmin team and community!
My name is Dmitriy (GitHub: @Vermillion-Develop). I am a PostgreSQL and pgAdmin 4 user, and I would like to contribute to the project by creating and maintaining the official Russian documentation.
Currently, there is no official Russian translation for the pgAdmin 4 user manual, and I believe this would be highly beneficial for the Russian-speaking PostgreSQL community.
I have already set up a local Sphinx environment, cloned the repository, and started working on the translation based on the latest v9.18 documentation files. As a pilot, I have translated the README and the ai_tools.rst section. You can check my current progress in my fork here: https://github.com/Vermillion-Develop/pgadmin4_ru
Before I move further with translating other sections (like backup, desktop deployment, etc.), I would like to ask for your guidance:
- Is the pgAdmin team open to accepting a new language localization for the documentation?
- What is the preferred workflow for documentation translations in this repository? Should I submit direct
.rstfiles in a newru_RUdirectory via Pull Request, or do you use a specific internationalization system (like.po/.potfiles via Sphinx-intl)?
I would love to adapt my work to your official standards and contribute regularly. Thank you for your time and for this amazing tool!
Best regards,
Dmitriy
Contributor 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.
Research direction
Start by reviewing the translated README and ai_tools.rst files in the reporter’s v9.18-based fork, along with the local Sphinx setup they mention. The issue asks maintainers to decide whether Russian documentation is accepted and whether contributions should use a new ru_RU directory with .rst files or a .po/.pot workflow; done means an agreed contribution path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- documentation, localization
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100