public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Do (old-ish) Portage QA checks comprise policy?
Date: Mon, 4 Nov 2019 16:02:35 -0600	[thread overview]
Message-ID: <20191104220235.GB8806@whubbs1.dev.av1.gaikai.org> (raw)
In-Reply-To: <20191105105009.7d39fc5f@katipo2.lan>

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

Hi Kent,

On Tue, Nov 05, 2019 at 10:50:09AM +1300, Kent Fredric wrote:
> On Mon, 4 Nov 2019 10:53:44 -0500
> Michael Orlitzky <mjo@gentoo.org> wrote:
> 
> > To avoid these sorts of questions in the future, it might be worth the 
> > time it would take to vote on each of these policies formally, document 
> > them on the wiki, and then move the related checks to ::gentoo/metadata 
> > where other package managers can benefit from them (and where they can't 
> > be unilaterally nuked). Having a comprehensive list of policies will 
> > also help developers who want to Do The Right Thing and who read up on 
> > these things proactively.
> 
> I believe the place for these is in the dev-manual[1]
> 
> If not the dev-manual, then if there is some other source of authority
> where they end up, there should be some mechanism to relay them to the
> dev-manual.
> 
> Its hard to expect people to follow a policy that is mostly codified in
> tools and cultural wisdom.

You are correct. When I was on the team, the idea was that the devmanual
was the cannonical source for all qa policies.

I'm not on the team now but I would strongly support this.

William

> 
> 1: https://archives.gentoo.org/gentoo-dev/message/497c28fb2dab0a480c302ba966481f4f



[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2019-11-04 22:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 15:01 [gentoo-dev] Do (old-ish) Portage QA checks comprise policy? Michał Górny
2019-11-04 15:53 ` Michael Orlitzky
2019-11-04 16:02   ` Michał Górny
2019-11-04 16:07     ` Michael Orlitzky
2019-11-04 19:26       ` William Hubbs
2019-11-04 20:05         ` Michael Jones
2019-11-04 21:51           ` William Hubbs
2019-11-04 19:40   ` William Hubbs
2019-11-04 23:17     ` Michael Orlitzky
2019-11-04 23:24       ` Michael 'veremitz' Everitt
2019-11-05 10:41         ` Kent Fredric
2019-11-05  0:17       ` William Hubbs
2019-11-05  0:47         ` Michael Orlitzky
2019-11-04 21:50   ` Kent Fredric
2019-11-04 22:02     ` William Hubbs [this message]
2019-11-05  2:26   ` Andreas K. Huettel

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=20191104220235.GB8806@whubbs1.dev.av1.gaikai.org \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@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