Skip to content

Accessibility #279

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

Merged
merged 29 commits into from
Apr 13, 2021
Merged

Accessibility #279

merged 29 commits into from
Apr 13, 2021

Conversation

fatmabadri
Copy link
Contributor

No description provided.

@netlify
Copy link

netlify bot commented Apr 3, 2021

Deploy preview for tr-reactjs ready!

Built with commit 8dcfce1

https://deploy-preview-279--tr-reactjs.netlify.app

@fatmabadri
Copy link
Contributor Author

fatmabadri commented Apr 3, 2021

Hi @alioguzhan,
Would you make me enable to assign the reviewer and add a label to the PR?

@alioguzhan
Copy link
Member

Hi @fatmabadri

You don't need to make assignments. Since we are only 2 (@yunusemredilber and I), we can manage that process internally. Thanks for your interest.

@alioguzhan alioguzhan self-assigned this Apr 5, 2021
@yunusemredilber
Copy link
Member

I have one more suggestion. I think there are a lot more commits than necessary for this translation. To keep the commit history clear, It might make sense to do "Squash and Merge" at the end. What do you think @alioguzhan ?

@alioguzhan
Copy link
Member

Yes. That makes sense. Let's squash and merge once this is ready to merge @yunusemredilber

Since you are translating one document, it is better if you keep it under one commit or two (with later updates). @fatmabadri

@fatmabadri
Copy link
Contributor Author

Hi @fatmabadri

You don't need to make assignments. Since we are only 2 (@yunusemredilber and I), we can manage that process internally. Thanks for your interest.

Hi @alioguzhan. I have asked to be enabled to add the reviewer myself when making a PR not to make an assignment or something else. This is my last translation. I am not interested to join you internally since you are only two people, managed to the end and the Turkish translation is almost done. Thank you.

@alioguzhan
Copy link
Member

@fatmabadri I thought you were mentioning picking a user from maintainers to review this PR. I didn't think that you would want to assign yourself as a reviewer to your own Pull Request.

Someone else has to be a reviewer for our own PR's. A second or third eye re-views the work that has been done and checks if this is appropriate to be merged. This is the idea about Pull Request and Review process.

Thanks for your work and translation. I will review it as soon as I have some spare time.

@fatmabadri
Copy link
Contributor Author

@fatmabadri I thought you were mentioning picking a user from maintainers to review this PR. I didn't think that you would want to assign yourself as a reviewer to your own Pull Request.

Someone else has to be a reviewer for our own PR's. A second or third eye re-views the work that has been done and checks if this is appropriate to be merged. This is the idea about Pull Request and Review process.

Thanks for your work and translation. I will review it as soon as I have some spare time.

@alioguzhan,
You have misunderstood. I asked to be enabled to add the reviewer myself, I did not say to add myself as a reviewer. I intended to add the maintainer while a PR was being made.
I cannot be the reviewer of my own translation. There is no point to do that. Absolutely, my translation has to be reviewed by the maintainer as they are the ones responsible and have more experience to do this. I hope it is clear now. And also thank you for your time.

@fatmabadri
Copy link
Contributor Author

Yes. That makes sense. Let's squash and merge once this is ready to merge @yunusemredilber

Since you are translating one document, it is better if you keep it under one commit or two (with later updates). @fatmabadri

It is one document but it is a quite long one. Translations were made in the different days. Multiple commits were done in order to keep the translated part protected . @alioguzhan

@alioguzhan
Copy link
Member

Yes. That makes sense. Let's squash and merge once this is ready to merge @yunusemredilber
Since you are translating one document, it is better if you keep it under one commit or two (with later updates). @fatmabadri

It is one document but it is a quite long one. Translations were made in the different days. Multiple commits were done in order to keep the translated part protected . @alioguzhan

It is totally fine if this is your preferred way. As I said, we can squash and merge. No problem at all.

@alioguzhan,
You have misunderstood. I asked to be enabled to add the reviewer myself, I did not say to add myself as a reviewer. I intended to add the maintainer while a PR was being made.

I see. So this brings us to my previous answer. Since we do not know who is available or not, It becomes uncertain who will be reviewing some particular PR. If the contributors would have permission to add reviewers, it would be a demand more than an assignment. And this is a concept we don't have here. In our case, I or @yunusemredilber are assigning ourselves. Or we mention each other in a comment by asking kindly if he can review this or not.

Sorry for the misunderstanding.

Copy link
Member

@alioguzhan alioguzhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the translation. See my comments, please.

Review the suggested changes
@alioguzhan alioguzhan merged commit 09b912b into reactjs:master Apr 13, 2021
@fatmabadri fatmabadri deleted the accessibility branch April 13, 2021 21:13
@alioguzhan
Copy link
Member

Thanks for the translation. (Forgot to write this message earlier today)

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

Successfully merging this pull request may close these issues.

3 participants