-
Notifications
You must be signed in to change notification settings - Fork 225
Guidelines: translations #153
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
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.
Apart from the usual grammatical corrections and wording enhancements, may we rename the following terms?
- "Full test suite" --> "Submit tests"
- "Proposed solution" --> "Complete solution" / "Reference solution"
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>
Let's discuss your question here: #154 |
Co-authored-by: kazk <kazk.dev@gmail.com>
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>
Just like #162 , not much going on here. Good to go? |
I don't like cross reviewing, so I'll do it after the last suggestions have been examined... x) (same for the preloaded PR) |
Co-authored-by: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com>
Co-authored-by: Donald Sebastian Leung <donaldsebleung@gmail.com>
It's gotten quiet here, so... merging! |
I would like this to be a set of official quality guidelines which reviewers could use to determine if a Translation is of sufficient quality to be approved.
Any remarks or reviews are welcome!
Discussion: #134
Deploy preview: here