From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] [RFC] New doc & policy
Date: Fri, 21 Jul 2017 06:29:04 +0100 [thread overview]
Message-ID: <ef664551-2fc3-8b64-1e1f-91d8ae85b85f@iee.org> (raw)
In-Reply-To: <1500584775.746.11.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1411 bytes --]
On 20/07/17 22:06, Michał Górny wrote:
>
> Here's v2, taking into account suggestions from k_f and wraeth:
>
> ==Privileges and responsibilities of proxied maintainers==
> What you get as a proxied maintainer:
> * ability to maintain ebuilds directly in the Gentoo repository for all
> our users to use;
> * coverage from our teams: QA, security;
> * coverage by package-oriented services: [http://euscan.gentooexperiment
> al.org euscan], [https://qa-reports.gentoo.org/ qa-reports],
> [https://repology.org/ repology];
> * ability to request keywording on additional architectures (but note
> that most of arch teams are against proactive keywording) and to request
> stabilization;
<snip>
It's a subtle point, but it's one I think that can be fixed with a
wording tweak - I get wraeth's point about users requesting
stabilisation of a package, which is quite true .. so I think the
wording of the final point here might be better as something like "...
to request stabilisation of a package by the Arch Teams" or such.
After all, we're basically talking about the correct authority to CC the
arch teams on the stabilisation bugs, vs filing a stabilisation bug,
right? [which also might warrant mentioning/clarifying at another stage].
It's a minor point, but may be clearer exactly what's being indicated,
rather than creating confusion or misinterpretation.
HTH,
MJE
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next prev parent reply other threads:[~2017-07-21 5:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 8:02 [gentoo-proxy-maint] [RFC] New doc & policy Michał Górny
2017-07-20 8:33 ` Kristian Fiskerstrand
2017-07-20 15:02 ` Michał Górny
2017-07-20 9:36 ` Sam Jorna
2017-07-20 15:15 ` Michał Górny
2017-07-21 5:11 ` Sam Jorna (wraeth)
2017-07-20 21:06 ` Michał Górny
2017-07-21 5:14 ` Sam Jorna (wraeth)
2017-07-21 5:29 ` M. J. Everitt [this message]
2017-07-21 14:36 ` Philippe Chaintreuil
2017-07-21 18:16 ` Michał Górny
2017-07-24 17:59 ` Philippe Chaintreuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef664551-2fc3-8b64-1e1f-91d8ae85b85f@iee.org \
--to=m.j.everitt@iee.org \
--cc=gentoo-proxy-maint@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox