Repository navigation
[Translation] Spanish Support #777
Description
To better reach Spanish-speaking communities, it's necessary to provide support for Spanish. This issue proposes translating the documentation into Spanish to improve accessibility and engagement.
Reacted by Jose Roman Martin Gil
Activity
welcome commentedon Feb 26, 2025
🎉 Welcome to The InnerSource Commons community, and in particular to our patterns! 🎉 We're really excited to have your input into the project! 💖
If you haven't done so already, please check out our Contributing Guidelines. If you need to connect more synchronously with members of The InnerSource Commons community, come chat with us in our Slack workspace.
0vas commentedon Feb 26, 2025
I'm working on it. Please assign me to the issue.
spier commentedon Feb 26, 2025
That is amazing @ovas04!
Are you already part of our Slack? I know that we have a couple of Spanish speakers there as well, who might be able to help with reviews etc
spier commentedon Feb 26, 2025
@ovas04 maybe you found these already but here is some documentation about our translation process specifically:
https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/translation/README.md
0vas commentedon Feb 27, 2025
Hi @spier, I am in. Thanks for the reference link
0vas commentedon Mar 5, 2025
Hi @spier , I have completed the translation of:
I am currently validating that all status checks pass before creating a PR. However, I am facing an issue related to mindmap generation because all status checks, not just the ones for the new language, are failing. I checked #620 as a reference and applied the same changes.
Do you know of any issues related to mindmap generation in a forked repository?
Here is my PR in my forked repository (https://github.com/ovas04/InnerSourcePatterns/pull/2/checks). If you have time, I would like you to review it.
spier commentedon Mar 5, 2025
hi @ovas04! Great job figuring out most things on your own.
Hopefully our documentation was helpful? If you got anything to add there, we are happy to hear any feedback.
For the mindmap:
There is a technical issues with generating these with our github action anyways.
Let's just ignore this for the time being.
So you can already submit your PR to the upstream repo (this repo here).
Then I can integrate this with a staging version of our book, so that we can test if everything is working.
Then we can iterate on that PR until we are done :)
Thanks a ton already for your work!!! 🥳
yuhattor commentedon Mar 5, 2025
Amazing contribution!!
Thank you @ovas04!
0vas commentedon Mar 7, 2025
Thanks, @spier @yuhattor. I am working on implementing InnerSource, and the information on this page has been useful for designing the solution. So, it's my pleasure to contribute, and I would like to contribute a pattern related to my custom learning in the short term.
I just created a PR, but it seems that a status check failed because an old link is broken, and I can’t handle it. Let me know if I need to change anything, please.
spier commentedon Mar 7, 2025
@ovas04 very much looking forward to that other pattern as well! You can even braindump your idea straight into a GitHub issue if you like (we have an issue template that contains the structure used in our patterns). So you can use that as a quick way of doing a brandump, without the need for a PR.
Also curious to learn at some point which patterns your picked for the practices in your use case. Every org favors different patterns, so this is always interesting.
rmarting commentedon Mar 11, 2025
I would like to join here too 😄 , at least, as reviewer of the main content.