Re: development process

[Han-Wen Nienhuys]

On Wed, Feb 5, 2020 at 10:23 AM Jonas Hahnfeld <address@hidden> wrote:

> I don't see why we need to have a final list of detailed points that we
> all agree upon before sketching a process.


I think it's a more systematic way of approaching the problem. The reason
I'm doing it this way, is because I have a vested interest. My daytime job
is managing the  Gerrit codereview team at Google, so I am more intimately
familiar with Gerrit, have slight preference for its review experience, and
a vested interest in seeing it in broader use.

Note that "proposal" in my
> view doesn't mean there needs to be a working prototype. I would be
> happy to merely have a (subjective) list of points to address followed
> by how concrete tools would solve them and why others don't.
> Would it help you if I posted something like this?
>

Yes, definitely!

> if you can only work with concrete proposals, I guess you'll have to wait
> until the rest of us come to that point.
>
> Okay.
>
> Jonas
>


-- 
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen