- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Jan 2019 17:09:50 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `More WPT reviewers needed`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: More WPT reviewers needed<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3496<br> <dael> ericwilligers: I wanted to bring attention, there are a few specs with essentially no reviewers. Some people may be listed but don't check their review emails.<br> <rachelandrew> present +<br> <dael> ericwilligers: It would be helpful if more people volunteered. I can get Blink people to review, but that's not available to everyone. More people should be able to submit tests without going through a browser<br> <dael> Rossen_: In general we've had this discussion many times in the past. Both tests and test reviewers have been a struggle to come about.<br> <dael> Rossen_: Was there anything you were doing to gather external contributions<br> <dael> ericwilligers: No. This is tests I wrote that I thought it unfortunate no one is reviewing<br> <dael> gsnedders: It's notable that CSSWG specs are much harder to get review than any other spec. People who work on layout aren't interacting with wpt the way other groups are. Be interested to know reasons<br> <dael> chris: I've tried to review tests. I share ericwilligers frustration. I'l submit tests and they sit<br> <dael> dbaron: I review tests when I have time, but I think it may be more useful to bug individuals then bug the whole WG for reviews<br> <dael> ericwilligers: I spec a person and nothing happened<br> <dael> dbaron: Some of us have hundreds of thigns in github queues. If you want me to review something, send an email<br> <dael> ericwilligers: That's all for this issue, thanks<br> <tantek> Last time this topic came up, the larger problem of WPT being poorly documented (processes etc.) was the key takeaway<br> <tantek> pretty sure there was an issue filed too<br> <dael> Rossen_: Than you for bringing it to attention again. For us to be successful as a WG and making sure standards are pushed through, tests are a huge part. If anyone submits tests, please be accomodating. I'm bad at following all repo build up, but I try and respond to direct emails<br> <gsnedders> tantek: that doesn't explain the disparity between CSS and pretty much every other group, though<br> <dael> Rossen_: Let's see if we can drain that queue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3496#issuecomment-454860281 using your GitHub account
Received on Wednesday, 16 January 2019 17:09:51 UTC