Augustus Mayo

Yeah, that does actually talk to GitHub directly at the moment. Oh, wow. Yep. Hopefully not for long. Our goal was to model it in the front end, see how people liked it. And then once we have a good idea, then we port it back down to the back end.

Yeah, that does actually talk to GitHub directly at the moment. Oh, wow. Yep. Hopefully not for long. Our goal was to model it in the front end, see how people liked it. And then once we have a good idea, then we port it back down to the back end.

One of the complicated bits, though, is we have this back end processing bit so that we don't have to go to GitHub to pull data, like all the static content from the RFDs and the images and all that. The problem, though, is that database we want to talk about sort of revisions of RFDs. And this is something we did recently. But we currently only expose the currently latest version of RFD.

One of the complicated bits, though, is we have this back end processing bit so that we don't have to go to GitHub to pull data, like all the static content from the RFDs and the images and all that. The problem, though, is that database we want to talk about sort of revisions of RFDs. And this is something we did recently. But we currently only expose the currently latest version of RFD.

But we have a database of every commit processed. So eventually, you could go back in time on the RFD site. And then the idea is, how do you tie comments into revisions? And what's that mean? Comments on a specific revision, how do you then pull them all together? So in the process, but yeah, as Chris was saying, we're building GitHub.

But we have a database of every commit processed. So eventually, you could go back in time on the RFD site. And then the idea is, how do you tie comments into revisions? And what's that mean? Comments on a specific revision, how do you then pull them all together? So in the process, but yeah, as Chris was saying, we're building GitHub.

That is absolutely correct. So if you don't know, when you have a private repo and you add an outside collaborator, you start paying for it. So you start racking up pretty big GitHub bills around that, as well as it's just a hard list to maintain and understanding who still wants to be on that list. Yeah. And also, it meant that we have to give full access to every RFD to everybody.

That is absolutely correct. So if you don't know, when you have a private repo and you add an outside collaborator, you start paying for it. So you start racking up pretty big GitHub bills around that, as well as it's just a hard list to maintain and understanding who still wants to be on that list. Yeah. And also, it meant that we have to give full access to every RFD to everybody.

We don't have any way to curate that. And we had some workarounds in place, but we have some static config files that list a handful of RFDs and this subset of people get them. We had no real good permissioning system around it. And that was one of the main reasons to rewrite that database and back-end processing was... we needed to model RFD access around actual permission sets.

We don't have any way to curate that. And we had some workarounds in place, but we have some static config files that list a handful of RFDs and this subset of people get them. We had no real good permissioning system around it. And that was one of the main reasons to rewrite that database and back-end processing was... we needed to model RFD access around actual permission sets.

So being able to grant things all the way down to you have access to a specific RFD, or maybe even have access to a specific RFD and the discussion for that RFD within the RFD site itself.

So being able to grant things all the way down to you have access to a specific RFD, or maybe even have access to a specific RFD and the discussion for that RFD within the RFD site itself.

So we had this weird... I'd have to look at the actual date. We had a weird workaround prior to the permissions where you could technically mark things as public that we did for one or two. But it wasn't until we actually launched the new RFD API, which was, I don't know, sometime this past year, to actually flag them.

So we had this weird... I'd have to look at the actual date. We had a weird workaround prior to the permissions where you could technically mark things as public that we did for one or two. But it wasn't until we actually launched the new RFD API, which was, I don't know, sometime this past year, to actually flag them.

Yeah, that's a good thing to point out. There's a difference between public, as in you could sign in and see stuff, versus now you can actually just go to the URL and you can actually just search the things that are public, as in they're actually public, not this fake behind a log in public.

Yeah, that's a good thing to point out. There's a difference between public, as in you could sign in and see stuff, versus now you can actually just go to the URL and you can actually just search the things that are public, as in they're actually public, not this fake behind a log in public.

Yeah, so I know it was less than a year because it was at last time when we all met up at the office. That's when I demoed the barely working API that was just tied together with string.

Yeah, so I know it was less than a year because it was at last time when we all met up at the office. That's when I demoed the barely working API that was just tied together with string.

And honestly, so all of this permissions and group stuff is, so the RFD site was the first test of this, but that's actually now, that's been factored out of the RFD site, out of the RFD API, and now sort of powers a lot of our internal application permissions. And now the RFD API gets updates now from the stuff we're doing throughout the rest of the company.

And honestly, so all of this permissions and group stuff is, so the RFD site was the first test of this, but that's actually now, that's been factored out of the RFD site, out of the RFD API, and now sort of powers a lot of our internal application permissions. And now the RFD API gets updates now from the stuff we're doing throughout the rest of the company.