text stringlengths 0 1.49k |
|---|
• Code review and shipping code discussed |
• Shoutouts to contributors to libraries for sensors and Arduino projects |
• Easter pig project and barbecue data streaming mentioned |
**Erik St. Martin:** Alright everybody, welcome back for another episode of GoTime. Today's episode is number 44, and our sponsors for today are Toptal and DataDog. |
Today on the show we have myself, Erik St. Martin, Carlisia Pinto is also on the show - say hello, Carlisia... |
**Carlisia Thompson:** Hi, everybody. |
**Erik St. Martin:** And Brian Ketelsen... |
**Brian Ketelsen:** Hello! |
**Erik St. Martin:** And our special guest today probably needs very little introduction, but a member of the Go team, Brad Fitzpatrick. |
**Brad Fitzpatrick:** Hello! |
**Erik St. Martin:** Hi Brad, how are you doing? |
**Brad Fitzpatrick:** Pretty good. |
**Erik St. Martin:** So for anybody who may not be familiar with who you are, do you wanna give a little bit of background on who you are and the things you're working on? |
**Brad Fitzpatrick:** I've been working on Go for maybe 5-6 years now, and I kind of work on the open source-facing part of the public project, the standard library, I run the build system... I kind of touched a little bit of everything over the years. |
**Erik St. Martin:** And you're to thank for most of the HTTP stuff... |
**Brad Fitzpatrick:** Yeah, a lot of the standard library -- I did all the HTTP client and server, for both HTTP/1 and HTTP/2, and... |
**Brian Ketelsen:** DB SQL... |
**Brad Fitzpatrick:** Yeah, the database stuff, the exec child process stuff, some of JSON... Here and there, just cleaning up everywhere... Can't change too much nowadays, but before Go 1, things were much more fluid. |
**Brian Ketelsen:** Back in the good old days... |
**Brad Fitzpatrick:** Yeah. |
**Erik St. Martin:** So you mentioned one thing that is interesting... There seems to be a set of Go team members who work on internal problems, Go as it relates to projects inside Google that use Go, and then some team members that focus more on the external community level stuff. Is that true? |
**Brad Fitzpatrick:** Yeah, I mean... Well, back in the day there was just the first three or four people, and then maybe like eight or nine people, and everyone kind of did everything, including internal stuff and external stuff. But as Go has grown in popularity both outside and inside Google, we've kind of started t... |
Sometimes you'll see people make an appearance in the open source world with some miscellaneous bug fix or performance improvement, and that was probably their first foray into public, and they've been debugging something for weeks internally, so... |
We're trying to change that, so that Google-only contributors spend more time in the open source community if they kind of feel uncomfortable there... Because there's different tooling and different processes and stuff... But we're just kind of getting started on maybe doing that every three months or six months or som... |
**Brian Ketelsen:** I've noticed that you've pretty much become the public face of open source Go. Any issues that come across, you're the person who's triaging them; dashboards go down, builders go down - you're the person that everybody's talking to. It's interesting to see how that has shaken out over the years. Is ... |
**Brad Fitzpatrick:** It kind of happened... Then, at some point, Russ or Ian or a group of people just kind of officially decided it was so, and I said, "Okay, well it's already kind of de facto", so it was announced officially. That's kind of how everything in Go happens. You do something long enough and you become t... |
**Erik St. Martin:** Yeah, that creates that buzz factor issue though too, sometimes... |
**Brad Fitzpatrick:** Yeah, that's a current problem. I'm actually having my first child soon here, and I will be taking some paternity leave. That's a different type of buzz factor I guess, but I've been trying to ramp up some other people to help take over the builders and dashboards and stuff like that. |
**Brian Ketelsen:** That's the best news ever. |
**Brad Fitzpatrick:** Yeah, it'll be fun... Although I'm missing [GopherCon](https://www.gophercon.com/), but I guess that's a good reason. |
**Brian Ketelsen:** Yeah, we'll give you a pass for this one, it's okay. |
**Brad Fitzpatrick:** Okay. I just wish it was all livestream, so I could watch it from home. |
**Brian Ketelsen:** It was last year. |
**Brad Fitzpatrick:** Oh, was it? |
**Erik St. Martin:** Yeah, the main room - all the keynotes were livestreamed; the side sessions weren't livestreamed... But yeah, we'll still work out details and we'll probably livestream part of it, so we'll give you a pass. A wedding doesn't count, because a wedding you can reschedule... \[laughter\] But you can't ... |
**Brian Ketelsen:** You can schedule babies. |
**Carlisia Thompson:** You could have timed the baby. Brad... |
**Brad Fitzpatrick:** I know... But you know, I did time it such that it comes out right at the Go 1.9 release, so... \[laughter\] I don't know if that's good or bad, but at least during the 1.9 release freeze I won't have to worry so much about it. |
**Erik St. Martin:** So is the 1.9 release's codename gonna be the same as the baby's name? |
**Carlisia Thompson:** Yeah, it's like two births. |
**Brad Fitzpatrick:** I don't know, we haven't really had codenames for the other releases, so it'd be weird to start now. |
**Brian Ketelsen:** Well, you've gotta start a tradition somewhere. Everybody else does codenames for releases: Zesty Zephyrs and Xenial Xerces and whatever. I think we need some cool names in Go. That's what we're missing. |
**Brad Fitzpatrick:** File a proposal. We have a proposal process. |
**Brian Ketelsen:** Yeah, I'll file a proposal... We know what's gonna happen with that. |
**Erik St. Martin:** Delete! \[laughter\] |
**Carlisia Thompson:** Actually, it seems Brad does so much of the work of interacting with people... Why don't we talk a little bit about what the process is like for people to contribute...? There's a recent blog post by [Steve Francia](https://twitter.com/spf13), but I think it's good to discuss it on the air. By th... |
**Brad Fitzpatrick:** Well, actually we don't officially take pull requests yet - that's one thing I need to be working on sometime here. |
**Carlisia Thompson:** I don't know, what is the thing that I did called? I made a change... The CL. What does CL stand for? |
**Brad Fitzpatrick:** ChangeList. It's actually this [Perforce](https://en.wikipedia.org/wiki/Perforce) terminology from back when Google used to use Perforce. |
**Erik St. Martin:** I remember Perforce. |
**Brad Fitzpatrick:** Go is now on its fourth version control system, and I think Perforce was the first one. It was like Perforce, Subversion, then Mercurial and now Git. But throughout all these transitions, we keep updating our tools to feel like the original tool, so all the terminology is still from way back in th... |
**Carlisia Thompson:** Alright, but let's not change subjects... Can you please approve it? \[laughs\] Whatever its name is... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.