The following is a report of my last Node.js translation, specifically the 9th version of changelog folder. I want to share my experience translating this kind of file. First, I will show some benefits of translating these files, so you can understand their importance.

When you are a user of a determined open source software, you will start your research about the functionalities that it offers. Probably you will make tests, some research work on the internet or even ask another user of the same software; in this process, you might find some issues, bugs or unnecessary content that harm the performance of the entire software because any program is perfect. As a platform user, you will purpose solutions to those errors you found, and you must warn the developers so they can make the necessary changes. You must know that those changes will be registered in a change log file that contains all the solutions purposed by the users.

Also, this file is public and anyone can see it to consult the changes that have been made through the releases. A change log file is mostly informative because those who consult it, will learn more about the open source software and about solutions of issues that could appear in another software.

Translating a change log file will allow people of the entire world to be informed about performance changes. Also, some of these can help improve other open source software, so it is a both sides winning.

In resume, Node.js is a way to unify a lot of languages in one single code, so there are no support issues between them. A simple solution for a big problem.

I decided to translate this project because I'm an engineering student and programming covers a huge area of knowledge on my career. Also, I like sharing information and a way to do it is translating the content of a big project like this so people around the world can access to it and share it too.

In this part of the 9th version of Node.js change log, you can find some new improvements in this project. For example, the reader can observe that there were a lot of useless an unused code; also, some collaborators found that some functions and modules were damaged or corrupted, so Node.js was in danger. These are examples that confirm the importance of updates.

The following image show some of the commits made in this part of the change log file.

The original language of this change log is English and it was translated into Spanish, which is my native language. I have experience translating in projects like Loopring wallet and Yapbam. These projects make me grow and learn a lot about open source projects.

Some examples of my translation:

Along the change log I have seen a word that calls my attention and it is "eslint". I got curious and started a research. I found that "lint" is a programming tool, originally used in C, to detect suspicious, confusing or incompatible code. It looks like a common error checker but it is more than that because it verifies errors that the compiler can't detect. Currently, is a tool supported in all programming languages.

Now, knowing what is a "lint", I can explain the concept of an "eslint". "Eslint is an open source JavaScript linting utility that helps you overcome developer errors". In resume, is a lint designed for JavaScript. It is interesting because it has a lot of pluggable rules and allows the developers create new custom rules. I must say that this tool has been modified a lot of times to improve it and to get better its performance.

You can visit my profile (navx) on Crowdin's website to find proof of authorship. Also, you can visit the Activity tab in the Node.js project and filter my contributions between October 24th and October 25th, which were the dates of the translation and the corrections respectively.