Skip to content

Add PR review rules for translations #795

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 7 commits into from
Feb 25, 2025
Merged

Add PR review rules for translations #795

merged 7 commits into from
Feb 25, 2025

Conversation

david-a-wheeler
Copy link
Contributor

No description provided.

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
@david-a-wheeler
Copy link
Contributor Author

@gkunz @balteravishay (WG co-chairs) and @ninan27 @Muuhh-CTJ @shimos (proposed Japanese trusted translation team) - I propose this to ensure translations are reviewed. I think this proposal should be discussed at the next Best Practices WG meeting, and if agreed on, merged. Let me know if this is sensible.

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
@balteravishay
Copy link
Contributor

balteravishay commented Feb 20, 2025 via email

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
@david-a-wheeler
Copy link
Contributor Author

david-a-wheeler commented Feb 20, 2025

balteravishay - you're welcome! I've added this PR to the list of items to discuss at the next working group meeting: https://docs.google.com/document/d/1u1gJMtOz-P5Z71B-vKKigzTbIDIS-bUNgNIcfnW4r-k/edit?tab=t.0 - hopefully there will be general agreement & we'll move on.

The main issue at the moment is the Japanese translations of the labs. But we may as well set the general rule & then we know how to cover it.

Anyone, including trusted translation team members, is welcome to
note any issues about any PR.

However, in this text, make it clear that the trusted translation team
members are focusing on the *translation*. They might not notice
other issues, nor is it reasonable to expect them to do so.
Let's make sure we're *not* asking them to do anything unreasonable.

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
Copy link
Contributor

@gkunz gkunz left a comment

Choose a reason for hiding this comment

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

I like this very much. Thank you @david-a-wheeler and particularly the translation team to push this forward. I just have one comment specifically on the management of labels.

Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
Copy link
Contributor

@gkunz gkunz left a comment

Choose a reason for hiding this comment

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

thanks!

@david-a-wheeler
Copy link
Contributor Author

I've created an example change so we can try out the process (as well as potentially fix a problem): #798

I had to create the "Japanese" label, but now that it's created I think all should work well.

@gkunz
Copy link
Contributor

gkunz commented Feb 25, 2025

Thanks for creating the label - this step is what I had in mind when posting my prior comment. The test PR also looks good!

@06kellyjac
Copy link
Contributor

Is there interest in creating actual GH teams? Then the repo could leverage CODEOWNERS to auto request & require the team's review rather than this being a manual process/standard?

It looks like to make that useful translation teams would need repo write access which may be undesirable.

@david-a-wheeler david-a-wheeler merged commit 7484e81 into main Feb 25, 2025
5 checks passed
@david-a-wheeler
Copy link
Contributor Author

I added issue #801 to discuss using GitHub teams in the future. I thought it was more important to have some process now, and then we can refine it later.

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.

4 participants