text stringlengths 0 1.62k |
|---|
[2600.90 --> 2605.08] there andrew so let's take a break we'll be right back and we'll we'll go through that |
[2605.08 --> 2612.82] over 400 000 developers have deployed to digital zones cloud digital ocean is a simple cloud hosting |
[2612.82 --> 2618.84] provider built for developers in 55 seconds that's all the time it takes you'll have a cloud server |
[2618.84 --> 2624.12] with forward access and it just doesn't get any easier than that pricing plans are super inexpensive |
[2624.12 --> 2630.78] just five bucks a month for half a gram 20 gigs of ssd drive space one cpu core and one terabyte of |
[2630.78 --> 2636.54] transfer all digital ocean servers run on ssds that means they're blazing fast they have tier one |
[2636.54 --> 2641.98] bandwidth support and come with private networking use our special link to get a ten dollar hosting |
[2641.98 --> 2647.30] credit when you sign up head to the changelog.com slash digital ocean to get started and now back to |
[2647.30 --> 2654.52] the show all right we're back uh so andrew i think it was a hot topic for you to kind of cover anyways |
[2654.52 --> 2659.74] which was the transition to get i know it made headlines um well it made it made hacking news |
[2659.74 --> 2666.30] that's well i mean what are headlines right it's good stuff you know it was in your talk so that's |
[2666.30 --> 2671.12] a headline yeah i mean in retrospect i was excited to hear this too i think everybody else was but it |
[2671.12 --> 2676.38] also you know in the wake of that you know how long has it been since the transition to get |
[2676.38 --> 2684.74] oh well a few months i guess it was december so a couple of months and so then the next question |
[2684.74 --> 2690.38] that came on the minds of those who follow go and obviously follow google code was like was that |
[2690.38 --> 2696.84] did you all know about google code or is that just by happenstance oh no like of course of course we |
[2696.84 --> 2704.98] knew um as a team because you know they're gonna tell like their biggest clients about it in advance |
[2704.98 --> 2714.94] but like in a way um our transition to get help was was kind of part of their preparing um this |
[2714.94 --> 2720.94] automated migration tool um that they've now given everyone access to so you know that so if you don't |
[2720.94 --> 2725.98] know they shut down google code and now there's this one click tool for um migrating your project |
[2725.98 --> 2731.04] from google code to github which you know it's pretty nice it works pretty well that's awesome yeah yeah |
[2731.04 --> 2736.76] and and the team were really adamant that they didn't want to announce the deprecation of google |
[2736.76 --> 2743.14] code until they had the plan totally worked out they had a tool that worked you know that they were |
[2743.14 --> 2751.56] able to make the the process as painless as possible and so we wanted to make the jump to coincide with |
[2751.56 --> 2759.36] the very beginning of our development cycle so our our release was for the first of december or the start of |
[2759.36 --> 2766.58] december and um we really wanted to make the cutover directly after that and so yeah we we did make the |
[2766.58 --> 2773.12] transition sort of motivated by the impending shutdown of google code but really i think all the reasons |
[2773.12 --> 2777.40] that we gave at the time were genuine like there are a lot of good things about making the switch to |
[2777.40 --> 2783.44] get and github and garrett uh but yeah if if it wasn't going if google wasn't going away maybe we |
[2783.44 --> 2786.92] wouldn't have done it i mean it was a tremendous amount of work and you know nobody wants to do |
[2786.92 --> 2791.20] busy work that's what i'm curious though because you got some pros and cons in your list here that |
[2791.20 --> 2795.14] you talked about in your talk but as i was listening i'm like there's something deeper into that story |
[2795.14 --> 2799.60] there and obviously we know now that google code is sunsetted so yeah there had to have been some |
[2799.60 --> 2804.90] reason there so you kind of throw a nugget in there of whether or not you may or may not have |
[2804.90 --> 2811.06] transitioned if google code didn't move away oh well it's you know it's just that you know i spent like |
[2811.06 --> 2817.88] two months of my life dealing with this problem of trying to seamlessly migrate all of our stuff |
[2817.88 --> 2822.50] from one service to another and it's not something that i would have chosen to do |
[2822.50 --> 2829.70] like if i had an option not to torture right well it's i mean it's just it's just work that i would |
[2829.70 --> 2835.32] that i could have not done and right i like i don't i feel like we're in a we're definitely in a |
[2835.32 --> 2841.84] better place now so you know i don't really feel bad about it um and i you know i respect the reasons |
[2841.84 --> 2847.58] for google wanting to shut down google code i can totally understand that as well i think you know |
[2847.58 --> 2858.22] like like chrome was um or even wave i guess was like a reason to try and shake up like you know the |
[2858.22 --> 2863.84] world of web browsers or the world of like online collaboration i think google code was really you know |
[2863.84 --> 2870.02] at the time if you remember like source forge was the thing yes yeah um and source forge was terrible |
[2870.02 --> 2876.66] you know so bad and google code was like just this breath of fresh air and it made it i think it made a |
[2876.66 --> 2882.86] lot of people realize oh hey you know we can build better like open source code hosting sites and that |
[2882.86 --> 2888.94] paved the way for like github and bitbucket and other services of that nature and so you know it kind of |
[2888.94 --> 2894.46] it served its purpose and you know it's it's obviously no secret now that it's it's not the |
[2894.46 --> 2900.94] place to be for open source projects now you know github seems to be that place now and that's fine you |
[2900.94 --> 2906.14] know we don't we don't feel bad about it that's for us it's mission accomplished there's something that |
[2906.14 --> 2910.66] people think is better they should be using that when google code came along that wasn't the case |
[2910.66 --> 2917.22] well this transition for you guys wasn't uh it was a lot of your life but it's not a big deal for |
[2917.22 --> 2923.70] your it is a big deal sorry reverse uh analogy there but it's a big deal for your contributors |
[2923.70 --> 2929.58] so those who actually contribute back to go or fork it and try to push pull requests we'll get into that |
[2929.58 --> 2935.48] in a bit but um but it's not so much important for go users so nothing's changing with go it's just a |
[2935.48 --> 2940.98] matter of yeah how you actually track versioning yeah yeah it's purely our projects development |
[2940.98 --> 2945.76] process how you do things yeah and the and the you know the only really like end user facing thing is |
[2945.76 --> 2952.10] they use the github issue tracker now rather than the google code issue tracker and that actually is |
[2952.10 --> 2956.70] generally better for our users because most users are more accustomed to using github's issue |
[2956.70 --> 2963.52] tracking system something you had said um in your talk was that it was a steep learning curve for |
[2963.52 --> 2970.04] for coming from mercurial to git and uh you know facebook back i think about a year and a half ago |
[2970.04 --> 2975.64] so i think almost last time you're on the show uh they had made a choice to move uh or choice of |
[2975.64 --> 2982.76] mercurial or git and they chose mercurial for speed reasons but you chose git do you think it's mainly for |
[2982.76 --> 2988.56] because of google code obviously but then also because of github in the community or is it git itself that |
[2988.56 --> 2996.90] attracted you i wouldn't say i'm particularly attracted to git nor am i particularly attracted |
[2996.90 --> 3004.34] to mercurial the main reason we switched to git is that the code review system garrett is built on git |
[3004.34 --> 3014.08] and garrett that um is partially maintained by people at google and there is you know a team at google that |
[3014.08 --> 3020.40] supports garrett instances for google is to use like so they use it on android extensively and you |
[3020.40 --> 3025.18] know if if it's developing infrastructure that is supporting android we know it's not going to go away |
[3025.18 --> 3030.76] like our code review system readfeld that we were using with mercurial um we were the we were basically |
[3030.76 --> 3035.62] the last people maintaining the instance that we were using it used to be used by a lot of people |
[3035.62 --> 3041.80] and so and we didn't really want to be in that position anymore we wanted to be using something that |
[3041.80 --> 3048.40] was well supported by um a team of people working full-time on making sure it works and so the garrett |
[3048.40 --> 3053.22] team were already doing that for the android people and so it just seemed like a natural choice to to go |
[3053.22 --> 3058.34] with that and there's a lot to like about garrett it has its rough edges but it's definitely |
[3058.34 --> 3064.70] a superior tool to what we were using before and so it was really garrett that motivated the choice to |
[3064.70 --> 3070.74] switch to git and then once we decided to switch to git um github seemed like the obvious choice for |
[3070.74 --> 3077.02] hosting our issues mostly it's mostly github is mostly just used for hosting issues |
[3077.02 --> 3084.28] what uh what role does garrett play in this process of building go and maintaining go well it's out it's |
[3084.28 --> 3090.10] the code review system sorry if i wasn't clear about that so um every single change that goes into go |
[3090.10 --> 3099.70] is reviewed and garrett is the system that web a web-based code review system that we use to |
[3099.70 --> 3108.42] look at the diffs and um leave comments uh upload new revisions so they're like pull requests but the |
[3108.42 --> 3118.80] workflow is a lot more focused on doing detailed code review um you know i find that you know github's |
[3118.80 --> 3125.48] pull requests are not very well suited to paying attention to all of the details you know i find |
[3125.48 --> 3131.00] it very hard to um to sort of keep track of different revisions of a change so you know as |
[3131.00 --> 3135.42] you're working on something that's coming in you know you'll make changes based on reviewer feedback |
[3135.42 --> 3141.00] and github makes it very hard to sort of see like what change from between one revision and the next |
[3141.00 --> 3146.96] it also you know forces you to do things like look at all of the files that have been changed in one |
[3146.96 --> 3154.56] big fell swoop and actually probably the most crucial thing that that i like about garrett and |
[3154.56 --> 3159.64] the other code review tools that i've been using in the past is that when you're reviewing something |
[3159.64 --> 3167.92] you make a series of comments on all the code like on lines and so on and then when you're you've you've |
[3167.92 --> 3174.16] done the review you then send all those comments as one big atomic thing and it comes as one mail |
[3174.16 --> 3179.68] message and then the the the author of the code responds to those messages whereas on github |
[3179.68 --> 3188.32] i start commenting on the change and the the author of the code is already receiving my comments |
[3188.32 --> 3195.38] by email like and so if i get halfway through the code and i'm saying like oh why did you do this here |
[3195.38 --> 3201.46] like this is confusing and then i get to like the next file and it's like oh i totally understand |
[3201.46 --> 3206.90] why you're doing this now and like in garrett i could go and delete those old comments or edit them |
[3206.90 --> 3214.44] but in github i suddenly have to like send more comments to the author and say oh oh oh ignore my |
[3214.44 --> 3219.60] ignore my other comments you're like i didn't mean that i understand now meanwhile they're giving you a |
[3219.60 --> 3224.06] deep dive and they're wasting their time commenting back like no i've fixed that down here and you're both |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.