17:55:44 RRSAgent has joined #openui 17:55:48 logging to https://www.w3.org/2025/01/21-openui-irc 17:55:48 Zakim has joined #openui 18:02:58 zakim, start meeting 18:02:58 RRSAgent, make logs Public 18:03:00 please title this meeting ("meeting: ..."), gregwhitworth 18:03:05 meeting: Open UI Design System 18:03:12 present+ 18:03:16 present+ 18:03:32 chris: reviewing RFC process and discuss that 18:03:49 chris: I want to see if we're in agreement with where that is going and that can set the foundation for the initial components 18:04:17 PR: https://github.com/openui/design-system/pull/4 18:05:13 chris: Looked at RFC proecess by other Design Systems and the idea is for it to propose a way for us to have initial proposals and ways for people to propose it and have some discussion and track it from RFC -> full components. And once it is a component it will go through the standard process 18:05:54 chris: I provided some templates on ways to fill it out and modifying it a bit to have a better way to track it. With react and carbon there is an internal working system and everyone can propose in and this is everyone proposing in 18:12:11 bkardell: I can't imagine what a RFC is for a design system and what it looks like 18:12:41 bkardell: I was looking at the inspirations and what you have an they're easier to imagine for an RFC as it's a functional thing but do you have an RFC that's just "tabs" 18:13:21 chris: Yeah, normally they're for an already established system. For us starting blank we'll say that these are the components we want and then have them follow that pattern 18:13:30 chris: I think it can follow the larger systems 18:13:43 bkardell: do you have an example that uses an RFC? 18:13:58 chris: Carbon uses it and so does React, but they use a modified version of Reacts 18:14:06 bkardell: I'm missing something here 18:14:13 bkardell: Where are the RFCs 18:14:22 brad: I posted a link to them 18:14:50 Chris: part of what react does that is different is that they have a separate repo for their RFCs and that makes it a bit harder to find them 18:15:10 chris: you have that work occurring elsewhere and it graduates into the main repo. To me that feels a bit disconnected 18:15:27 chris: if we want to break it into a separate repo\ 18:15:36 brad: this is a tighter scope 18:15:47 chris: if we get a year or two down the road we can break it off if necessary 18:16:02 specific example provided by brad: https://github.com/loganmccaul/rfcs/blob/master/text/0000-carbon-addons.md 18:16:13 chris: merge the RFCs in the main repo 18:16:42 hdv: I kind of had the same thing as Brian as I can see a lot of different RFCs occurring 18:16:51 hdv: I can imagine people will do a specific component 18:17:04 hdv: maybe we should make it clearer what a proposal looks like 18:17:14 hdv: the one week period does seem very short? 18:17:26 hdv: how can we make that work? 18:17:56 chris: the RFCs go through a comment period for a while it's only once they're tagged that they're ready for inclusion that there is a final week call for comments 18:18:54 gregwhitworth: we may have an RFC that says how a component should be auhored… personally I think the fastest way to figure this out and take a component of choice and open a PR that does your RFC 18:19:29 gregwhitworth: eg when you author them, this is the shape it'd take 18:19:56 brad: agreeing with you, model it through the initial seeding of them and by the time that other people are coming to this there are some good examples 18:20:21 brad: bolster them as we go and this occurs with design systems normally anyways 18:20:38 brad: it's only after the initial stuff is in place that other people come to the party and determine how to do things 18:20:49 brad: do it and model it and put things down and it's a good first step 18:21:01 brad: the spirit of the initial work will be how we bolster the other work 18:21:35 chris: to that point Brad and Brian and break out a RFC for a new component vs an existing component? 18:21:47 chris: ultimately the template for both will vary slightly 18:21:56 chris: I think the tabs should be left to right vs right to left 18:22:16 brian: I wouldn't worry about changes to components as we don't have them yet 18:22:33 brian: I think we can make them pretty simply once we have them 18:23:33 brad: I was hoping to switch gears to the short list of components that we should start 18:24:05 chris: before we do that, @brian here is the questions that would need to be answered *shares screen that shows PR* 18:24:46 chris: do you want to provide a list of initial components? 18:25:02 brad: I think this is a good connect the dots and take it on as a first component we bite down on to round this out 18:25:12 brad: what components to do, I have an idea to run by you 18:25:22 brad: trying to have this be inclusive and open 18:26:15 brad: that whole matrix could be a poll and set that up for a couple weeks; which should be included in the global design system and allow that to run for a couple of weeks and get the results and that would be a fun and inclusive way to get the word out and get people's input and align our priorities 18:26:30 bkardell: I don't follow it 18:26:52 brad: send out a survey to have them vote on which ones they will want 18:27:02 chris: so we tackle those in priority order? 18:27:10 brad: we allow it to influence the direction 18:27:36 brad: allows us to have a collective insight into what people expect 18:29:54 gregwhitworth: should we just do button 18:30:37 brad: maybe we done that isn't controversial but let's maybe start with badge because it's inert component and there are states, etc but it may be a good one to start with 18:30:49 brad: button is notorious for being an iceberg 18:31:00 brad: tabs and accordions can get really complicated 18:31:12 brad: it doesn't do a whole lot but it can give us enough to chew on 18:31:25 brad: we make solid progress with this one when working with design system teams 18:34:19 Zakim, end meeting 18:34:19 As of this point the attendees have been hdv, gregwhitworth 18:34:20 RRSAgent, please draft minutes 18:34:22 I have made the request to generate https://www.w3.org/2025/01/21-openui-minutes.html Zakim 18:34:30 I am happy to have been of service, gregwhitworth; please remember to excuse RRSAgent. Goodbye 18:34:30 Zakim has left #openui 18:36:01 rrsagent, please leave 18:36:01 I see no action items