Skip to content

Add a "Translation Team" to the teams page #796

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

Closed
melissawm opened this issue Nov 25, 2024 · 3 comments · Fixed by #806
Closed

Add a "Translation Team" to the teams page #796

melissawm opened this issue Nov 25, 2024 · 3 comments · Fixed by #806

Comments

@melissawm
Copy link
Member

I was thinking about the best way to credit translators for the NumPy.org page, and I thought this might be a good idea. I'd like to propose using the Teams gallery page provided by the scientific python hugo theme to show a "Translation Team".

The only issue is that right now the Teams page is sourced directly from GitHub teams, and there are two problems there:

  • There is no translation team on github (but this would be easily fixed)
  • Not every translator has a github account - they log in to Crowdin with potentially other credentials.

If there is interest and consensus, could we have a manual section on the teams page to add translators? Or source them directly from crowdin?

cc @steppi

@rgommers
Copy link
Member

👍🏼 from me - in general we like to acknowledge any type of significant contribution, and translations contributions deserve that as well (doubly so because they're less visible; no commit stats to look at in the GitHub UI).

@InessaPawson
Copy link
Member

@melissawm Another thumbs up from me. Thank you for facilitating these contributions!
As far as an approach for creating this team's section, what are the drawbacks of syncing with crowdin?

@melissawm
Copy link
Member Author

I am not sure I would go with that option right now as it seems like a very large lift. Looking at

I think if we add a manual toml file this should work? I think we can rely on a manual update for now and think about a potential automation in the future.

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

Successfully merging a pull request may close this issue.

3 participants