-
Notifications
You must be signed in to change notification settings - Fork 70
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
RFC: Web Platform Feature Known Issues Management Repository #206
base: master
Are you sure you want to change the base?
RFC: Web Platform Feature Known Issues Management Repository #206
Conversation
|
||
## Details | ||
|
||
* **Repository Name:** web-platform-tests-feature-issues |
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.
Any repo name will be OK, but I wonder if the shorter web-features-issues would be acceptable?
Co-authored-by: Philip Jägenstedt <[email protected]>
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.
Just to make sure the discussion we've had in the meeting is recorded here:
This RFC needs to explain what problem it's trying to solve. The way it's phrased here it seems like it's about implementing a feature on webstatus.dev
. But given there are existing concerns about the incentive structure generated by that project being detrimental to the overall health of the web platform tests project, anything that's motivated by that project needs to explain how it's going to address those concerns.
Also, if this is something that requires governance, the governance section needs to be much more explicit, rather than just saying "will be established".
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.
I also don't understand what this is for
Rendered