On Wed, Jul 30, 2008 at 4:48 PM, Wincent Colaiuta <win@xxxxxxxxxxx> wrote: > El 30/7/2008, a las 21:32, Junio C Hamano escribió: > >> That's one valid approach. I or you might have taken a different avenue, >> but after all, it's his book, not mine, not yours, nor git list's book. > > Funnily enough, he chose to title it the "Git Community Book". Hard to match > Scott's enthusiasm; this is the second major initiative we've seen from him > in the last few days (the other being git-scm.com itself) which to the > casual onlooker might look like the "official" Git homepage and > documentation, but in both cases development occurred behind the scenes and > the list was only notified after the fact. Better late than never I suppose. Not sure what else I could have done - I announced that I was starting a documentation project like this about a week ago on this list, then I started the book 3 days ago (http://github.com/schacon/gitscm/commits/book) and announced it here for initial review yesterday. I haven't told very many people about it yet and I haven't linked to it from git-scm.com yet either. It's been open source from the first minute on GitHub, and the link to the source was on the website I posted here. Same for the git-scm site - I started it on the 23rd and emailed Pasky about it the next day, and the day after that he began submitting patches to me for it and I announced it on this list. Am I missing something here? Do you think I've been working on these secretly for months, or something? If there is a better communication workflow, I would be happy to do so. I appreciate that you notice my enthusiasm, though. :) Scott >> We originally hoped (well, at least I did) that Scott's effort on his book >> might help us in improving the User Manual as well, but the approach seems >> to make it unlikely. But that is nothing to hold against him --- he is >> doing his own thing in a way he feels is the best, and that's perfectly >> fine. We lost nothing, perhaps except for a chance to cooperate a bit >> better and to widen the community. > > Even though there might not be an automated way to get changes back from the > fork, if there are clear improvements made then there is at least no legal > obstacle to incorporating them back in, the only obstacle would be time and > willingness to do so manually. > >> > Cheers, > Wincent > > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
