-
Notifications
You must be signed in to change notification settings - Fork 717
[Contributing.md] Suggestion to improve the contribution best practices #9928
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
Conversation
Addressing @fantasai's feedback and removing double-whitespace-after-period.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
As this isn't a spec, unfortunately these guidelines aren't quite applicable (since there's no Editor :P ). As I note a couple of approvals and a thumbs-up from one of the chairs, I'll leave it to you all to decide when it's appropriate to merge once @fantasai has given it a re-review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, this is consistent with my rough understanding of current WG expectations.
We will announce this update on the Feb 28 call and can take further improvements |
To those following: filed a small PR to clarify where PRs should originate from: #10009 |
This is merely a suggestion to improve the contribution best practices to reflect (what I think is) the actual status quo.
This is based on an attempt to figure out how we could have avoided some incidents that ruffled a few feathers, by being clearer about expectations; I'd welcome feedback about whether this is useful or if it could be improved in some other way.