Node.js Translation to Spanish - 1061 words (Part 26)

In my last report I made a brief introduction to a change log file general format. In this opportunity I will discuss about the specific format of a commit because they have some fields that make easier its understanding. This format also allow the reviewers following the changes among the different versions of the program.

The specific commit format consist on several parts that I will explain in appearance order:

- Memory Block:

It a hexadecimal expression that is also an ID that identify the memory block assigned to the variable, module, document, etc

https://ipfs.busy.org/ipfs/QmNh6ZMPR3Mk5iHuexRP1KREkRY5zuneF2tpuUZeYbz1dL - Module Name:

Next to the memory block number, there is the module name where the modified variable or doc is.

https://ipfs.busy.org/ipfs/QmexZLU6u1GsfvuzpPuduxDiStUorAmQtSN7GSYnynPpsY - Action:

Then there is the executed action with a brief explanation of the change that was made in this module, specifying the involved variables and modules.

https://ipfs.busy.org/ipfs/QmZK16GHjvf1Fx3581efrfEcXptsi6xJuGX21rwM7NyCJv - Collaborator Name:

Between parentheses there is the collaborator's name who made executed the action explain before. This is a way to give credit to those who contributed in the project.

https://ipfs.busy.org/ipfs/QmU1ByfvtX6VPj9aiWAuRsYbeMAHmStK1BUoBWH7wA5gNs

Finally, there is a number that is a reference to the commit. This reference allows collaborators name a commit without explaining it. https://ipfs.busy.org/ipfs/QmdPRGjZFxb5qpP1pKcGj54LKrb93fPXFSoaPc4iVK8jqm

The final result of this format is as follow:

https://ipfs.busy.org/ipfs/QmdoV7UkehGGGTe9L1W5ddiCcJbofB86zaXYfRLbZj6tqR

This format is very simple, but useful and as I said, it is a way to make things easier to open source projects developers and contributors. I must say that may be this is not the only format developers use in change log files. Nonetheless, in Node.js it is the used one and that's why I explained it.

In summary, 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 file there are a lot of grammar and spelling changes that are very important to fix. Although Node.js is an open source project which objective is improve programming, the grammar is very important because people will read this files and documents where the information must be correct and, without spelling, there is no such thing.

This spelling, typo and grammar fixes are a way to expand the open source projects scope and that's why I decided to talk about it in this report.

https://ipfs.busy.org/ipfs/QmX64wVP7T8gHqS91uXcoT4LSjQ3mfXJndpF1J1K3YFC22

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:

There is a word that has been appearing among the change log file and it is "fs" so I decided to do some research about its meaning. In this research I found that fs is a reference to the File System and it "is a method of organizing and retrieving files from a storage medium, such as a hard drive. File systems usually consist of files separated into groups called directories."

A file system is very important because it allows the computer organizing its documents to a future search. It is also up to the administrator making this easier to the machine because he can also organize files and directories.

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 31th and November 1st, which were the dates of the translation and the corrections respectively.