15:58:43 <RRSAgent> RRSAgent has joined #cg-program
15:58:47 <RRSAgent> logging to https://www.w3.org/2026/03/23-cg-program-irc
15:58:47 <Zakim> Zakim has joined #cg-program
15:59:48 <dom> Meeting: Community Group Program CG Meeting
15:59:53 <dom> Chair: Ian, Dom
16:00:03 <dom> Present+ Ian, Dom, Elf
16:00:50 <dom> Agenda: https://lists.w3.org/Archives/Public/public-council/2026Mar/0000.html
16:02:13 <elf-pavlik> elf-pavlik has joined #cg-program
16:02:26 <elf-pavlik> present+
16:05:16 <dom> Present+ DeborahDahl
16:05:20 <Ian> -> https://www.w3.org/2026/Talks/beta-plan-20260323.pdf Ian slides
16:05:28 <dom> Slideset: https://www.w3.org/2026/Talks/beta-plan-20260323.pdf
16:05:49 <dom> Present+ Yoav
16:06:20 <dom> Topic: Preparing for beta of new CG specification styles
16:06:27 <dom> [slide 2]
16:07:19 <dom> [slide 3]
16:08:07 <cwilso> present+
16:08:14 <dom> [slide 4]
16:09:03 <dom> [slide 5]
16:09:49 <dom> [slide 6]
16:13:20 <dom> cwilso: the "transfer for standardization" change addresses my feedback re ambiguity on standardization progress
16:13:46 <Ian> Ian: Were you thinking of linking to implementation traction model?
16:14:03 <Ian> Dom: not initially. It's mostly document what signals we are using for these types of specs
16:14:29 <dom> -> https://github.com/w3c/cg-program/pull/41 implementation traction model
16:15:06 <dom> Ian: we have had questions about re-using the metadata for non-CG specs - no reason not to extend this
16:15:12 <dom> ... to TR specs if there is demand
16:15:16 <Ian> Yoav: I want the metadata for WG specs!
16:15:38 <dom> Yoav: also useful to look at sub-spec features
16:16:14 <Ian> Dom: For browser specs we have the advantage of web features project. I would expect we could highlight different features for different specs.
16:16:31 <Ian> ..if we were to migrate to WGs, we should find a way to be more granular
16:16:46 <dom> [slide 7]
16:17:50 <elf-pavlik> which page had links to old and new examples?
16:19:06 <dom> Yoav: would it make sense to link to wpt.fyi?
16:19:26 <Ian> Dom: We do link to wpt.fyi for the tests
16:19:33 <Ian> ...we don't document that explicitly as interoperability
16:19:51 <dom> elf-pavlik, https://github.com/w3c/cg-program/tree/main/beta-2026
16:21:38 <dom> Yoav: the interop story is complex, but surfacing some of that complexity might help to avoid making it look more simple than it is
16:22:09 <Ian> Ian: Where would a mortal go to learn the answer?
16:22:13 <Ian> Dom: Caniuse or MDN
16:22:27 <elf-pavlik> https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility ?
16:22:40 <Ian> Dom: These are great questions. I would like to wait to start interviews to get info
16:23:13 <Ian> ...we can find out from the people with the profile we have in mind what they do
16:23:47 <Ian> ...am I interpreting your sense that the signal might appear to be "too positive" about interop?
16:23:54 <Ian> Yoav: I think it's fine.
16:24:04 <Ian> ....but it could be interesting to know "where did it ship"
16:24:10 <Ian> ...and "did everything ship"?
16:24:19 <Ian> Yoav: The MDN table would be helpful
16:24:35 <Ian> Dom: Right now the implementation traction bit tries to be compact
16:24:51 <Ian> ..but this pull request has more information that could be represented:
16:25:02 <elf-pavlik> https://developer.mozilla.org/en-US/docs/Web/API/Scheduler#browser_compatibility
16:25:13 <Ian> https://github.com/w3c/cg-program/pull/41
16:25:24 <Ian> Yoav: People would prefer to click on a link.
16:25:44 <Ian> Dom: I can add another row to the table..
16:27:18 <Ian> Ian: How much of the metadata is automated?
16:27:34 <Ian> Dom: Our goal is "as much as possible" but some will need to be manual at some stages of the spec's life
16:27:42 <Ian> ...the main thing will be the standardization plan
16:28:09 <Ian> ...we build on the shoulders of the browser ecosystem for much of this. But for non-CG specs it will initially be more manual work for editors.
16:28:13 <Ian> (Ian: that's phase 3)
16:28:53 <dom> Ian: still gathering infos about candidate devs and regulators for interviews
16:29:52 <dom> Yoav: I can find people at Shopify
16:29:59 <dom> Topic: AoB
16:30:12 <dom> Ian: we will do a CG revamp recap at the upcoming W3C AC meeting
16:30:21 <dom> s/a CG/a short CG/
16:30:44 <dom> Ian: suggest our next call should be in May
16:31:22 <dom> Debbie: re regulators, it's not just regulators, but any kind of gov agencies who might give recommendations based on specs
16:31:42 <dom> ... there is the open source week at the UN in June - might be a good thing to raise at that meeting
16:32:10 <dom> Ian: was talking about that very week yesterday; I would want to talk with people sooner than that, but may still be a good opportunity
16:32:21 <dom> ... e.g. during the Community day of that week
16:32:45 <dom> Elf: what's the earliest CGs could start using these new styles?
16:33:09 <dom> Ian: we haven't considered this yet - want to do some early testing to remove hiccups
16:33:35 <Ian> Dom: Maybe not "after the beta" but rather "phase 2 or phase 3"
16:33:46 <Ian> ...which Cg would you like to argue for early adoption?
16:33:50 <Ian> ...we could do more work on metadat
16:33:56 <Ian> s/metadat/metadata/
16:34:03 <Ian> Elf: Solid CG
16:34:29 <Ian> ...there's be a solid symposium at the end of April...with more promotion and traction; having a new design would be nice.
16:34:39 <Ian> ...I'd need to chat with the CG chairs
16:35:07 <elf-pavlik> https://sosy2026.eu/
16:35:48 <dom> RRSAgent, draft minutes
16:35:49 <RRSAgent> I have made the request to generate https://www.w3.org/2026/03/23-cg-program-minutes.html dom
16:45:40 <elf-pavlik> I think light mode in new designs is much better than in old. Are there any plans for a dark mode or they will be only one design?
17:17:32 <Ian> Good question.
17:18:01 <Ian> RRSAGENT, set logs team
17:18:03 <Ian> RRSAGENT, set logs public
17:18:12 <Ian> elf-pavlik, I'll look into that.
17:31:46 <elf-pavlik> ty