Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP

[Tom Wijsman <TomWij@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 2585 bytes --]

On Sat, 22 Jun 2013 12:20:22 +0200
Michael Weber <xmw@gentoo.org> wrote:

> But in every single metadata? Can I get a script for my 160 personal
> edits, pls?

You can find your metadata files with 

`grep -r --include 'metadata.xml' \>xmw@gentoo.org\< /usr/portage -l`

See "Inserting Content using sed" [1] on how to insert content after a
specific line, if you pass the above grep output through xargs you
should be able to easily adjust all the files. If you intent to do
more careful, then feel free to state so

 [1]: http://devmanual.gentoo.org/tools-reference/sed/

> And what's a sane default?

Asked this is my sub thread. Let's see before drawing conclusions.

> Let's take a amount to time (~2month) for responsive people to mark
> their preferences and default to EVERTHING_GOES/ANYBODY.

It may be reasonable for this to go before the council to avoid us from
taking a rushed decision that results in inconsistent metadata across
the tree; whatever happens, a big share of people should agree on the
matter and this should be properly and unambiguously documented.

> And we lost the timeout dimension. An "Feel free to bump my stuff"
> override in devaway works for single maintained packages, how to
> interpret these data for teams and multiple maints? AWOL people...

If there are multiple maintainers, there would be no need for random
developers to take care of the package; the rules in the file would
therefore still apply. Note the "my stuff" part of this, which means
this is not really about the packages of teams and multiple maints.

> Bottom line: I think we need more of a culture of mutual trust than a
> ton of metadata.

Yes, I think of this approach to be somewhat like to my optional files
metadata approach; though it introduces less metadata, and tries to
deal with a slightly different matter, but we should still be careful.

> - Respect the right of an maintainer to take a few days until
> responding (except QA, security, major skrew ups)

I assume you meant committing instead of responding, this is already
covered by the dev manual (do not commit unless you never got response).

> - Take a look at the package/ebuild complexity to estimate the
> maintainers affection.

Add eclasses to that, they can contain some tricky magic which might
not be directly clear from the ebuild.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]