Uh oh!
There was an error while loading. Please reload this page.
Quantifiers +, *, ? and {n} - #429
Conversation
nazarepiedady
left a comment
There was a problem hiding this comment.
@peruibeloko, you did a great work here, so there is not so much things to be reviewed.
I will let the rest on your hands and our colleagues.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
javascript-translate-bot
commented
Feb 6, 2024
Please make the requested changes. After it, add a comment "/done". |
nazarepiedady
commented
Mar 8, 2024
@jonnathan-ls, could you review it? |
nazarepiedady
commented
Mar 8, 2024
@peruibeloko, I think you could also look at your own pull request and approve it if you agree with what you did. This would help a lot when we don't have enough people online to look at it. |
peruibeloko
commented
Mar 8, 2024
@nazarepiedady that would be a conflict of interests, wouldn't it? the idea of reviews is to catch errors |
nazarepiedady
commented
Mar 8, 2024
@peruibeloko, yes, but you are also a reviewer even not being a maintainer. I also think that you have a good point. |
peruibeloko
commented
Mar 23, 2024
/done |
nazarepiedady
commented
Mar 24, 2024
@peruibeloko, excellent, now we can go forward. We need to merge all current opened pull request to do a good review on the issues and to organise the things to start to add new translations. |
jonnathan-ls
commented
Mar 30, 2024
I agree with @peruibeloko in relation to the translator ending up accepting the PR itself, although it is a documentation repository, if we consider the same premise as the code, whoever opened the PR may end up missing errors that they would not end up catching, hence the need to have reviewers for a look beyond the context (this corroborates the project's premise of having 02 reviewers, to avoid possible translation errors and ending up being taken to production when the translation is incorporated into the javascript.info website ' But I also consider @nazarepiedady's observation valid, unfortunately there are few contributors to this project and we need to release the translation. As it is a documentation repository and not a code repository, perhaps we can be a little more flexible, but if we are going to follow a path like this, I think it is worth creating a separate issue first to evaluate the opinion of other maintainers, at the same time time to ensure that we do not violate the premise adopted by the project owner (repository in English). |
nazarepiedady
commented
Mar 31, 2024
@peruibeloko, @jonnathan-ls, unfortunately this project do not have so many active maintainers so if we depend on the maintainers that are not so active we can not go ahead. |
peruibeloko
commented
Apr 2, 2024
@nazarepiedady I think your approval is the only one remaining |
javascript-translate-bot
commented
Apr 2, 2024
Thank you 💖 I updated the Progress Issue #1 🎉 🎉 🎉 |
No description provided.