{"thread":{"id":"25761","subject":"Git roadmap (How read What's cooking in git.git)","startedAt":"2010-11-16T12:53:01Z","lastAt":"2010-11-18T15:31:11Z","messageCount":7,"participants":["Sebastien Douche","Ævar Arnfjörð Bjarmason","Jakub Narebski","Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"155995","messageId":"AANLkTimtUz3L0F_iOpH7YuYpyoutPqtevPj-Tjo6MRcs@mail.gmail.com","threadId":"25761","inReplyTo":null,"subject":"Git roadmap (How read What's cooking in git.git)","fromName":"Sebastien Douche","fromEmail":"sdouche@gmail.com","sentAt":"2010-11-16T12:53:01Z","receivedAt":"2010-11-16T12:53:01Z","isPatch":false,"sender":{"key":"sdouche@gmail.com","avatar":"https://gravatar.com/avatar/1b4a6cb11f6237ff9dc78b953ce48e416afa42e947143e14273cdc2c7f6f9c1a?d=mp&s=160"},"body":"Hi Junio,\nI'm starting a french blog[1] on git to support workshops[2]. The goal\nis to explain deeply the philosophy, the commands and subcommands,\nworkflows, etc. And also to aggregate headlines of the git world,\nfollow events and announce git releases. For the latter, it's a bit\nhard (for a non core developer) to follow the development. From your\npoint of view, how we could set up a roadmap and a \"what's new\"?\n\n\n\n[1] http://blog.gitfr.net\n[2] 100% free, with 50 attendees for the first workshop, 70 for the second!\n\n\n-- \nSebastien Douche \nTwitter: @sdouche (agile, lean, python, git, open source)\n"},{"id":"155996","messageId":"AANLkTim4FOixgxUjv24o9gTNqK3DWafmpNtDVMA+PS9d@mail.gmail.com","threadId":"25761","inReplyTo":"AANLkTimtUz3L0F_iOpH7YuYpyoutPqtevPj-Tjo6MRcs@mail.gmail.com","subject":"Re: Git roadmap (How read What's cooking in git.git)","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-11-16T13:38:30Z","receivedAt":"2010-11-16T13:38:30Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Tue, Nov 16, 2010 at 13:53, Sebastien Douche wrote:\n> I'm starting a french blog[1] on git to support workshops[2]. The goal\n> is to explain deeply the philosophy, the commands and subcommands,\n> workflows, etc. And also to aggregate headlines of the git world,\n> follow events and announce git releases. For the latter, it's a bit\n> hard (for a non core developer) to follow the development. From your\n> point of view, how we could set up a roadmap and a \"what's new\"?\n\nProjects that have a \"Roadmap\" are usually the ones that have paid\ndevelopers, where someone will centrally plan what things get worked\non. Then assign developers to those tasks.\n\nGit is a free software project. So it can't have a \"Roadmap\" in the\nsame sense.\n\nWhat we'll end up implementing is a function of what patches people\nsend, and which of those patches end up passing review and get into\ngit.git.\n\nYou can get something like a roadmap just by following what people are\nworking on, and asking them what they want to do next.\n"},{"id":"156076","messageId":"AANLkTikDyxUWBnCzxRNA9MzBmr0LrqDb1ggNjOTc=7DR@mail.gmail.com","threadId":"25761","inReplyTo":"AANLkTim4FOixgxUjv24o9gTNqK3DWafmpNtDVMA+PS9d@mail.gmail.com","subject":"Re: Git roadmap (How read What's cooking in git.git)","fromName":"Sebastien Douche","fromEmail":"sdouche@gmail.com","sentAt":"2010-11-18T01:55:30Z","receivedAt":"2010-11-18T01:55:30Z","isPatch":false,"sender":{"key":"sdouche@gmail.com","avatar":"https://gravatar.com/avatar/1b4a6cb11f6237ff9dc78b953ce48e416afa42e947143e14273cdc2c7f6f9c1a?d=mp&s=160"},"body":"On Tue, Nov 16, 2010 at 14:38, Ævar Arnfjörð Bjarmason wrote:\n\nHi Ævar,\nthank you for your response.\n\n> Projects that have a \"Roadmap\" are usually the ones that have paid\n> developers, where someone will centrally plan what things get worked\n> on. Then assign developers to those tasks.\n\nIt's a bit surprising that you (the core devs) haven't any ideas on\nthe future versions. But roadmap is maybe a misleading word, I talk to\nleverage a bit the visibility of the project for users. It's not a\nmajor point, \"what's cooking\" is a nice overview (understand it is a\ndifferent kettle of fish).\n\n> What we'll end up implementing is a function of what patches people\n> send, and which of those patches end up passing review and get into\n> git.git.\n\nCool.\n\n> You can get something like a roadmap just by following what people are\n> working on, and asking them what they want to do next.\n\nUnderstood. I will make it.\n\n\nBTW, congrats. Git is a wonderful piece of software.\n\n\n\n\n-- \nSebastien Douche \nTwitter: @sdouche (agile, lean, python, git, open source)\n"},{"id":"156096","messageId":"m3ipzu682o.fsf@localhost.localdomain","threadId":"25761","inReplyTo":"AANLkTimtUz3L0F_iOpH7YuYpyoutPqtevPj-Tjo6MRcs@mail.gmail.com","subject":"Re: Git roadmap (How read What's cooking in git.git)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-11-18T14:05:51Z","receivedAt":"2010-11-18T14:05:51Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Sebastien Douche writes:\n\n> I'm starting a french blog[1] on git to support workshops[2]. The goal\n> is to explain deeply the philosophy, the commands and subcommands,\n> workflows, etc. And also to aggregate headlines of the git world,\n> follow events and announce git releases. For the latter, it's a bit\n> hard (for a non core developer) to follow the development. From your\n> point of view, how we could set up a roadmap and a \"what's new\"?\n> \n> [1] http://blog.gitfr.net\n\nThere is Junio's blog which sometimes contain interesting bits about git:\n\n http://gitster.livejournal.com/\n\n\nThere is also \"A git blog looking to be official\" (with announcements\nand git top links, etc)\n\n http://gitlog.wordpress.com/\n\n\n\nI know that it doesn't really answer your question, but Git User's Surveys\nincluded question about what features one would want in Git, see for example\n\n https://git.wiki.kernel.org/index.php/GitSurvey2010\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"156100","messageId":"AANLkTi=ggFa4mwd=vkxJYq-JgCT=Tkmkv-0RQ_cqeYWm@mail.gmail.com","threadId":"25761","inReplyTo":"AANLkTikDyxUWBnCzxRNA9MzBmr0LrqDb1ggNjOTc=7DR@mail.gmail.com","subject":"Re: Git roadmap (How read What's cooking in git.git)","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2010-11-18T14:41:10Z","receivedAt":"2010-11-18T14:41:10Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Thu, Nov 18, 2010 at 8:55 AM, Sebastien Douche wrote:\n>> You can get something like a roadmap just by following what people are\n>> working on, and asking them what they want to do next.\n>\n> Understood. I will make it.\n\nAny chance you can revive the \"Git Chronicles\" [1]?\n\nJunio is too busy to update it (see his reply in [1]). I'm sure it\nwould be really appreciated.\n\n[1] http://mid.gmane.org/201007081057.51946.jnareb@gmail.com\n-- \nDuy\n"},{"id":"156101","messageId":"AANLkTi=BhjEfTtsKd-gTch8M7Af7cuTkrnLORNAz9gwX@mail.gmail.com","threadId":"25761","inReplyTo":"m3ipzu682o.fsf@localhost.localdomain","subject":"Re: Git roadmap (How read What's cooking in git.git)","fromName":"Sebastien Douche","fromEmail":"sdouche@gmail.com","sentAt":"2010-11-18T15:25:02Z","receivedAt":"2010-11-18T15:25:02Z","isPatch":false,"sender":{"key":"sdouche@gmail.com","avatar":"https://gravatar.com/avatar/1b4a6cb11f6237ff9dc78b953ce48e416afa42e947143e14273cdc2c7f6f9c1a?d=mp&s=160"},"body":"On Thu, Nov 18, 2010 at 15:05, Jakub Narebski wrote:\n>  http://gitster.livejournal.com/\n>  http://gitlog.wordpress.com/\n>  https://git.wiki.kernel.org/index.php/GitSurvey2010\n\nthank you Jakub for the links but I know all ;)\n\n\n-- \nSebastien Douche \nTwitter: @sdouche (agile, lean, python, git, open source)\n"},{"id":"156103","messageId":"AANLkTi=mH5QDvpBGGfjmLuLP9CZOtbxEZZe=A3r9U2g5@mail.gmail.com","threadId":"25761","inReplyTo":"m3eiai657o.fsf@localhost.localdomain","subject":"Re: Git roadmap (How read What's cooking in git.git)","fromName":"Sebastien Douche","fromEmail":"sdouche@gmail.com","sentAt":"2010-11-18T15:31:11Z","receivedAt":"2010-11-18T15:31:11Z","isPatch":false,"sender":{"key":"sdouche@gmail.com","avatar":"https://gravatar.com/avatar/1b4a6cb11f6237ff9dc78b953ce48e416afa42e947143e14273cdc2c7f6f9c1a?d=mp&s=160"},"body":"On Thu, Nov 18, 2010 at 16:07, Jakub Narebski wrote:\n>> Any chance you can revive the \"Git Chronicles\" [1]?\n>>\n>> Junio is too busy to update it (see his reply in [1]). I'm sure it\n>> would be really appreciated.\n>>\n>> [1] http://mid.gmane.org/201007081057.51946.jnareb@gmail.com\n>\n> There was also one issue of \"Git Traffic\", a spin-off now also defunct\n> for quite a long time \"Kernel Traffic\":\n>\n>  http://www.kerneltraffic.org/git/index.html\n>\n> It was meant to summarize events on git mailing list.\n>\n>\n> See also (quite out-of-date):\n>\n>  https://git.wiki.kernel.org/index.php/GitLinks#Mailing_list_digests\n\n(about Git Chronicles and Git Traffic)\nUnfortunately, my english is broken, that's why I would make the same\nin French. If a found a translator, I would be happy to create a\nenglsh version.\n\n\nCheers.\n\n\n-- \nSebastien Douche \nTwitter: @sdouche (agile, lean, python, git, open source)\n"}]}