{"thread":{"id":"15781","subject":"GitTogether topics status (4th of October)","startedAt":"2008-10-04T16:16:40Z","lastAt":"2008-10-17T19:18:16Z","messageCount":6,"participants":["Christian Couder","Jeff King","Nicolas Pitre","Shawn O. Pearce","René Scharfe"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"92296","messageId":"200810041816.41026.chriscool@tuxfamily.org","threadId":"15781","inReplyTo":null,"subject":"GitTogether topics status (4th of October)","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2008-10-04T16:16:40Z","receivedAt":"2008-10-04T16:16:40Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nAs can be seen on the GitTogether page on the wiki: \n\nhttp://git.or.cz/gitwiki/GitTogether\n\nthe planned speakers/topics changed a lot during the last weeks and are now:\n\n- Johannes Schindelin (Google Tech Talk, 1 hour):\n\tContributing with Git (or: all your rebase are belong to us)\n\n- Shawn O. Pearce (Talk + Brainstorm, 1 hour):\n\tIntroduce the secret bundle project\n\n- Shawn O. Pearce (Talk + Debate, 0.5 hour):\n\tJGit, where is it going?\n\n- Shawn O. Pearce (Talk + Plan Hacking, 1 hour):\n\tPack v4, what's stopping you?\n\n- Sam Vilain (?):\n\tGitTorrent, Git as a DB backend, perl.git conversion\n\n- Junio C Hamano (Talk, 1 hour):\n\tGit Chronicle, Recent Additions to Git\n\n- Scott Chacon (Talk/Discussion, 1 hour):\n\tLinkable library, Scriptability\n\n- Scott Chacon (Hack Session(proposed)):\n\tArchitecting / Building a usable linkable library\n\n- Scott Chacon (Lightning Talk, 10 min):\n\tiGitHub - git daemon and repository browser on the iPhone\n\n- Tom Preston-Werner (Talk/Discussion, 1 hour)\n\tGit ideas from GitHub\n\n- ? (Talk/Discussion, 1 hour):\n\tNew git homepage hammering out\n\n- ? (Talk/Discussion, 1 hour):\n\tGit GUI that even a designer would use\n\nThere are still many things that are not clear or undecided. So more input \nis welcome.\n\nThe topics suggested on the wiki are:\n\n * GitTorrent: current state, security considerations, future direction\n * Submodules: how to make a UI for this important feature that is intuitive \nand complete\n * PackV4\n * JGit, quo vadis?\n * Using Git for everything but source (Git as a backup tool, how to handle \nlarge blobs, using as a DB back-end, etc)\n * How to make Git more attractive to the Google Code folks?\n * Success/War stories (big wanking session for Gits)\n * perl.git - the joy of grokking Perforce metadata using Postgres, and \nwriting a transactional git-fastimport exporter SamV\n * Linkable library for basic object access (libification or new library)\n * Scriptability, using git in other languages (using interfaces vs calling \nplumbing vs reimplementting) \n * Git GUI that even a designer could use (GitCheetah, AKA TortoiseGit?) (UI \nsession?)\n * Git integration with IDE, RAD, and editors (UI session?)\n * New Git Homepage hammering-out (UI session?)\n * Shawn's current bundle related secret project\n * TopGit introduction/design/integration(?)\n * Pasky's current pickaxe related \"secret project\" (if tangible by then)\n * Extending Git with volatile metadata database (see \n[http://mid.gmane.org/20080910164045.GL10360@machine.or.cz \n20080910164045.GL10360@machine.or.cz])\n * Git improvement ideas gleaned from creating and running Git``Hub as a \nsocial layer on top of Git\n * Git Survey 2008 results and discussion\n * Free form \"We tried to use git in our project this way, didn't work very \nwell\" session, where participants are not allowed to say \"Your workflow is \nbroken\".\n\nThanks,\nChristian.\n"},{"id":"92481","messageId":"20081007031509.GA6031@coredump.intra.peff.net","threadId":"15781","inReplyTo":"200810041816.41026.chriscool@tuxfamily.org","subject":"Re: GitTogether topics status (4th of October)","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2008-10-07T03:15:09Z","receivedAt":"2008-10-07T03:15:09Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Oct 04, 2008 at 06:16:40PM +0200, Christian Couder wrote:\n\n> As can be seen on the GitTogether page on the wiki: \n> \n> http://git.or.cz/gitwiki/GitTogether\n> \n> the planned speakers/topics changed a lot during the last weeks and are now:\n\nI just added two proposed half-hour meetings, both of which I intend to\nbe a few minutes of me talking followed by group discussion. The topics\nare:\n\n  1. Helping new developers join the git community\n\n     This title is a little bit sneaky. I want to talk about not just how\n     we can get new developers to help improve git, but also how we can\n     convince them to adopt workflows that make less work for reviewers\n     and maintainers. It seems like there are some things that we tell\n     new people over and over about formatting code, formatting patches,\n     sending patches, etc. Probably the end goal will be improvements to\n     SubmittingPatches, but maybe putting similar content somewhere more\n     visible, or maybe even adjusting our workflows a bit.\n\n     I hope to make it useful for veterans (who may _constructively_\n     complain about the habits of new developers), and new developers,\n     who may learn something about contributing.\n\n     This might overlap a bit with Dscho's \"contributing with git\" talk\n     (which I am not sure is a talk about using git to contribute in\n     general, or using git to contribute to git), but I think the\n     discussion-like forum will make it different enough to be valuable.\n\n  2. What needs refactoring?\n\n     I occasionally run up against parts of the code that just make my\n     eyes bleed everytime I touch them. I think we've made significant\n     progress in maintanability and bug-avoidance with things like the\n     strbuf library, refactoring of remote and transport handling, etc.\n     What areas might still benefit from such refactoring?\n\n-Peff\n"},{"id":"92484","messageId":"alpine.LFD.2.00.0810062343000.3045@xanadu.home","threadId":"15781","inReplyTo":"20081007031509.GA6031@coredump.intra.peff.net","subject":"Re: GitTogether topics status (4th of October)","fromName":"Nicolas Pitre","fromEmail":"nico@cam.org","sentAt":"2008-10-07T03:46:41Z","receivedAt":"2008-10-07T03:46:41Z","isPatch":false,"sender":{"key":"nico@fluxnic.net","avatar":"https://avatars.githubusercontent.com/u/702790?v=4"},"body":"On Mon, 6 Oct 2008, Jeff King wrote:\n\n>   2. What needs refactoring?\n> \n>      I occasionally run up against parts of the code that just make my\n>      eyes bleed everytime I touch them. I think we've made significant\n>      progress in maintanability and bug-avoidance with things like the\n>      strbuf library, refactoring of remote and transport handling, etc.\n>      What areas might still benefit from such refactoring?\n\nTree object walking and commit object parsing. This is what's holding \npack v4 performances back. But I think that Shawn will cover this \nalready (I won't be there but I sent my thoughts about this to him).\n\n\nNicolas\n"},{"id":"92530","messageId":"20081007143859.GJ8203@spearce.org","threadId":"15781","inReplyTo":"alpine.LFD.2.00.0810062343000.3045@xanadu.home","subject":"Re: GitTogether topics status (4th of October)","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-10-07T14:38:59Z","receivedAt":"2008-10-07T14:38:59Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Nicolas Pitre <nico@cam.org> wrote:\n> On Mon, 6 Oct 2008, Jeff King wrote:\n> \n> >   2. What needs refactoring?\n> > \n> >      I occasionally run up against parts of the code that just make my\n> >      eyes bleed everytime I touch them. I think we've made significant\n> >      progress in maintanability and bug-avoidance with things like the\n> >      strbuf library, refactoring of remote and transport handling, etc.\n> >      What areas might still benefit from such refactoring?\n> \n> Tree object walking and commit object parsing. This is what's holding \n> pack v4 performances back. But I think that Shawn will cover this \n> already (I won't be there but I sent my thoughts about this to him).\n\nYup.  A huge part of the pack v4 talk is going to be the parsing\ncode.  Maybe 10 minutes of it will give the high level overview\nof how pack v4 is organized, to explain why the parsing code is\na problem.  :)\n\n-- \nShawn.\n"},{"id":"92533","messageId":"20081007144643.GK8203@spearce.org","threadId":"15781","inReplyTo":"20081007031509.GA6031@coredump.intra.peff.net","subject":"Re: GitTogether topics status (4th of October)","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-10-07T14:46:43Z","receivedAt":"2008-10-07T14:46:43Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Jeff King <peff@peff.net> wrote:\n> I just added two proposed half-hour meetings, both of which I intend to\n> be a few minutes of me talking followed by group discussion. The topics\n> are:\n> \n>   1. Helping new developers join the git community\n\nOh, this is a good idea.  Yesterday I myself had trouble with\na new contributor not being familiar with the patching process.\nPartly also my fault of still being a green maintainer.  ;-)\n \n>   2. What needs refactoring?\n> \n>      I occasionally run up against parts of the code that just make my\n>      eyes bleed everytime I touch them. I think we've made significant\n>      progress in maintanability and bug-avoidance with things like the\n>      strbuf library, refactoring of remote and transport handling, etc.\n>      What areas might still benefit from such refactoring?\n\nAlso a good idea.  I imagine Junio may have some interest in this.\nI certainly do.  Some of the code is just bloodly aweful to work\nwith.  I guess those are the parts that make your eyes bleed.\n\n-- \nShawn.\n"},{"id":"93307","messageId":"48F8E4F8.3050902@lsrfire.ath.cx","threadId":"15781","inReplyTo":"200810041816.41026.chriscool@tuxfamily.org","subject":"Re: GitTogether topics status (4th of October)","fromName":"René Scharfe","fromEmail":"rene.scharfe@lsrfire.ath.cx","sentAt":"2008-10-17T19:18:16Z","receivedAt":"2008-10-17T19:18:16Z","isPatch":false,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"Christian Couder schrieb:\n> Hi,\n> \n> As can be seen on the GitTogether page on the wiki: \n> \n> http://git.or.cz/gitwiki/GitTogether\n\nWhile I won't be there, another good topic might be the usage of a patch\ntracker like patchwork (http://ozlabs.org/~jk/projects/patchwork/).\n\nRené\n"}]}