David Crespo

syntactic features that we got out of asciidoc was kind of why for complex documents we want to move there you know easy knowing that there's easy ways to link between different sections or other things or kind of a bunch of the other features and you know there's a bunch of features we didn't even use back then that uh now so our colleagues like uh ben knacker is using in the oxql rfd so he could easily do call outs or other things so i i found it to be a you know

syntactic features that we got out of asciidoc was kind of why for complex documents we want to move there you know easy knowing that there's easy ways to link between different sections or other things or kind of a bunch of the other features and you know there's a bunch of features we didn't even use back then that uh now so our colleagues like uh ben knacker is using in the oxql rfd so he could easily do call outs or other things so i i found it to be a you know

Easy to get something basic that looks pretty good. And then if you need to go complex, you had that capability. Whereas with Markdown, you were kind of constrained by the Markdown renderer. And no two renders were going to do it the same way.

Easy to get something basic that looks pretty good. And then if you need to go complex, you had that capability. Whereas with Markdown, you were kind of constrained by the Markdown renderer. And no two renders were going to do it the same way.

I just always used ASCII doctor and just pulled up the HTML file. Um, and just use that. And it was pretty good. It had default CSS too, which just meant you could use it and toss a document somewhere, and people could see it. And it looked fine on both mobile and not mobile, which was really nice as someone who doesn't want to think about CSS.

I just always used ASCII doctor and just pulled up the HTML file. Um, and just use that. And it was pretty good. It had default CSS too, which just meant you could use it and toss a document somewhere, and people could see it. And it looked fine on both mobile and not mobile, which was really nice as someone who doesn't want to think about CSS.

Yeah.

Yeah.

Yeah, specifically for the Gimlet hardware sled.

Yeah, specifically for the Gimlet hardware sled.

Sure. So, I mean, I think to kind of talk about how we use RFDs for Cosmo, it helps a little bit to talk about RFDs for Gimlet along the way. So when we were developing Gimlet, I'd say, you know, this was a time when the first RFDs were in, there's maybe what, 12 of us, 15 of us. And this is before most of the team has started. I mean, this is mid 2020, maybe early.

Sure. So, I mean, I think to kind of talk about how we use RFDs for Cosmo, it helps a little bit to talk about RFDs for Gimlet along the way. So when we were developing Gimlet, I'd say, you know, this was a time when the first RFDs were in, there's maybe what, 12 of us, 15 of us. And this is before most of the team has started. I mean, this is mid 2020, maybe early.

So a lot of it was us trying to separate out the specifics of what was important for socket SP3 or specifics for this particular AMD aspect versus what is it we generally want. So a lot of things are split up in those early RFDs in part because of that. We had something about what does PCIe hot plug look like? What are our goals and constraints?

So a lot of it was us trying to separate out the specifics of what was important for socket SP3 or specifics for this particular AMD aspect versus what is it we generally want. So a lot of things are split up in those early RFDs in part because of that. We had something about what does PCIe hot plug look like? What are our goals and constraints?

How do we split up responsibility between different subsystems? Just edit broad core strokes. What's even the role of power monitoring? When should we do it? When shouldn't we do it? All these things. So that gives us a lot of initial foundation there. And then from there, with Cosmo, a lot of these things that we have, we're not starting from a clean slate, per se. We have an existing system.

How do we split up responsibility between different subsystems? Just edit broad core strokes. What's even the role of power monitoring? When should we do it? When shouldn't we do it? All these things. So that gives us a lot of initial foundation there. And then from there, with Cosmo, a lot of these things that we have, we're not starting from a clean slate, per se. We have an existing system.

There's a lot of stuff we want to reuse between that. we have a large investment in hubris and tooling and different components. You know, we have vendors that we've worked with. So we're not trying to necessarily reinvent the whole wheel there. So, you know, not everything is like, not everything is starting from a clean shade again. So that kind of helps constrain it.

There's a lot of stuff we want to reuse between that. we have a large investment in hubris and tooling and different components. You know, we have vendors that we've worked with. So we're not trying to necessarily reinvent the whole wheel there. So, you know, not everything is like, not everything is starting from a clean shade again. So that kind of helps constrain it.

So in there, we kind of, in the Cosmo RFD, for example, you know, we've broken up that into a bunch of different areas that different folks helped collaborate on. Some of it was Adam and I collaborating on, what is the disk drive interface that we should use? There's U.2, E3S, E1S. There's E1L. There's three different variants of widths and thicknesses of E3S and even longer things.

So in there, we kind of, in the Cosmo RFD, for example, you know, we've broken up that into a bunch of different areas that different folks helped collaborate on. Some of it was Adam and I collaborating on, what is the disk drive interface that we should use? There's U.2, E3S, E1S. There's E1L. There's three different variants of widths and thicknesses of E3S and even longer things.