Skip to content

Conversation

@ksen0
Copy link
Member

@ksen0 ksen0 commented Aug 21, 2025

This PR includes some updates of expectations for PRs, including how contributors are assigned, and what kind of timeline can be expected. The phrasing is intended to make more clear the practices that have already been used in some cases.

Tagging all other maintainers: @davepagurek @limzykenneth @perminder-17 @Qianqianye

@ksen0 ksen0 marked this pull request as ready for review August 21, 2025 20:33
Copy link
Collaborator

@perminder-17 perminder-17 left a comment

Choose a reason for hiding this comment

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

Looks nice to me! Just a single typo.


Similarly, you should work at your own pace and be confident that there is no hard time limit on how long you can spend working on something. That being said, if you are having trouble with any aspect of your code contribution, do not hesitate to ask for help in the issue, the stewards and maintainers, as well as members of our community, will do our best to guide you!

In some cases, issues may be time sensitive - so either maintainers will work on these directly, or explain any important deadlines. If the issue has a deadline, and a contributor isn't able ot finish on time, it may be reassigned. This is an exception, though, and not the rule. Generally, you should work at your own pace and be confident that there is no hard time limit on how long you can spend working on something. If you are having trouble with any aspect of your code contribution, do not hesitate to ask for help in the issue, the stewards and maintainers, as well as members of our community, will do our best to guide you!
Copy link
Collaborator

Choose a reason for hiding this comment

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

In this line,

a contributor isn't able ot finish on time,

"ot" should be replaced by "to" I guess.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for catching it!

@Qianqianye
Copy link
Contributor

Lgtm! Thanks for updating it. Just a quick note that this doc is translated, so we’ll need to update the translations afterwards as well.

@ksen0 ksen0 merged commit 4287c1c into main Sep 2, 2025
5 checks passed
@ksen0 ksen0 deleted the ksen0-patch-2 branch September 2, 2025 10:47
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