Comments (56)
I'd be happy to contribute if this issue is still open! 🇫🇷
from nodebestpractices.
@adaube If you want we can split the work. Each of us having his pages to translate.
I started with the main page but I didn't realise it was massive. Maybe start with the smaller sections ?
from nodebestpractices.
Yes ! I'll try and come up with a table with pages, the translator, and the status.
from nodebestpractices.
I can give my help to review or contribute. 👍
from nodebestpractices.
@forresst Thanks for keeping this going. Apologies for not getting more involved in this yet, I have recently started a new role and have a little daughter that keeps me busy 🤦♂
I hope to get started asap!
from nodebestpractices.
Hi
I'd be happy to contribute :-) Just tell me how I can help 👷
@corentindesfarges First of all, thank you for your help. The simplest:
- Choose the file you want to translate from those that are not assigned in thise issue and leave me a comment in this issue so that I can assign you the translation of a file.
- Then fork my own fork and work on the
french-translation
branch - When the work is done, propose a PR on my fork
- I will review your work
If you only want to review my work, you can post comments directly on my commits in Github
from nodebestpractices.
@gaspaonrocks sounds amazing, would you like to lead this work and find together others that will help you?
p.s. your name will be added to the core contributors + will be on top of the French page
from nodebestpractices.
@gaspaonrocks - French translation can be officially kicked-off. You're the lead! I'll be at your disposal should you need anything. Please create a branch for this work and PR to master once it's 100% done.
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 French
Duplicate pages - the content should be translated over a page duplication. Readme.MD became Readme.french.MD, all other files should be duplicated similarly. So the number of English & French pages should be the same. Will create a bold link from the English home page to the French home page (with bold credit of course...).
from nodebestpractices.
@gaspaonrocks that sounds great. Your approach of breaking the work down into smaller chunks is exactly how I like to roll! I'll fork and dive deeper this weekend, or sooner if I can carve out time.
from nodebestpractices.
Hey !
If you guys need some help with French translation, let me know
from nodebestpractices.
@Annouar
Hey ! Sure, you can translate any parts. Any help is appreciated.
I have almost done the /sections/projectstructure
folder, but i see that thincomponents.md and breakintocomponents.md is the exact same file. Any idea why @i0natan ?
I fixed some minor typos in the english files as well.
I'll PR once I'm done with this folder.
from nodebestpractices.
Hey ! I'll be happy to contribute for the french translation :) What is not currently being translated ?
from nodebestpractices.
Hi! I have seen that the French translation isn't done yet. I could work on it if you need some help.
from nodebestpractices.
@NTurchi Bienvenue! 👍
@gaspaonrocks @adaube @Annouar I'd be glad to hear your thoughts (see @NTurchi message) and progress so far?
from nodebestpractices.
Hello everyone,
Sorry for the lack of news about the french translation, but I have been swamped with work, which is a good thing. For everyone working on the French translation, you can do small files, and submit a PR for a review.
You announce what files you are working on before submitting the PR, that way duplicate work will be avoided.
I'll try and be more available.
Again, sorry and thanks to everyone involved.
from nodebestpractices.
How's that going?
I'm fluent in French so thought I could help.
from nodebestpractices.
@gaspaonrocks Any progress on that?
from nodebestpractices.
Hi
I'd be happy to contribute :-) Just tell me how I can help 👷
from nodebestpractices.
Just to give you an update, 41 out of 87 files are translated and reviewed. Currently 10 are in progress or awaiting review.
I regularly update the translation according to the modifications applied to the original English version.
Anyone interested in translation and/or review is welcome.
from nodebestpractices.
Thank you @forresst
I like the 2nd option, focusing on the home page only for now. Let French readers read the main part at least, then gradually later process individual files. Maybe also @tkhadir and @corentindesfarges wish to be part of the home page writing.
from nodebestpractices.
Hello @forresst , @goldbergyoni
I will read this with pleasure this night :),
from nodebestpractices.
@i0natan I'll start a readme.french.md then and wait for your instruction for the pull request.
from nodebestpractices.
I would love to be able to help on this PR. I see that @gaspaonrocks has the lead.
How can I help?
from nodebestpractices.
sounds great. You may share in some French groups (FB, etc) to see whether other would like to join
from nodebestpractices.
@gaspaonrocks @adaube @Annouar sounds great, really anxious to see it live
from nodebestpractices.
@Yaty Bienvenue.
Tagging @gaspaonrocks @adaube @Annouar
from nodebestpractices.
/remind me in 5 days
from nodebestpractices.
@i0natan set a reminder for Dec 20th 2018
from nodebestpractices.
@gaspaonrocks If nobody work on it, I can translate "2.1 Use Async-Await or promises for async error handling" and also the attached article below "Read More: avoiding callbacks"
from nodebestpractices.
👋 @i0natan,
from nodebestpractices.
Sounds great, as suggested let's start with small steps, do we need someone to correlate the work like maintain a list/table of what is translated by whom (avoiding duplicates)?
from nodebestpractices.
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! 💚
from nodebestpractices.
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! 💚
from nodebestpractices.
@Joaquinox Welcome aboard!
It's super relevant. Maybe @gaspaonrocks @NTurchi can share their progress so you join or at least not start from a clean slate?
from nodebestpractices.
Thanks @i0natan! I'll wait for instructions from @gaspaonrocks or @NTurchi before moving forward then 👍
from nodebestpractices.
@gaspaonrocks or @NTurchi Maybe can you kindly just share with @Joaquinox the current status so he can progress your great work from the right point?
from nodebestpractices.
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! 💚
from nodebestpractices.
@gaspaonrocks @NTurchi One more try, maybe you can just share a status update? 🙏
from nodebestpractices.
@goldbergyoni Sorry for this late reply. A PR has been in the French repo version at the beginning of this year but I didn't get any follow-up. Thus, I have not started to go deeper into the translation. @gaspaonrocks Any update?
from nodebestpractices.
Thank you @NTurchi :)
@Joaquinox, In that case, I suggest you just fork the French repo of @gaspaonrocks?
from nodebestpractices.
Thanks for the green light @goldbergyoni, I'll get to work this weekend 👍
from nodebestpractices.
Thanks for the green light @goldbergyoni, I'll get to work this weekend 👍
🎈 🎉
Let me whether I can help in any form
from nodebestpractices.
Hey, if you need help I'd be happy to contribute! 😊
from nodebestpractices.
@goldbergyoni Despite several attempts, the translation is no longer progressing.
So I started translating into French (taking up and adapting what had already been done). For this, I made a fork of the repositorygoldbergyoni/nodebestpractices
and I created a branchfrench-translation
.
My first commit just copied all the markdown files from the original text to copy them into xxxx.french.md
files.
The following commits are the first translations.
I made one commit per file. For example, one for the file writing-guidelines.md
. Thanks to my first commit explained above, you can see both the original version and the replacements made by the French translation. Here is the commit of the writing-guidelines.md
file.
My goal is to finish on 31 January 2020.
Of course all help is welcome: translations, proofreading, discussion
I have created an issue to track the progress of translations.
As I write his lines, 15% of the translation is done.
If people volunteer to translate into French, leave me a comment in this issue so that I can assign you the translation of a file. This prevents several people from working on the same file.
from nodebestpractices.
have a little daughter that keeps me busy 🤦♂
❤️
from nodebestpractices.
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! 💚
from nodebestpractices.
This subject is still in progress, I'm behind schedule but the translation is progressing well. Moreover I received help for translation and proofreading. And that's great.
from nodebestpractices.
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! 💚
from nodebestpractices.
Hey @tkhadir ! Welcome 🎊, Thanks for approaching in #831 !
Let's continue the discussion here.
Dear @gaspaonrocks @samueldjones24 @corentindesfarges @forresst, Would you kindly help @tkhadir get on board and understand how to continue your wonderful work? Maybe can share with him some high-level status?
from nodebestpractices.
hello @goldbergyoni thanks for all :)
from nodebestpractices.
Sorry I've been away for more than 9 months, but I'm back to move on. I advise to follow the instructions of this comment
from nodebestpractices.
@forresst Awesome progress. Is the homepage translated? If yes, shall we publish this already and then wait for the internal files?
cc @kevynb
from nodebestpractices.
The main page (README) is translated progressively. Currently, for the main page, parts 1, 2, 3 and 4 are translated and reviewed, part 5 is awaiting proofreading (Going To Production Practices). Part 6 is being translated (Security).
We have a main branch (french-translation) of all translations done and reviewed. An issue to follow the progress of the translations.
Two possibilities:
- I can do a PR for the french-translation branch, this allows to have 47 out of 87 translated files and parts 1,2, 3 and 4 of the README.
- I can focus on the translation of the main page, and provide the complete main page translation with all the other files already translated and reviewed.
What's your opinion?
from nodebestpractices.
@goldbergyoni Ok, I focus on the translation of the main page
@tkhadir You can already review part 5 in priority
from nodebestpractices.
@forresst @tkhadir Awesome. Let me know how I can help.
from nodebestpractices.
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! 💚
from nodebestpractices.
Related Issues (20)
- Easy to translate advice HOT 1
- Translations status HOT 1
- Bonnes pratiques nodejs
- Arabic Translation
- Node practice 1
- Should include Corepack in our recommendation? HOT 5
- Bootstraping nodejs container may be misleading
- Node
- Node js fullstack HOT 4
- Wrong example HOT 2
- Broken link to env-var
- Nextjs as main framework? HOT 2
- Another comment regarding "1.1 Structure your solutions by business components" HOT 1
- Italian Translation
- The backend-testing-checklist.png file is missing. HOT 3
- Hinglish Translation HOT 1
- Кнас
- Dead link for safe-regex
- Mi006
- Is using cache for npm install in docker safe?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nodebestpractices.