Skip to content

Traducción al Español (es-ES) - OWASP API Security Top 10 2023 #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
EdgarPsda opened this issue Feb 25, 2025 · 2 comments
Open

Traducción al Español (es-ES) - OWASP API Security Top 10 2023 #139

EdgarPsda opened this issue Feb 25, 2025 · 2 comments
Assignees

Comments

@EdgarPsda
Copy link

Hello OWASP API Security Team,

I would like to contribute by translating the OWASP API Security Top 10 2023 into Spanish (es-ES).
So far, I have translated the Introduction section up to API1:2023 - Broken Object Level Authorization.

I have created a separate branch based on develop, following the repository's contributing guidelines. You can track the progress here:
🔗 EdgarPsda/OWASP-API-Security

Before proceeding further, I would like to confirm:

  1. Would you be interested in an official Spanish translation for this version?
  2. Should I submit a single PR once the full translation is complete, or would you prefer incremental PRs per section/module?
  3. Are there any specific formatting or terminology guidelines I should follow for consistency with other translations?

Looking forward to your feedback! Thank you for maintaining such an important project.

Best regards,
Edgar Posada

@PauloASilva
Copy link
Collaborator

PauloASilva commented Mar 11, 2025

Hi @EdgarPsda,

1. Would you be interested in an official Spanish translation for this version?

Yes. The community will benefit from having the OWASP API Security Top 10 translated in as many languages as possible.

2. Should I submit a single PR once the full translation is complete, or would you prefer incremental PRs per section/module?

A single PR is fine.

You can open it right away since it gets updated with your latest commits.
This way other users can track the translation progress and hopefully contribute to it.

3. Are there any specific formatting or terminology guidelines I should follow for consistency with other translations?

Thanks for asking ;)

There's an .editorconfig file in monorepo's root. As long as you adhere to what is specified in there you're good.

I will assign this issue to you so that you can coordinate the translation with other contributors.

Cheers,
Paulo A. Silva

@EdgarPsda
Copy link
Author

Thanks @PauloASilva I will continue working on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants