08:31:31 RRSAgent has joined #webwewant 08:31:31 logging to https://www.w3.org/2021/10/19-webwewant-irc 08:31:33 RRSAgent, stay 08:31:36 RRSAgent, make log public 12:06:32 jeff has joined #webwewant 14:54:59 stephstimac has joined #webwewant 14:58:11 emeyer has joined #webwewant 14:58:16 takio has joined #webwewant 14:58:41 cwilso has joined #webwewant 14:59:08 Zakim has joined #webwewant 14:59:15 Zakim, this is WebWeWant 14:59:15 got it, cwilso 14:59:26 chairnick: stephstimac 14:59:30 scribenick: cwilso 15:01:59 tantek has joined #webwewant 15:02:08 present+ 15:02:15 Present+ stephstimac, cwilso, dom, briankardell, ivanherman, louisMaher, Pierre-AntoineChamin, TakioYamaoka, jeffJaffe, RakashiMinamii, EricMeyer, Andrew Williams 15:02:23 Present+ FrancoisDaoust 15:02:28 present+ 15:02:32 zakim, who is here? 15:02:32 Present: jeff, stephstimac, cwilso, dom, briankardell, ivanherman, louisMaher, Pierre-AntoineChamin, TakioYamaoka, jeffJaffe, RakashiMinamii, EricMeyer, Andrew, Williams, 15:02:36 ... FrancoisDaoust 15:02:36 On IRC I see tantek, Zakim, cwilso, takio, emeyer, stephstimac, jeff, RRSAgent, dom 15:02:55 Present+ tantek 15:03:06 Present+ AtsushiShimono 15:03:09 atsushi has joined #webwewant 15:03:11 Present+ WendySeltzer 15:03:12 pchampin has joined #webwewant 15:03:15 steph: I'm a PM on the MS Edge Dev Exp team, and this is about the WebWeWant project. 15:03:29 Present+ DanAppelquist 15:03:36 Present+ Sam 15:03:44 ... WWW is a x-browser standards initiative to identify problems people who build with the web have. 15:03:48 ...started in 2019 15:03:49 Present+ JohnRiviello 15:03:54 dietrich_ has joined #webwewant 15:04:02 Present+ DietrichAyala 15:04:05 wseltzer has joined #webwewant 15:04:11 ... we're asking "if you could change a something about the web, what would it be?" 15:04:22 Present+ RijubrataBhaumik 15:04:27 Present+ JamesGraham 15:04:43 Present+ AlexCone 15:04:46 ... initially started as an event session, where attendees could present lightning talks on their wants to a panel of experts; 15:05:15 ... due to COVID, we stopped the live events, and we've worked through the backlog of wants; we still get incoming wants, though. 15:05:19 present+ 15:05:28 ... Right now we have ~160-170 wants from developers 15:05:30 Present+ anuvrat 15:05:43 Present+ ChrisNeedham 15:05:59 ... [goes to https://webwewant.fyi/] 15:06:31 -> https://webwewant.fyi/ The Web We Want Web site 15:07:11 -> https://github.com/WebWeWant/webwewant.fyi WebWeWant/webwewant.fyi repo 15:07:18 ... 3 different kinds of wants - 1) easy feature requests for browser features 15:07:27 ... particularly devtools... 15:07:49 ... 2) broader platform features - CSS or JS features. More difficult to get fixed, as they require standards. 15:08:13 3) "Moonshots" - broader problem that needs quite a bit of research and design effort, as well as standards work to address. 15:08:47 -> https://github.com/WebWeWant/webwewant.fyi/tree/main/wants Wants as Markdown files in github 15:09:07 ... with the slowing down of events, we've pivoted to thinking about how we can better use this data 15:09:41 ...what we're trying to get out of this session today is what's missing from the initiative and the data we have right now. 15:09:42 q+ 15:09:51 Present+ WolfgangSchindler 15:09:57 Present+ MichaelChampion 15:10:05 ... we haven't gained a lot of traction in being a definitive source of developer engagement. 15:10:11 q? 15:10:13 q+ to comment on moving topics to CGs and standards 15:10:22 cpn has joined #webwewant 15:10:48 wseltzer: I see a real synergy between this and the incubation pipeline trying to hear needs that people have for the web. 15:10:54 -> https://github.com/w3c/strategy/projects/2 W3C Incubation Pipeline 15:10:55 marie has joined #webwewant 15:11:00 jamesn has joined #webwewant 15:11:02 dka has joined #webwewant 15:11:15 present+ 15:11:42 ack jeff 15:11:42 jeff, you wanted to comment on moving topics to CGs and standards 15:11:42 wolfgang has joined #webwewant 15:11:44 ... are there places the tools could talk to one another, that the people could talk to one another, ??? 15:11:44 q+ to comment on overlapping efforts 15:11:44 riju has joined #webwewant 15:11:46 jgraham has joined #webwewant 15:11:47 ack me 15:11:53 bkardell_ has joined #webwewant 15:11:55 jeffjaffe: interesting effort; on how to funnel this into various standards groups... 15:12:01 q+ 15:12:24 ... I don't really understand how far you've gone on the basic processing. 15:12:53 steph: triage has been done, and they've been categorized... the ones that are on the web site have had some basic research/validation done. 15:13:06 ... some of the wants have been ranked. 15:13:25 present+ BertBos 15:13:31 ... some of the wants, there's not a lot of detail. Some of them are almost explainer-status. 15:13:35 present+ BenjaminDeKosnik 15:13:49 present+ 15:14:04 jeff: if you have an important issue with a spec, sure, you can raise it in the standards WG. 15:14:22 ... all of the groups have Team Contacts you can reach out to. 15:14:53 ack tantek 15:14:53 tantek, you wanted to comment on overlapping efforts 15:15:27 JohnRiv has joined #webwewant 15:15:37 tantek: I'm here to comment and also as a participant. I appreciate the detail Stephanie outlined in the breadth of issues that come through WWW. 15:15:57 ... in general, many of the wants we've seen are user-centric, which is an important perspective. 15:16:26 ... at W3C, sometimes we try too hard to fit everything into a standards-shaped hole. 15:16:52 Present+ JamesNurthen, LouayBassbouss, MichaelKleber, PeterRushforth 15:17:18 ... standards are developed in a lot of different places (TC39, W3C, WHATWG, etc) so it's good to have both perspective,. 15:17:19 scribe+ 15:17:46 kleber has joined #webwewant 15:17:47 ChrisW: we have a bunch of different participants from across the overall web platform space, not just browser vendors 15:17:54 present+ 15:17:58 ... it's not triaging in terms of weeding out the junk, but instead feeding ideas 15:18:14 ... one challenge in incubating standards is to go from "I have a problem" to a detailed explainer to fill that gap 15:18:22 q+ 15:18:28 ... how to prioritize this - each vendor will have a very different prioritization 15:18:35 ... getting lots of different perspectives helps 15:18:49 scribe+ 15:19:06 q? 15:19:11 JohnRiviello: is there a way those of us who speak at conferences can help promote this? 15:19:18 q+ 15:19:25 ack dw 15:19:25 ack cw 15:19:25 ack jo 15:19:51 steph: you can evangelize this as a community platform, people can submit directly on the Github or the web page, and participate in the discussion 15:20:01 ... we are looking for more engagement to prioritize 15:20:40 ... there is a prioritized view, I'll share 15:21:06 Dom: thanks for the presentation - great source of inspiration. Are there any success stories you can share? 15:22:00 steph: most of the wants that have become features are devtools features: someone did submit container queries, but I don't want to claim that as our success. 15:22:23 ... I like that idea. 15:22:54 tantek: did we talk about the distributed upvoting system that Aaron built? 15:23:07 Bert has joined #webwewant 15:23:37 q+ to ask: do you encourage developers to document the user need when they are registering a want? 15:23:40 present+ Bert_Bos 15:23:50 steph: no. on the website, Aaron hooked up web mentions, so we get broader reach via Twitter et al. We also wanted to hook that into Github to show want-ers. 15:24:25 s/web mentions/webmentions 15:24:25 ack me 15:24:25 ack dka 15:24:26 dka, you wanted to ask: do you encourage developers to document the user need when they are registering a want? 15:24:34 tantek: in particular, this was trying to plug in to the community, not just build another silo 15:24:51 dka: one of the things we do in TAG is ask to document user need 15:24:53 q+ 15:25:01 q+ to respond to Dan 15:25:16 ... what do you to do inspire developer wants? 15:25:50 s/plug in to the community/plug into the community, and use the actual web to participate in the Web We want/ 15:26:01 steph: this does come up when we do research to validate whether these are validate wants 15:26:05 i wonder how the WebWeWant list compares to the MDN DNA results of top developer pain points.... 15:26:24 dka: when we ask for use need, we could ask them to point to WWW 15:27:19 cwilson: we've looked at tying back to webwewant as one of the signals of developer support in our chrome process 15:27:19 q? 15:27:24 ack cw 15:27:24 cwilso, you wanted to respond to Dan 15:27:25 ack cwilso 15:27:40 q+ 15:27:56 thanks @tantek, i'm in a mutezone! 15:28:04 steph: re: MDN DNA, it's somewhat comparable. 15:28:07 ack brian 15:28:11 ack bk 15:28:13 bkardell: they ask the questions in very different ways 15:28:45 ... we also have State of CSS, which asks for similar data but in very different ways; I don't think the data ends up being highly correlated. 15:28:56 q? 15:29:26 steph: any other thoughts? 15:29:44 bkardell: I wonder if anyone on the call has submitted a want? 15:30:01 ... it would be good to get some feedback 15:30:02 The MDN survey ususally shows compat as a big problem, but I think the web we want is more related to features rather than difficulties with existing features 15:30:09 *new features 15:30:24 peter rushforth: I submitted one 15:30:33 ... it's excellent to be asked what you want. 15:30:48 ... please keep it going 15:30:48 weiler has joined #webwewant 15:30:48 tidoust has joined #webwewant 15:31:00 ... it doesn't come up on my radar too often, but I'd like to help promote 15:31:13 q+ 15:31:26 [I note that the "If you are already attending one of the events we’ll be at, would you consider presenting your idea in person?" question does not seem to have a "yes" choice] 15:31:44 tantek: you can post a like of a want on your own website, and that will show up 15:32:16 q? 15:32:27 ack jamesn 15:32:48 jamesn: when you look through these on Github, if we know there's work to solve this want going on, is it useful to add a pointer? 15:32:57 q+ 15:33:02 steph: yes, definitely. any references are very helpful 15:33:21 ack ws 15:33:51 wseltzer: in terms of browsing the site to add that metadata... is there any way to browse the site to see the metadata ("security", "css" etc) 15:34:19 this is kind of an interesting idea wseltzer 15:34:50 steph: yes. On the website there isn't a good way to navigate the tags, but you can go into a want that is tagged "accessibility" and click the "accessibility" tag to get all the wants tagged with accessibility. 15:34:55 Present+ AvneeshSingh 15:35:16 wseltzer: thanks, the WebAppSec WG is looking for good ways to get developer feedback. 15:35:21 q? 15:35:34 steph: the website is in the process of being redesigned to make it easier to navigate. 15:36:05 bkardell: I think it's a great idea to let WGs know they could participate in their own triage. 15:36:14 q+ 15:36:24 ack kleber 15:37:10 kleber: do you have any thought of the freshness of things on the site? Some things seem a little stale (article posted from 2014 on promoting secure sites in Google search results, e.g.) 15:37:56 steph: I think we need to grow capacity and depth of research bandwidth. 15:38:25 ... we still want to bring up things that weren't addressed; but we have limited triage capacity, so we're not always experts. 15:38:29 q? 15:38:38 emeyer has left #webwewant 15:39:00 tantek: how many folks here are going to go to WWW to submit a want? 15:39:33 bkardell: this seems like a somewhat biased crowd. 15:39:43 ... but pull requests are welcome! 15:40:21 tantek: or file bugs! 15:41:14 tantek: wondering if folks here every run into times that they don't know what group or organization to go to? 15:41:57 Dom: working on web components frequently has this kind of confusion 15:42:19 steph: incubation pipeline is the right way to express our primary intent. 15:43:05 steph: question for the group: is there anything that may be missing from this data that would make it more helpful? 15:43:38 peter rushforth: maybe search? More categories? 15:43:56 Sam: can people submit contact info? 15:43:59 steph: yes 15:44:08 q+ 15:44:35 JonRiviello: would be nice to know if there was like a playbook for these to go through the process 15:44:51 the web we have 15:44:57 james: can you vote without sharing on social media? 15:45:30 steph: on github; we want to implement an upvote system on the site that doesn't use social media, but that's tbd 15:45:39 james: github upvotes aren't synced with the site 15:46:03 https://imgflip.com/i/5r0qsq 15:46:40 tantek: are there other places we'd want to post upvotes other than social media? 15:46:52 dom: +1s/thumbs up on GH would be useful. 15:47:08 steph: we have to figure out how to get them properly synced 15:47:11 q? 15:47:14 ack james 15:48:03 steph: any other feedback? 15:48:52 dom: we have the collection of data from browsercompatdata/MDN - that might be another entry point? 15:50:19 q+ 15:50:48 also answered to james: you can upvote from your own website in addition to social media 15:50:51 steph: we talked about caniuse, etc. 15:50:58 cwilso: not sure if it's possible to unify 15:51:25 dom: related to this remotely is browsercompat data 15:51:47 I look forward to steph solving this! :) 15:52:13 -> https://github.com/w3c/browser-specs browser-specs: A machine-readable list of specifications used to build Web browsers 15:52:16 bkardell: one of the things that makes this hard to track is that although you can track back from shipping, most wants don't progress in a linear fashion to shipping 15:52:35 emeyer has joined #webwewant 15:52:37 s/browsercompat data/browser-specs data 15:52:54 ... it's a squiggly line. 15:53:19 emeyer has left #webwewant 15:53:20 steph: thanks all! 15:53:51 ... you can find me on WWW or twitter (seaotta) 15:53:55 thanks for hosting this! 15:54:46 dka has left #webwewant 15:55:17 rrsagent, make minutes 15:55:17 I have made the request to generate https://www.w3.org/2021/10/19-webwewant-minutes.html cwilso 15:55:20 rrsagent, make minutes public 15:55:20 I'm logging. I don't understand 'make minutes public', cwilso. Try /msg RRSAgent help 15:55:37 rrsagent, make logs public 15:56:51 Meeting: WebWeWant.fyi 15:56:51 RRSAgent, be kinder with cwislo 15:56:51 I'm logging. I don't understand 'be kinder with cwislo', dom. Try /msg RRSAgent help 15:57:31 chair: stephstimac 15:57:35 rrsagent, draft minutes 15:57:35 I have made the request to generate https://www.w3.org/2021/10/19-webwewant-minutes.html wseltzer 16:21:28 Ian has joined #webwewant 16:21:34 Ian has left #webwewant 18:16:54 Bert has left #webwewant 18:21:52 Zakim has left #webwewant 19:23:16 tidoust_ has joined #webwewant 22:59:03 jeff has joined #webwewant 23:59:32 tantek has joined #webwewant