On Thu, 2008-08-14 at 04:57 +0200, Jakub Narebski wrote: > 1. GitTorrent > > Student: Joshua Roys > Mentor: Sam Vilain > > If I remember correctly at midterm it was deemed to be somewhat late; > metainfo was done, tracker was in works, some core infrastructure > and beginnings of peer to peer: > http://thread.gmane.org/gmane.comp.version-control.git.gittorrent/1 > > Unfortunately this project, even that is as much tied with git as > StGIT, > or egit/jgit, or git-gui or gitk, all of which use git mailing list > for > discussion and patches, choose to have its own separate mailing list; > moreover I think most of discussion was kept private. > > Status: I have no idea how close GitTorrent is to completion (where > by > completion I mean ready, tested and benchmarked code running e.g. on > kernel.org). I'm not sure if it is meant to be incorporated in git, > even in contrib, or remain separate like StGIT, TopGit or jgit. The scope outlined in the GitTorrent proposal was a little bit more of a research project; being ready for production use on kernel.org or having code ready to merge to git was not directly a deliverable. The approved idea at the outset of *this* project was to try out the RFC protocol design as it stands, iron out the weaknesses and see how it performs. As it was pointed out along the way, there are other simpler designs possible, but I tried to explain how the fully denormalized design of the current RFC gives it more legs compared to other approaches. ie the goal was to prove the proposed network design, and test it and show it to be as resource efficient as the more pragmatic designs proposed by people like Johannes (or, indeed, earlier versions from Jonas which were much closer to bittorrent in design). I was certainly hoping that at or shortly after the end it would at that point also be good enough to be useful for production sites, even kernel.org sized (perhaps requiring the odd piece rewritten in C). We just need to crawl before we can walk, so to speak. I think saying "we're on track to prove the protocol" might be a little of an exaggeration at this point. But we have got a test script that is performing a replication between two test directories, transmitting data over sockets using GTP. Once Joshua has wrapped up this work to make it "less hackish" to drive ;) then we can review the implementation and sign off on completion of what was technically set out to complete. At that point the design becomes open to suggestions from the floor again. Anyway, that's the current status at this time. Thanks for the prod to update, Jakub. Come the actual completion date of the program, there will be complete news. Cheers, Sam. --- and now the rant: Please bear in mind that some of the "why Didn't You Just..." type comments are really "20/20 hindsight" now. And please, comments about what was made public and what not are also not useful. The initial design decisions between Jonas and myself are mostly in the RFC in comments and in history from gittorrent.utsl.gen.nz. Sure we chatted on IRC about it here and there as well. But the RFC has had a public profile since at least last year's GSoC when our last student was accepted to build it, but few people found time to comment on it. I have made every effort to keep everything useful in the public arena and as far as I know never turned down the opportunity to answer questions. And snide remarks about my choice to press a few buttons on my list server to make a new mailing list for a project I was undertaking I simply have no time for. -- 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
