 Okay, so I actually have a lightning talk as well, but I didn't want to be a dick and cut somebody off, so. Oh, well. Okay, so I actually kind of realized I'm a little bit sick today, which you may have noticed in my energy level and nasally voice. So I apologize that I don't think I actually introduced myself at the beginning of the day. So I'm, my name is Scotcha Cohn and I work at GitHub and I've been kind of helping put this thing together. But the lightning talk that I'd like to give today is on a project of mine, that's sort of a really long-lived project, which is the Git SEM website and some of the stuff that comes out of that. So I maintain the Git SEM.com website. Right now it is basically a community portal, so it tries to take people that are new to Git and teach them how to get started in it as easily as possible. So I know that a lot of you are from companies that are trying to get adopted or some of you are trainers or have done work trying to teach people Git that you work with. And so I really appreciate any feedback that you have. If you guys say this resource sucks or this thing is not good or this is the problems that users that I know have had trying to adopt Git or use it successfully, I'd really appreciate that feedback in trying to make this resource better for users. If you're core developers, I know there are a number of them in the room right now. This is the website that we have on Git SEM.com right now. Git SEM.com is not a developer community portal. It's not really useful for developers of Git. It's useful for developers who use Git, right? And so the entire community list is this. So if you're somebody who's new to Git and wants to get involved in Git, all you have is this one page and it's not particularly great. So I'd like to have... If anybody has ideas of tools that would help people on board as developers of Git, new developers to the Git project, I'd love to hear that. I'd love to sort of hack on that tomorrow a little bit. So if you have ideas or something, please let me know. And then the next thing is for sort of users of Git, which is I also wrote this book, the Pro-Git book that was published by A-Press and it's Creative Commons License, then it is... If you click on the documentation book link, this is a book you can read online and search through and all that stuff. And the reason we were able to do that is because it's Creative Commons License and because I own it so I can basically do whatever the hell I want with it. So they've been pushing me to... They've been asking me to write a second edition of this and I really don't want to because it takes a lot of time and it's really kind of shitty, but at the same time they make you... I don't know if anybody wants to commiserate over how difficult it is to write a book in Microsoft Word. Let me know because it is basically the worst process on the planet. It literally is... I was writing a book on version control and like emailing chapter1.doc to people and then having them edit it and send it back and I was like, this is so un-made. This is awful. So anyways, it's in Markdown. The entire book is in Markdown. It's on GitHub, pro-git slash pro-git, if nobody's seen this. There's like 100 translations. Some of them are partial, some of them are relatively full. But I do want to start doing a second edition because a lot of it is out of date and so I've had a couple people tell me that they like the book, even here today, and what I would really like is that comma-butt. So if you have read the book or you know people who have read the book and you have a comma-butt, like a long awkward pause, but the one thing is, I want to hear those things because I'd like to make the second edition sort of slowly, in the community, so I want to be publishing it a piece at a time onto the website and get feedback from people and say, you know, here are the weaknesses that the book has now. Here's how new users could get up to speed better or learn the system better, I think. And I could publish it slowly over time and then at the end give it to A-Press and say, okay, it's fine, you can publish this now. As opposed to going through the process that they make me do. So that's what I'd like to do. So you don't have to help me write it all, you know, that's not necessary. But if you go to this repo and you add an issue and say, here are some things that I've seen of people that have read this book or that I've sent to this book where they still have problems with these sections, I'd really appreciate it because I would like this to be a really good resource for people moving forward and so that you don't necessarily have to teach people if your colleague comes up to you and says, you're really good to get, right, how do you do this? You can help them once or you can, like, you know, sort of teach them to fish by sending them to this website, right? If you personally tell them how to do that, they're just going to keep coming back to you all the time. So I want to make it a really nice way to sort of send somebody off. So, yeah, that's it. Please help me write the second edition of this book so that, you know, it's easier to teach people Git. And then I just want to close on sort of a sense, we were talking about GitTF, sort of the hidden, sort of a hidden stupid trick of GitHub, which you may or may not know about. Does anybody know about GitHub Subversion Bridge? Like a couple of people. So you can actually, I'll type this out, you can actually, every single GitHub is the world's largest Subversion repository. So I don't know if you knew that. But you can actually say, SVN checkout, hold on. Actually, any Git repository, you can just do Subversion checkout and it will check out that repository via Subversion. So every single repository in GitHub this works for. So if you're in a company where you're on Subversion now and you want to move to, you know, you want to move stuff to GitHub and people are still on Subversion and that's a blocker of some sort, this works, you can actually also commit to this and push over it. It's sort of an interesting story. If anybody ever wants to talk at a deeply nerdy level about sort of the Subversion HTTP protocol and how we made this work, it's deeply nerdy and sort of stupid, but incredibly fun to me. So that's it. That's all the lightning talk. So now, thank you very much. Are there any questions on that stuff? Oh, thank you. Are there any questions on, yes? How close are the links to... Well, that's... Hold on, let me get some water real fast. Sorry, I literally couldn't speak. Okay, so that's problematic just because I don't speak to the people that translate the core documentation is what you're talking about. I don't really have... A, I'm not a translator and B, I don't speak German and C, I don't speak the other 20 languages that the book's translated into. So, like, what I've been trying to do is sort of choose somebody that seems like they're... that does a lot of work translating it and then merge that in and then let that sub-community sort of, you know, figure out who's better at stuff. For my part, whatever the first pull request that comes in, I merge it because there's no way for me to double-check it and there's not enough people involved to... and it's a lot of work to go through and translate an entire book, right? So, you know, especially if it's like Chinese or Japanese or something like that, I have absolutely no concept if this is working well or not when I merge it in. And so I just kind of have to rely on the community to figure out what it is. I may, at some point, get a little bit more serious and hire some... like, have GitHub hire some translators to try to make some of this stuff better because it's useful to the entire community and it's useful to GitHub for people to be able to learn, get easier. And so I might consider doing that for the second edition as having some professional translators, but 30 is probably a little bit overkill. So, I mean, I would love to speak to more people about that, but like, every time, you know, at the end of the day it's like, I have no concept of really what your argument was between, like, germish and, I don't know, is that what you said? And, like, you know, strict technical German or something, like, there's no way for me to fix that. So, I mean, if you know people that are good at that and are interested, then that'd be great, but like, it's so small of a community it's hard to find those people. Yeah. Okay. Oh, yeah. Okay, yeah, I'd love to. I would love to. That'd be great. I would love to. I mean, it's been, it depends on the translation. Some of them are hugely popular, like in China, for example, the Chinese translation is unbelievably popular. It's a huge amount of the traffic to the website and the Russian one as well. And then a lot of them are not, like, German is actually really low, possibly because it's a fairly, like, it's a weird translation in that they kept a lot of the English German underneath it. So, like, you go through and they literally have, like, blocks of both. And that's how they wanted to do it. That's how that community wanted to do it. And so, I just kind of accepted it. I kind of want to fix it. But also because, you know, most technical Germans that I've, I mean, now I'm going into most technical Germans that I've met speak English as well. And so, a lot of them prefer the English documentation when they're reading this. I mean, it just depends on, you know, the actual, like, thing that you have to do in college in order to be successful in that field. So, I don't know. But I would love to talk to you about that. Okay. One more question. Yes. Regarding the subversion, do you have support for excellence then? Yeah. Well, I mean, yeah. Because, I mean, it's a subversion client. And so, it pulls down the references. If you have the references in, well, how do you do that? I'm trying to remember how it's stored, because I believe it's stored in a, like, .svn file, right? So, if you commit that into the repository and then pull it down, I mean, it's not going to work for Git people cloning that. Yeah. But the SVN externals, I know people that have a subversion project that have SVN externals that are Git repositories on GitHub. So, like, PHP libraries, this is very common, where libraries will move over to GitHub. It's one of the reasons we did this, is so libraries can move over to GitHub, where people using subversion for their main project can clone it and it has a GitHub URL in it, and it still does a subversion check out of that, right? So, it's very popular in sort of the PHP, like, library community. Yes, for doing, I'm trying to remember some of the names of the projects there, but anyways. But, yeah, I mean, any of the server-side stuff, it just speaks to the SVN version DAV protocol, so it covers most of those cases. Anybody else? Okay. So, what time is it?