Re: The future of commit access policy for core Firefox

On 3/9/17 8:19 PM, Bobby Holley wrote:
> That said, there can still be hitches in the landing process that are not
> necessarily related to the review tool (recall all the edge cases that bz
> hit a few weeks ago).

Most of those were due to opinionated tools that have opinions that 
don't match reality, nor each other.

The fewer tools at a time in the mix, the better from that point of view.

That said, I strongly urge people working on these tools to actually 
consider the various workflows we use and make sure the tools don't 
assume common ones away.  The issues I ran into also had to do with the 
opinionated tools having the opinion that certain use cases don't exist. 
  Use cases that were brought up as a problem with these tools several 
years ago...  This sort of thing is OK for optional-to-use tools, but 
less OK for mandatory ones.

> but building a replacement for {git,hg} push that satisfies
> everyone's use-cases is equally hard.

A good start here is establishing what the use-cases are.

-Boris

P.S. I am still thinking about the original policy questions here; 
trying not to rathole too much on the mechanism