You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Spanish translation for "Open Source Principle 0: With many eyes, all bugs are shallow" #3714
Could someone please review the translation and provide feedback on accuracy, terminology, and consistency with the Training team's translation guidelines?
I'll incorporate the feedback before proceeding with the next lesson.
Thank you so much for working on this translation! Your draft is conceptually very strong and follows the lesson structure perfectly.
I’ve reviewed the text to help optimize its natural flow, technical terminology, and contextual clarity for Spanish-speaking developers (avoiding some literal English phrasings).
Here are some friendly suggestions for your consideration:
1. Suggested Corrections & Justifications
Original Text (EN)
Provided Translation (ES)
Suggested Correction
Reason for Change
With many eyes, all bugs are shallow
Con muchos ojos, todos los errores son superficiales
Con suficientes ojos, todos los errores son superficiales
Formulation more natural in Spanish, improving the flow of the title expression.
report a problem
reportar un problema
informar de un problema
More natural phrasing in neutral Spanish for reporting bugs.
suggest or provide a fix
sugerir o proveer una solución
proponer o aportar una solución
Avoids the literal and less natural use of "proveer" in this specific context.
improvements happen more quickly
las mejoras suceden más rápido
las mejoras se producen más rápidamente
Enhances readability and fits a professional educational tone.
find/fix bugs
encontrar/corregir errores
encontrar y corregir errores
Avoids using slashes, making the reading experience smoother.
better features
mejores características
mejores funcionalidades
"Funcionalidades" is the precise technical term used in software development.
a reliable recipe for reproducing the bug
una receta confiable para reproducir el error
instrucciones fiables para reproducir el error
"Receta" is too literal; "instrucciones" is a cleaner way to say this..
more noise than signal
más ruido que señal
más ruido que información útil
Clarifies the idiom so it is easily understood by any reader.
Avoid perfection like a plague
Evita la perfección como una plaga
Evita la perfección como si fuera una plaga
A more idiomatic and natural construction in Spanish.
least-hassle route
la ruta menos problemática
la forma más sencilla
Conveys the idea of the easiest path without translating "route" literally.
a plausible promise
una promesa plausible
una promesa creíble
"Creíble" sounds more natural when talking about a promise that builds trust.
2. General Reviewer Notes
Technical Terms: Keeping terms like «código abierto», «código fuente», and «depuración» works beautifully for the open-source context.
Tone: The formal yet welcoming tone is consistent throughout the text.
Feel free to check these out and let me know if you have any questions. Fantastic job on this translation! 🚀
Activity
Pamelasibaja25 commentedon Oct 17, 2026
Hi everyone!
I've completed the first lesson's Spanish translation for the Open Source Basics and WordPress course.
Translation document: https://docs.google.com/document/d/1OEapUr2rMLqjwV1IvPuJcHoV1NGP7sKAkgCWHzxdvDA/edit?usp=sharing
Could someone please review the translation and provide feedback on accuracy, terminology, and consistency with the Training team's translation guidelines?
I'll incorporate the feedback before proceeding with the next lesson.
Thank you!
JAIR187 commentedon Oct 21, 2026
Hi @Pamelasibaja25! 👋
Thank you so much for working on this translation! Your draft is conceptually very strong and follows the lesson structure perfectly.
I’ve reviewed the text to help optimize its natural flow, technical terminology, and contextual clarity for Spanish-speaking developers (avoiding some literal English phrasings).
Here are some friendly suggestions for your consideration:
1. Suggested Corrections & Justifications
2. General Reviewer Notes
Feel free to check these out and let me know if you have any questions. Fantastic job on this translation! 🚀
Pamelasibaja25 commentedon Oct 23, 2026
Hi @JAIR187!
I've incorporated the suggested corrections into the Spanish translation and reviewed the terminology and phrasing for consistency.
Thank you again for your helpful feedback!
I'd appreciate it if you could take another look when you have a chance.