David Crespo

Yeah, I think, you know, But definitely a bunch of things we're trying to figure out is what is the content? How do we section it? I was going back and looking at the prototype we had for the RFD set at Joyent. And it's literally just like, OK, there's a title, and that's it.

Yeah, I think, you know, But definitely a bunch of things we're trying to figure out is what is the content? How do we section it? I was going back and looking at the prototype we had for the RFD set at Joyent. And it's literally just like, OK, there's a title, and that's it.

And I think sometimes that not even having like, not that there's too many more sections than what we have at Oxide, but I think having a little bit there

And I think sometimes that not even having like, not that there's too many more sections than what we have at Oxide, but I think having a little bit there

helps um and then i think the method of discussion it's also something that we're trying to iterate and figure out you know what's the right way to do it um yeah you know some of it was just kind of like ah there's an issue or you know some folks discuss in chat or sometimes we had an email thread and that worked okay ish um i don't know yeah i mean pros and cons there the github

helps um and then i think the method of discussion it's also something that we're trying to iterate and figure out you know what's the right way to do it um yeah you know some of it was just kind of like ah there's an issue or you know some folks discuss in chat or sometimes we had an email thread and that worked okay ish um i don't know yeah i mean pros and cons there the github

GitHub PR today is differently painful because of GitHub more so than anything else.

GitHub PR today is differently painful because of GitHub more so than anything else.

Yeah, and I think some of the other bits here, you know, locating everything in a repo makes it very easy to see what's changed over time. The discoverability was big, and then We ended up with Markdown initially mostly because, I don't know, it was the thing to do du jour. It was easy to see rendered.

Yeah, and I think some of the other bits here, you know, locating everything in a repo makes it very easy to see what's changed over time. The discoverability was big, and then We ended up with Markdown initially mostly because, I don't know, it was the thing to do du jour. It was easy to see rendered.

Trent had his Python Markdown 2, which we had used for a lot of docs and other things historically.

Trent had his Python Markdown 2, which we had used for a lot of docs and other things historically.

I mean, probably. Given how we're weird on everything else, right? Yeah, part of this evolution I think came from a few steps. I mean, once you're in the non-WhizzyWig world, so once you're not in a Word or Google Docs, then there's kind of two challenges. One, and

I mean, probably. Given how we're weird on everything else, right? Yeah, part of this evolution I think came from a few steps. I mean, once you're in the non-WhizzyWig world, so once you're not in a Word or Google Docs, then there's kind of two challenges. One, and

This may be my own fault, but it is very hard in the markdown days, particularly in 2012, 2015, to see a rendered markdown doc, per se, locally without pushing it somewhere up. And that, for me, was just my own mental foible of wanting to see, hey, does this render correctly before I push it?

This may be my own fault, but it is very hard in the markdown days, particularly in 2012, 2015, to see a rendered markdown doc, per se, locally without pushing it somewhere up. And that, for me, was just my own mental foible of wanting to see, hey, does this render correctly before I push it?

It's like tough, tough and fair. Uh, and then I think the other, the other thing that we kind of saw as we were getting down, um, And I think the first Joyent, so actually Alex Wilson, who wrote RFD1, was the first one to use ASCII doc in an RFD at Joyent. Oh, really? Yeah, he was the one who found it and pointed us towards it. And I want to say it was probably for RFD77 there.

It's like tough, tough and fair. Uh, and then I think the other, the other thing that we kind of saw as we were getting down, um, And I think the first Joyent, so actually Alex Wilson, who wrote RFD1, was the first one to use ASCII doc in an RFD at Joyent. Oh, really? Yeah, he was the one who found it and pointed us towards it. And I want to say it was probably for RFD77 there.

And once you kind of got to, you know, I think one of the Markdown strengths was, you know, it was very simple. Uh, one of Markdown's weaknesses is like, if you want to create a table, there's still probably like 20 different ways to create a table. And if you want a table of contents, like, you know, God forbid that, uh, you're, you're really on your own. And so the little bit of additional, um,

And once you kind of got to, you know, I think one of the Markdown strengths was, you know, it was very simple. Uh, one of Markdown's weaknesses is like, if you want to create a table, there's still probably like 20 different ways to create a table. And if you want a table of contents, like, you know, God forbid that, uh, you're, you're really on your own. And so the little bit of additional, um,