On Tue, Nov 16, 2010 at 14:38, Ãvar ArnfjÃrà Bjarmason <avarab@xxxxxxxxx> wrote: Hi Ãvar, thank you for your response. > Projects that have a "Roadmap" are usually the ones that have paid > developers, where someone will centrally plan what things get worked > on. Then assign developers to those tasks. It's a bit surprising that you (the core devs) haven't any ideas on the future versions. But roadmap is maybe a misleading word, I talk to leverage a bit the visibility of the project for users. It's not a major point, "what's cooking" is a nice overview (understand it is a different kettle of fish). > What we'll end up implementing is a function of what patches people > send, and which of those patches end up passing review and get into > git.git. Cool. > You can get something like a roadmap just by following what people are > working on, and asking them what they want to do next. Understood. I will make it. BTW, congrats. Git is a wonderful piece of software. -- Sebastien Douche <sdouche@xxxxxxxxx> Twitter: @sdouche (agile, lean, python, git, open source) -- 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