Re: What's cooking in git.git (Aug 2018, #01; Thu, 2)

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 3, 2018, 21:45 UTC
Message-ID: <xmqq600rw2dj.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CAGZ79kZdPP+q9iuQioUU+2JkfH4n1mkkHrXaJzxGVwhxvbKZ1Q@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

Show 6 quoted lines

> - The second part of having an immediate plan is *very* nice
>   to see, though I would argue that it could be improved
>   by having these updates in the thread instead of summarized
>   unrelated to that thread.
>
>   We do not do this for now due to tooling issues, I suppose.

I need the current draft of "What's cooking" message that I haven't sent out (and the committed copy on 'todo' branch, which is a copy of what was already sent out) to be the single place I go that drives my day-to-day integration work anyway. I don't have time to jump around 30-70 discussion threads (assuming there only is one active one per each topic in flight) to see what the last tentative verdict I gave to each one of them before deciding which ones to merge to 'next' in day's integration run.

You are welcome to split these pieces out of the "What's cooking" report and spray them into the original message, or write a bot to do so.

> Is there a better way to start a workflow discussion?

My take on it is not to discuss ways to add more to other's workload to worsen the bottleneck in the first place, and instead try to do things you would think you can do to help, see if it actually helps, and then after that encourage discussit as a way for others to do to help the project, perhaps?