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.

Sign up for GitHub

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

Jump to bottom

Russian translation удачи #105

Closed
goldbergyoni opened this issue Dec 7, 2017 · 7 comments
Closed

Russian translation удачи #105

goldbergyoni opened this issue Dec 7, 2017 · 7 comments
Assignees
@oshliaer

Comments

@goldbergyoni
Copy link
Owner

goldbergyoni commented Dec 7, 2017 •
edited
Loading

https://github.com/i0natan/nodebestpractices/tree/russian-translation

@demid5111 - Russian translation can be officially kicked-off. You're the lead! I'll be at your disposal should you need anything. A branch was created (link below), you should have permissions to it, everyone else must PR before changing anything there.

I would ask/recommend only 2 important guidelines:

Keep the same content & formatting - the focus is on translation, should anyone want to modify the content or the graphics - let's PR first in English and them translate to Spanish
Duplicate pages - the content should be translated over a page duplication. Readme.MD became Readme.russian.MD, all other files should be duplicated similarly. So the number of English & Russian pages should be the same. You already have readme.russian.md & sections/breakintcomponents.russian.md - kindly create all other page duplication (feel free to ping should you need help). Will create a bold link from the English home page to the Russian home page (with bold credit of course...).

https://github.com/i0natan/nodebestpractices/tree/russian-translation
@goldbergyoni goldbergyoni changed the title Russian translation Russian translation удачи Dec 7, 2017
@goldbergyoni goldbergyoni mentioned this issue Dec 8, 2017
Closed
@goldbergyoni
Copy link
Owner Author

@demid5111 no rush, just checking whether everything is clear and if I assist in anyway

@demid5111
Copy link

@i0natan yep, it is all clear - it is WIP, hope to create first PR till EO ww3. Thank you so much for assistance!

@goldbergyoni
Copy link
Owner Author

Sounds great and looking forward

@stale
Copy link

stale bot commented Mar 25, 2019

Hello there! 👋
This issue has gone silent. Eerily silent. ⏳
We currently close issues after 100 days of inactivity. It has been 90 days since the last update here.
If needed, you can keep it open by replying here.
Thanks for being a part of the Node.js Best Practices community! 💚

@stale stale bot added the stale label Mar 25, 2019
@stale stale bot closed this as completed Apr 4, 2019
@oshliaer
Copy link
Collaborator

oshliaer commented Jul 3, 2019 •
edited
Loading

Russian translation resume

There are three PRs/threads for the start translate:

  1. The first initiative Russian translation #98 Russian translation удачи #105
  2. The second attempt is @GraxMonzo PR Translating to russian #388
  3. The third attempt is Russian translation #1 #433

As I can see now we cannot coordinate to form a group for active participation. It's sadly because I find the Practices very useful.

My suggestions

  1. Reopen Russian translation удачи #105 because this topic is already referenced by all translations.
  2. Close Translating to russian #388 with reject. I cant merge this softy.
  3. Review Russian translation #1 #433
  4. Direct all intro messages to What is the Russian translation status? #454

@oshliaer oshliaer mentioned this issue Jul 3, 2019
Merged
@goldbergyoni
Copy link
Owner Author

@oshliaer Sounds good

@oshliaer
Copy link
Collaborator

oshliaer commented Aug 8, 2019

Related #454

@oshliaer oshliaer mentioned this issue Aug 19, 2019
Merged
@oshliaer oshliaer self-assigned this Jan 25, 2020
@oshliaer oshliaer mentioned this issue Jan 25, 2020
Closed
MatanYadaev pushed a commit to MatanYadaev/nodebestpractices that referenced this issue Aug 16, 2023
@goldbergyoni
Merge pull request goldbergyoni#105 from j9t/patch-1
7716ddf 
style: fix typos and heading levels, improve punctuation, make formatting consistent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oshliaer oshliaer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@demid5111 @oshliaer @goldbergyoni