From: "Sam Jorna (wraeth)" <wraeth@gentoo.org>
To: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] [RFC] New doc & policy
Date: Fri, 21 Jul 2017 15:11:03 +1000 [thread overview]
Message-ID: <9bf5f0e1-4db4-3ce9-b619-bc64b6beef22@gentoo.org> (raw)
In-Reply-To: <1500563738.746.8.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 4357 bytes --]
On 21/07/17 01:15, Michał Górny wrote:
> On czw, 2017-07-20 at 19:36 +1000, Sam Jorna wrote:
>> On 20/07/17 18:02, Michał Górny wrote:
>>> * ability to request keywording on additional architectures (but note
>>> that most of arch teams are against proactive keywording) and to request
>>> stabilization;
>>
>> Stabilisation requests can also be filed by users per [1] without being
>> the maintainer.
>
> This is not the point. The point is, you can't file
> a keywordreq/stablereq against a package that's not in ::gentoo. So
> being a proxied maintainer means you can submit a package that will go
> stable.
Fair enough, just was worried it was a "you get <this thing> that you
can already do anyway".
>>> * ensure that the package follows the best practices (preferably of our
>>> own accord),
>>
>> I'm not sure what this wording is supposed to mean.
>
> That was supposed to be 'your own accord'. The generic idea is that we
> want proxied maintainers to use newest EAPI, follow current policies
> and so on. Should I give those examples in the doc?
I think how you have it now (v2) is good.
>>> Our team will review the submitted files and help you bring them to the
>>> top quality. Once the package is ready, we will merge it and close the
>>> relevant bugs (if there are any).
>>
>> The bugs should probably be assigned to the maintainer for them to close
>> (if suitable) or otherwise deal with, as described below.
>
> It's about maintainer-wanted bugs. I don't really see a reason to
> reassign this kind of bug and tell maintainer to close it afterwards.
Right, I was thinking maintainer-needed.
>>> It is recommended that you try to keep the same commit structure as
>>> you'd use when committing straight to Gentoo as a developer, and follow
>>> the best git practices (atomic changes, proper commit messages). For
>>
>> A link to [2] or [3] may be useful here (or, at least, /somewhere/).
>
> Yeah, I'm still thinking of how to solve this best. Maybe a separate
> section on git with links would be helpful, since right now things seem
> to be a little split between the three methods.
The links that are there at present, plus your suggestion about a
reference list on the main page below, should be enough I think.
>>> You need to explicitly use <kbd>repoman full -e y</kbd> to verify the
>>> experimental profiles.
>>
>> What about developer profiles (`repoman full -d`) and checking metadata
>> (`repoman full -x`)?
>
> Out of scope. I wanted only to give the generic note that things won't
> work out of the box for the common case of ~arm64.
>
> It's first time I hear that I need '-x' for anything. Why is that?
I remember reading somewhere that repoman didn't check metadata.xml by
default, though I can't find that reference any more. It could be
out-of-date information, or I may have mis-remembered.
>>> ===Keywording & stabilization===
>>> As a proxied maintainer, you can request [https://devmanual.gentoo.org/k
>>> eywording/index.html keywording and stabilization] of your packages.
>>> However, all those requests need to be approved by proxy-maint team
>>> member (or a regular developer co-maintainer) first.
>>
>> As mentioned previously, others can request stabilisation as well.
>
> The point is that you need approval from proxy-maint. Compare with
> today's bug when an user CC-ed arches on a bug that hasn't even been
> assigned.
A previous incarnation of the stablereq policy had users CC'ing relevant
teams after a timeout. How that works with the bot now I'm not sure.
Either way, I'm happy with how this is now.
>>> If you ever change your Bugzilla e-mail address, please remember to
>>> submit an update to your package {{Path|metadata.xml}} files. We will
>>> also note the new e-mail address on the maintainer bug.
>>
>> This implies maintainer address and bugzilla address may be different,
>> which will annoy bug wranglers to no end.
>
> Are you suggesting that I make it 'submit an update ... first'?
No, it came across as that your Bugzilla address and maintainer address
per metadata.xml did not have to be the same, so long as you added a
comment to the bug noting your maintainer address. I think this is
adequately covered now.
--
Sam Jorna (wraeth)
GnuPG ID: D6180C26
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2017-07-21 5:11 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) [this message]
2017-07-20 21:06 ` Michał Górny
2017-07-21 5:14 ` Sam Jorna (wraeth)
2017-07-21 5:29 ` M. J. Everitt
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=9bf5f0e1-4db4-3ce9-b619-bc64b6beef22@gentoo.org \
--to=wraeth@gentoo.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