Git roadmap (How read What's cooking in git.git)

Hi Junio,
I'm starting a french blog[1] on git to support workshops[2]. The goal
is to explain deeply the philosophy, the commands and subcommands,
workflows, etc. And also to aggregate headlines of the git world,
follow events and announce git releases. For the latter, it's a bit
hard (for a non core developer) to follow the development. From your
point of view, how we could set up a roadmap and a "what's new"?



[1] http://blog.gitfr.net
[2] 100% free, with 50 attendees for the first workshop, 70 for the second!


-- 
Sebastien Douche [off-list ref]
Twitter: @sdouche (agile, lean, python, git, open source)

On Tue, Nov 16, 2010 at 13:53, Sebastien Douche [off-list ref] wrote:

I'm starting a french blog[1] on git to support workshops[2]. The goal
is to explain deeply the philosophy, the commands and subcommands,
workflows, etc. And also to aggregate headlines of the git world,
follow events and announce git releases. For the latter, it's a bit
hard (for a non core developer) to follow the development. From your
point of view, how we could set up a roadmap and a "what's new"?

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.

Git is a free software project. So it can't have a "Roadmap" in the
same sense.

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.

You can get something like a roadmap just by following what people are
working on, and asking them what they want to do next.

On Tue, Nov 16, 2010 at 14:38, Ævar Arnfjörð Bjarmason [off-list ref] 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 [off-list ref]
Twitter: @sdouche (agile, lean, python, git, open source)

Sebastien Douche [off-list ref] writes:

I'm starting a french blog[1] on git to support workshops[2]. The goal
is to explain deeply the philosophy, the commands and subcommands,
workflows, etc. And also to aggregate headlines of the git world,
follow events and announce git releases. For the latter, it's a bit
hard (for a non core developer) to follow the development. From your
point of view, how we could set up a roadmap and a "what's new"?

[1] http://blog.gitfr.net

There is Junio's blog which sometimes contain interesting bits about git:

  http://gitster.livejournal.com/


There is also "A git blog looking to be official" (with announcements
and git top links, etc)

  http://gitlog.wordpress.com/



I know that it doesn't really answer your question, but Git User's Surveys
included question about what features one would want in Git, see for example

  https://git.wiki.kernel.org/index.php/GitSurvey2010

-- 
Jakub Narebski
Poland
ShadeHawk on #git

On Thu, Nov 18, 2010 at 8:55 AM, Sebastien Douche [off-list ref] wrote:

quoted

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.

Any chance you can revive the "Git Chronicles" [1]?

Junio is too busy to update it (see his reply in [1]). I'm sure it
would be really appreciated.

[1] http://mid.gmane.org/201007081057.51946.jnareb@gmail.com
-- 
Duy

On Thu, Nov 18, 2010 at 15:05, Jakub Narebski [off-list ref] wrote:

 http://gitster.livejournal.com/
 http://gitlog.wordpress.com/
 https://git.wiki.kernel.org/index.php/GitSurvey2010

thank you Jakub for the links but I know all ;)


-- 
Sebastien Douche [off-list ref]
Twitter: @sdouche (agile, lean, python, git, open source)