text
stringlengths
0
1.82k
**Erik St. Martin:** It's like Damian for Docker issues. \[laughter\]
**Jessie Frazelle:** Yeah... It's crazy.
**Erik St. Martin:** Do you guys keep statistics of how long it takes to turn around issues or pull requests? I'm interested to see whether some have lagged so long you just had to delete them.
**Jessie Frazelle:** Yeah, so issues and stuff - there's definitely stats on this, but I don't actually know the answer. But issues, it's like we don't really care about the oldest there, but with pull requests we'll have weekly maintainer meetings and we'll go through the oldest. Usually, the oldest is something where...
**Brian Ketelsen:** That's not too bad.
**Erik St. Martin:** Yeah, that's not as bad as I was expecting it to be. Because you've gotta figure that it grows faster than it goes down; you're either spending time managing other people's pull requests or writing your own code, and that's gotta be a hard debate, which thing you work on.
**Jessie Frazelle:** Yeah, it's a juggle. Because we used to - I don't know if they still do this, they probably don't... But we would try to have maintainer days, where like on Tuesday one week I was just closing issues that day, and then the rest of the week I got to write code. So almost everybody kind of had a day ...
When you're stuck in a maintainer day and the day before that you were just about to finish your thing, it sucks.
**Carlisia Thompson:** How's your workflow, Jessie, for accepting PRs or evaluating PRs? Do you download the PR and run it locally in run tests? Or is that automated? How does it work?
**Jessie Frazelle:** So normally I would just make sure that it has the first CI passing, which is checking that it's been signed, and all that stupid legal stuff. Then if it's actually green in the CI... Say it's just a small bug fix and they added a test case, I'll go in and check out their change, remove the fix and...
After the design review, we go through and do a full-on code review, but I would say most pull requests that come in, they're like a typo change or some small fix. The feature requests are what take the most time, but when they're done correctly it can be smoother.
**Erik St. Martin:** \[11:49\] Yeah, so I'm actually quite impressed by the pull request process for Docker when I went through that. There's a number of automated CI steps that it goes through. There's a document that it starts out, "Describe what the problem is, describe how you fixed it, give us a one-liner for what...
**Brian Ketelsen:** Who put all that together, Jessie?
**Jessie Frazelle:** The CI stuff, before I started at Docker, we used Travis and it only ran our unit tests, which considering that you've made a change to Docker, you probably know that most of our tests are integration tests, and they take a really long time. So we were testing the integration test by hand. Two peop...
**Erik St. Martin:** I still rock that T-shirt with the swords... "Compiling. Carry on."
**Jessie Frazelle:** \[laughs\] Totally. So we ended up switching to Drone, and Drone had some issues with Docker and Docker, because we need very specific things to test Docker, since we need Docker for Docker... Yeah, it's crazy.
**Erik St. Martin:** Docker inception.
**Jessie Frazelle:** And it also just totally messes with your server after. So we then switched to Jenkins. I kind of just switched it overnight, and at first a few people got mad, just because nobody likes change. And it didn't exactly work right away, but once we got things working, now it's all still Jenkins and th...
**Brian Ketelsen:** Did you hack the Gibson?
**Jessie Frazelle:** It would have been cool. \[laughter\]
**Erik St. Martin:** So talk to us a little bit about what you worked on for Docker, because Docker's a pretty big project. Now it's split up across I don't even know how many repos and subprojects, but what specifically did you enjoy working on?
**Jessie Frazelle:** Yeah, I think most of the engine team itself worked on more the container runtime stuff and design of the CLI. Then there was another whole team that handled all the distribution of tarballs. I liked more of that, and then also I ended up doing that whole thing with the CI, where I was like the CI ...
**Erik St. Martin:** I hope I have the name right... I think it was Yehuda Katz that said this, and he said something along the lines of the thing he fears the most about releasing stuff open source is having to maintain it. And it's almost the same thing - you build the CI thing out and it's awesome, but now you're th...
**Jessie Frazelle:** Yeah, and it became super stressful because the Windows servers that we had for some reason needed to be restarted every other day. So just the first ten minutes of my day were like restarting Windows servers, and I was like "This is such a waste..." And there was an entire team that did CI for the...
The entire CI once broke because of a stupid kernel bug, and then we ended up upgrading to a kernel with another bug. So I was basically like, "Computers just don't work. We should all give up now." But then we got over it.
**Brian Ketelsen:** I think we've all been there.
**Jessie Frazelle:** Yeah. \[laughs\]
**Erik St. Martin:** ...like, daily.
**Carlisia Thompson:** Daily, I was gonna say.
**Erik St. Martin:** \[16:01\] How can I love tech and hate tech so much at the same time?
**Jessie Frazelle:** It's terrible. \[laughs\]
**Brian Ketelsen:** I have a question for you. It's a little bit of a different topic, but you've been at Docker, you've been at Mesos, and now you're at Google. Many people say that Go is kind of the language of the cloud. You've seen pretty much the whole cloud now - what do you think about that proposition?
**Jessie Frazelle:** At Mesosphere they were writing a lot of C++ - that's what Mesos is written in - and they even had some cool networking stuff in Erlang, but other than that it's all Go, that's what I've seen. And I love Go, so obviously I'm biased, but I even made a couple pull requests to Go and I wanna make more...
**Brian Ketelsen:** What is it about Go that makes it better for cloud work?
**Jessie Frazelle:** Probably the fast compile time, because I honestly forgot when I was compiling Mesos how slow things used to be, and just with header files, and everything needs to compile again, and I was just sitting there twiddling my fingers, not knowing what to do with life. So that's definitely helpful, and ...
**Brian Ketelsen:** Yeah, the static binaries make a huge difference. I would agree with that, sure.
**Erik St. Martin:** Yeah, I think that's a big thing that attracted everybody to the language - being able to do static binaries, but still have a more dynamic feel to the language.
Every time I go back to C or C++ and have to wait... Like, "Oh, come on..." I think everybody should have to compile one just to keep us honest though, right? \[laughter\]
**Jessie Frazelle:** Yeah, because I was complaining about the slowness that came with upgrading from 1.4 to 1.5 Go and I was like, "What?! I'm a terrible person. Such a hypocrite. I should not have done that" \[laughs\] after seeing what C++ was like.
**Erik St. Martin:** Yeah, we've joked about the compile times. But now they're back down... I think they split the difference, I think they're less thanhalf way from where they were between 1.4 and 1.5, so we're getting closer... But if you go back and compile a C or C++ app and then go back to Go, you realize just ho...
**Jessie Frazelle:** It is amazing.
**Erik St. Martin:** I guess we should probably stop and talk about sponsors real quick. I think now is a good time, right everybody?
**Carlisia Thompson:** Yeah, let's do it.
**Jessie Frazelle:** Cool.
**Erik St. Martin:** So Linode is the first one, and we've mentioned that all of our new CMS architecture will be hosted on that. Ours and Changelog's, because we are a part of Changelog. So Adam and Jerod really love Linode, and everything's gonna be hosted there.
I think Brian was saying you have some experience with Linode, right Jessie?
**Jessie Frazelle:** Yeah. Since I set up our CI, we also needed a separate server for testing IPV 6, because it's hard to do in most cloud providers, but they had a really good setup, so we ended up using that, which was nice.
**Brian Ketelsen:** Oh, that's nice. Linode was one of the first VPS's as I stood up many years ago, probably 10 or 11 years ago now, and I really enjoyed using it for a long time.
**Jessie Frazelle:** Nice, yeah.
**Brian Ketelsen:** I understand one of the neatest things about their setup is that you've got a CLI tool that you can use to manage it; just get your API key and go to town managing your nodes directly from your terminal. I'm all about managing stuff from the terminal.