-
-
Notifications
You must be signed in to change notification settings - Fork 333
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
feat: adding translation rules to README #116
feat: adding translation rules to README #116
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@CBID2 as soon as you update your branch and change if from a draft PR, I think this is ready to be merged. |
I am new to open source, how can I help with contribution? |
Hi @ivansftdejc. You've come to the right place! 😊 We have an intro course to help you get started: https://intro.opensauced.pizza/#/ |
Description
In this PR, I added a translation guidelines section to the README file. This will encourage non-English or bilingual people an opportunity to contribute to the project, and fulfill one of our goals: to make this project more culturally-inclusive.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Closes #93
Relates to #71
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
Note to Reviewers
I was heavily inspired byAstro's Docs approach to encouraging translation contributions. Now I placed this in draft mode because I'm debating on whether to create the translating guide and add it to this PR or do it in another PR after this one is merged. Any feedback is helpful.
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?
Rick from "Rick & Morty" looks confused