Re: Write after approval additions

[fche at redhat dot com (Frank Ch. Eigler)]

cagney wrote:

: [...]
: Someone gets to add themselves to the write after
: approval list of the MAINTAINERS file when they:
: 
:         o       have recently demonstated an ability
:                 to submit good quality patches to
: 		  gdb-patches.
: 		  (Hint, fix something trivial)
: 
:         o       have an assignment in place
: 
:         o       have OpenSSH and can reach the
:                 repository (so an account can be
:                 created).


It may be instructive to contrast this policy with that of binutils:

#                --------- Write After Approval ---------
# 
# Individuals with "write after approval" have the ability to check in
# changes, but they must get approval for each change from someone in
# one of the above lists (blanket write or maintainers).
# 
# [It's a huge list, folks.  You know who you are.  If you have the
#  *ability* to do binutils checkins, you're in this group.  Just remember
#  to get approval before checking anything in.]


I've always wondered what this specific colour along the power
spectrum was supposed to accomplish.  In what way is it a *useful*
middle point between maintainers and ordinary contributors?

It has the unintended consequence of making more work for maintainers.
They have to check in approved patches themselves instead of letting a
contributor do it.

- FChE