-
Notifications
You must be signed in to change notification settings - Fork 263
Quick Start #372
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
Comments
Reopen as the Quick Start (https://id.react.dev/learn) This is the PR: #500 (tbh I've been waiting for so long to get a beautiful number 😂) |
is my assignee tasked is canceled @mhaidarhanif @resir014 ? 🤔 |
@infrasync We realised some pages had some assignees mixed up while reworking our workflow so you might be caught up in it, sorry about that! Last I checked, you have another page assigned to you. So feel free to start from there |
@infrasync @resir014 Also because we've waited for a few days and there wasn't any Draft PR / PR for this page yet. Therefore we've taken over and the translation itself is already done here: #500 Since 3~ days ago, we've improved the workflow to prioritize who can work on the pages as soon as possible with a real PR. So it's a fair better chance for all contributors. The goal is to complete the translation progress sooner. But it's okay to take any available page that's not yet in progress, there are several other open issues/pages here: https://github.com/reactjs/id.react.dev/issues |
It's ok for me, but I would suggest giving information related to what is expected for contributors such as completion plans, especially timelines, because it seems that in the issue description it is not available 🤔. And for accountability, if you switch assignees on an issue, please inform the previous assignee, because like me, who just wants to contribute, it feels like I'm not considered to contribute. But because there are still several issues available, I still want to contribute, thanks ✨ |
Page: https://id.react.dev/learn
Assignee: @mhaidarhanif
PR: #500
Progress
The text was updated successfully, but these errors were encountered: