Meeting minutes
chris: reviewing RFC process and discuss that
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
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
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
bkardell: I can't imagine what a RFC is for a design system and what it looks like
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"
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
chris: I think it can follow the larger systems
bkardell: do you have an example that uses an RFC?
chris: Carbon uses it and so does React, but they use a modified version of Reacts
bkardell: I'm missing something here
bkardell: Where are the RFCs
brad: I posted a link to them
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
chris: you have that work occurring elsewhere and it graduates into the main repo. To me that feels a bit disconnected
chris: if we want to break it into a separate repo\
brad: this is a tighter scope
chris: if we get a year or two down the road we can break it off if necessary
specific example provided by brad: https://
chris: merge the RFCs in the main repo
hdv: I kind of had the same thing as Brian as I can see a lot of different RFCs occurring
hdv: I can imagine people will do a specific component
hdv: maybe we should make it clearer what a proposal looks like
hdv: the one week period does seem very short?
hdv: how can we make that work?
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
<hdv> 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
<hdv> gregwhitworth: eg when you author them, this is the shape it'd take
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
brad: bolster them as we go and this occurs with design systems normally anyways
brad: it's only after the initial stuff is in place that other people come to the party and determine how to do things
brad: do it and model it and put things down and it's a good first step
brad: the spirit of the initial work will be how we bolster the other work
chris: to that point Brad and Brian and break out a RFC for a new component vs an existing component?
chris: ultimately the template for both will vary slightly
chris: I think the tabs should be left to right vs right to left
brian: I wouldn't worry about changes to components as we don't have them yet
brian: I think we can make them pretty simply once we have them
brad: I was hoping to switch gears to the short list of components that we should start
chris: before we do that, @brian here is the questions that would need to be answered *shares screen that shows PR*
chris: do you want to provide a list of initial components?
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
brad: what components to do, I have an idea to run by you
brad: trying to have this be inclusive and open
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
bkardell: I don't follow it
brad: send out a survey to have them vote on which ones they will want
chris: so we tackle those in priority order?
brad: we allow it to influence the direction
brad: allows us to have a collective insight into what people expect
gregwhitworth: should we just do button
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
brad: button is notorious for being an iceberg
brad: tabs and accordions can get really complicated
brad: it doesn't do a whole lot but it can give us enough to chew on
brad: we make solid progress with this one when working with design system teams