Ryan Hill posted on Wed, 04 Nov 2009 21:48:23 -0600 as excerpted:

> Is there any interest in allowing certain packages to be stabilized by
> the maintainer without going through the arch teams?  I always feel
> guilty when i file stabilization bugs for app-doc pkgs.

Weren't there already arrangements for this in some cases?  I distinctly 
recall a thread on it some time ago, with the conclusion being that 
various maintainers can get permission from the arch teams to keyword 
their own packages.

Now that was in the /general/ context of having access to the arch either 
directly/personally or thru available testing resource machines, but (as 
klausman accounts for in his post) that really doesn't apply to (for 
example) docs packages that don't require fancy build-chains or (with 
some sanity margin) where the build chain dependencies have been long 
stable, so "required testing resources" are virtually zero.

Thus, I'd say it's probably an extension of the previous arrangement -- 
but of course that does still require an initial one-time permission 
grant per arch, either per-package, or depending on arch/pkg-maintainer 
trust level, possible per category or similar.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman