6 ms·
The current (and pretty much only, ever, despite Linus having been the creator) maintainer of git is a google employee [1], in case anyone else was wondering.
by oneeyedpigeon 8y ago
The current (and pretty much only, ever, despite Linus having been the creator) maintainer of git is a google employee [1], in case anyone else was wondering.
[1] https://en.m.wikipedia.org/wiki/Junio_Hamano https://en.m.wikipedia.org/wiki/Junio_Hamano
- Retroity 8y agoNon-Mobile link for those on desktop: https://en.wikipedia.org/wiki/Junio_Hamano https://en.wikipedia.org/wiki/Junio_Hamano
- chrisseldo 8y ago>"Linus Torvalds said in 2012 that one of his own biggest successes was recognizing how good a developer Hamano was on Git, and trusting him to maintain it."
- vga805 8y agowow! what an accolade
- Dragonai 8y agoSeconded. I can only imagine how good Junio must be to have earned that kind of praise and trust.
- kumarharsh 8y agoI came across this email from Linus announcing the handover: https://lwn.net/Articles/145123/ https://lwn.net/Articles/145123/ It's interesting how the first ever git project itself was looking for new maintainer almost as soon as it was created.
- ojosilva 8y agoAlright, I was wondering why this was published on the Google Opensource website. I had no idea. Yet, the Git project itself has not been published under their umbrella. https://opensource.google.com/projects/list/featured https://opensource.google.com/projects/list/featured
- avar 8y agoOne of the places it's hosted at is https://kernel.googlesource.com/pub/scm/git/git https://kernel.googlesource.com/pub/scm/git/git See the list of URLs at https://public-inbox.org/git/xmqqindt6g1r.fsf@gitster.mtv.corp.google.com/ https://public-inbox.org/git/xmqqindt6g1r.fsf@gitster.mtv.co...
- willnorris 8y agoWe currently only list project that are or were primarily developed by Google. We decided to include projects that started at Google and were since donated to foundations, such as Kubernetes. But we aren't yet including projects where we are just heavy contributors, but they're not "Google projects". That includes Linux, git, LLVM, and a host of others. We do want to recognize them in our project directory, but want to make sure that they are distinguished from Google projects so that we're not implying something that is accurate.
- trumped 8y agoDoes he do it as a Google employee or on his own time? If he does it on his own time, why does it matter that he works at Google? and If he does it as a Google employee, when are the ads coming? edit: 3 replies, 5 down-votes and no answer to the main question...
- vesrah 8y agoIt is mentioned because this announcement is hosted on Googleblog.
- castis 8y agoMost likely it was noted because several of us probably immediately wondered why google would have taken it upon themselves to release a new version of something they weren't the maintainer of.
- apple4ever 8y agoMy first thought was “Ugh, Google forked git and now we’ll have two competing protocols” So its good to know why this was posted on Google’s site.
- brown9-2 8y agoGoogle has as much incentive as anyone else to introduce a faster wire protocol. The article mentions the Chrome project, and don’t forget that Google Cloud has a git-repo-hosting product.
- sevensor 8y agoThat's true, and while we all get to enjoy the new protocol, it seems like its primary beneficiary will be big organizations that have gigantic repos with massive numbers of refs in them. Furthermore, there's a clear orientation towards specialization -- putting that giant repo on a central server. Google clearly stands to benefit more from this work than those of us who use git as a distributed version control system. Who pays the piper calls the tune.
- AdmiralAsshat 8y agoThanks, that really helps. As an open-source advocate, my first thought was, "Why the hell is Google releasing a version of a protocol that Linus Torvalds wrote?" Without that context, it would be like Google throwing up an announcement, "Introducing Google's Linux Kernel 5.0!"
- fiatjaf 8y agoThat may seen odd, but it could happen in a open-source world: multiple parties releasing different versions of the same piece of software and calling it the same.
- loeg 8y agoOne fun example of this is the so-called RPM "5" fork[0], which is basically dead and almost entirely unused[1]. The result is the main RPM everyone uses will probably stay at version 4.x forever. [0]: http://rpm5.org/ http://rpm5.org/ [1]: https://en.wikipedia.org/wiki/Rpm_(software)#RPM_v5 https://en.wikipedia.org/wiki/Rpm_(software)#RPM_v5
- nkkollaw 8y agoThey could skip a version like PHP did. Among other reasons, since books and articles about PHP 6 had already been written long before PHP 5+1 came out, they went with 7.
- loeg 8y agoSure, they could. I don't think they've felt the need to. RPM tends to change slowly and conservatively.
- AdmiralAsshat 8y agoIsn't it customary to at least rename the fork?
- 8y ago
- biohax2015 8y agoFun fact: if you google “git blame” it returns his wikipedia entry.