text
stringlengths
0
1.82k
**Carlisia Thompson:** But I think GitHub put a button there that does that automagically, if I'm not mistaken.
**Erik St. Martin:** I'm more of a command line junkie, but yeah, I can see how just being able to go to the website and click the button becomes super useful.
**Carlisia Thompson:** As far as Git goes, I don't trust any UI tool. I wanna see it on the command line. If it didn't happen there, I don't know if it happened, so I wanna see it.
**Cory LaNou:** Git for me is a Swiss army knife that has all these buttons on it, and when you press it, I stab myself every single time.
**Erik St. Martin:** The thing I tell people all the time is if you learn to use the reference log, you'll feel much safer with Git. Because you're like, "Oh, it doesn't matter. If I committed it, I can totally fix it."
**Carlisia Thompson:** But you said the magic words, "If you committed it." If you don't, it doesn't really matter. But it is amazing how many people don't even know that that exists, and it's a life changing thing.
**Erik St. Martin:** Yeah, if you have not played with the ref log, you should.
**Brian Ketelsen:** Git's really simple for me - you just delete the directory and clone again. \[laughter\]
**Erik St. Martin:** No, don't do that.
**Brian Ketelsen:** That's all you need to do: rm -rf <my repo> git clone <my repo> Fixed!
**Carlisia Thompson:** We'll edit that out.
\[laughter\]
**Erik St. Martin:** Yeah, yeah. Do not take Brian's advice there.
**Carlisia Thompson:** Not this one, people.
**Erik St. Martin:** So back to the open source contributions too, I wanted to point out another fact. I think that people not only should contribute, but go in and dig around the code, because I think people will find that their vision of the code for any big name project is far from the reality. They're gonna start d...
**Cory LaNou:** Yeah, I'm a big fan of Help Wanted. I just started a repo the other day on Go open source projects that have the actual issues labeled with Help Wanted. You can go on and find these issues very quickly, and figure out where they need help.
The more important thing for me on that one wasn't because I wanted to help all these open source projects - that actually wasn't my intention - it was because people were always asking me "How can I get started in Go?" and I'm like "Well, there's all these projects out there that need Help Wanted." We just need to get...
**Carlisia Thompson:** Yeah, I saw you started putting together a repo? Was that it? I forgot.
**Cory LaNou:** Yes, it was a repo.
**Carlisia Thompson:** We will include a link to that on the show notes for sure, so tell us more about that.
**Cory LaNou:** Yeah, basically it spawned off of a meetup that I was doing in Chicago, and I couldn't make it down there, and the host - we missed a month and we had to get back on track, and we didn't have time to really get speakers lined up. So it was like a week before we were gonna have it, and he was kind of a l...
**Erik St. Martin:** I think it's actually a really good idea, because when you're forced to solve a problem you have to dig around and you have to learn the codebase, which means you have to understand more Go, too. Then on top of that when you submit your pull request, you have other people reviewing your new Go code...
I think that it should be said too that skill level doesn't matter. Just getting in there, and even if your patch doesn't get accepted, you're going to learn a lot along the way.
**Carlisia Thompson:** Let me throw something at you guys, because you've all been doing Go forever, and I'm a newcomer totally. So I would go to InfluxDB source code, download it to my computer, and actually kudos to all of you because I was able to install and get it running on my machine just reading the documentati...
**Erik St. Martin:** I think that some people will be more natural at figuring it out, and I think it's just more a matter of domain knowledge. So you have understanding something from a technical perspective, and you also have the understanding of domain knowledge. If you know very little about, say InfluxDB, it's gon...
**Cory LaNou:** I don't think there's ever been a time that I've gone into source code, like the Go raft library - that's a pretty sophisticated piece of code that HashiCorp wrote. The first time I went in there I'm like "Oh, it's written in Go, I should be able to understand this", and I pretty much got in there and I...
**Erik St. Martin:** Become buddies with a project member, too. Get him all excited, buy him a beer. Say, "Talk to me!".
**Brian Ketelsen:** Definitely.
**Carlisia Thompson:** ...ping them on Slack all day long.
**Cory LaNou:** I get a ton of people that reach out to me on Slack for Influx randomly; I have no idea who these people are, and they're like "Hey, I'm working on this bug for you. Can you help me?" Like, "Sure, what do you need?"
**Carlisia Thompson:** Speaking of which, there is a reviews channel on GopherSlack which I just discovered recently. I don't know if all of you are aware. There is a lot of action in there, I wonder if people make good use...
**Erik St. Martin:** I actually didn't know that.
**Brian Ketelsen:** It's a very busy channel.
**Carlisia Thompson:** Yeah. I wonder if people make good use of it. If people get good feedback... I started keeping track of it.
**Erik St. Martin:** So this is just a channel somebody opened up for people to post pull requests and just get anybody who has some spare cycles to review for them?
**Carlisia Thompson:** Yeah, not even necessarily pull requests, just any code, just "Review this code."
**Erik St. Martin:** That's awesome. I didn't even see that yet.
**Carlisia Thompson:** Yeah, GopherSlack, full of surprises.
**Erik St. Martin:** So Cory, you said you have a whole bunch of free time still, right?
**Cory LaNou:** Yes, absolutely.
**Erik St. Martin:** Review all the things. \[laughter\]
**Cory LaNou:** I'll start doing that at midnight every night.
**Brian Ketelsen:** We'll expect to see you in the reviews channel shortly...
**Cory LaNou:** I just joined. \[laughter\]
**Brian Ketelsen:** ...fixing all the code. No, actually it's a great channel, and I've spent quite a bit of time in there, because I always want to make sure I'm doing things the right way, so it's a good place to be.
**Erik St. Martin:** And for anybody who's not aware, we're referring to the Gopher's Slack, which is gophers.slack.com. There's a Heroku app for doing the invite we'll link to in the show notes. So that's what we're referring to. I think we assume because there's 6,000 people in there that everybody knows about the Sl...
**Cory LaNou:*** It's interesting you make the comment about assuming, it's something I've been doing in most of the cities I'm in, as I maintain a document specific to the city, which provides all of the online resources like Slack and Go forums and all that kind of stuff, and it also provides information on everythin...
**Erik St. Martin:** Brian and I, it was a month after GopherCon 2015, it was basically a big name company emailed us about the conference and wanting to sponsor, and we were like "It's over." They didn't even know... We had made the assumption that everybody kind of in the Go world knew about the conference. We feel c...
**Brian Ketelsen:** Yeah, how could you not know about the conference? It's all we talked about on Twitter. Come on! \[laughter\]
**Erik St. Martin:** All you had to do was follow one of us on Twitter.