public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] New QA Policy Guide
Date: Sun, 19 Jan 2020 07:08:30 -0500	[thread overview]
Message-ID: <CAGfcS_kSpEON3jUYaykf7Ccod8vSo=fhVFughfdp6S3wVrjG4Q@mail.gmail.com> (raw)
In-Reply-To: <w6gr1zvlldm.fsf@kph.uni-mainz.de>

On Sun, Jan 19, 2020 at 6:46 AM Ulrich Mueller <ulm@gentoo.org> wrote:
>
> >>>>> On Sun, 19 Jan 2020, Michał Górny wrote:
>
> > The sources are stored in proj/policy-guide.git [3].  If you wish to
> > submit your own changes, you can either use the 'Policy Guide' bugzilla
> > component [4] and/or GitHub mirror [5].
>
> Please, no github for official policies. We should have a permanent
> paper trail for this kind of things, which isn't guaranteed if the
> discussion would happen entirely on github.
>
> Besides, by the Social Contract we cannot rely on a non-free service
> for anything official.

The official sources aren't in github.  A bugzilla component is
available, so if github goes away there is no problem and we aren't
relying on it.

It looks like there is the optional ability to do work on github, just
as people can optionally talk about anything, anywhere.

If I have a chat with another package maintainer at a bar, and they
modify their ebuild and push that to the Gentoo repo on infra, and no
bug is ever opened, that is 100% within our current policy.  I don't
see how having that discussion on github instead of at the bar changes
things.

They're just offering an alternative place to get things done.
Anybody who wants to could just file a bug instead.

If we want to have an additional Gentoo policy that nobody is allowed
to discuss a Gentoo policy outside of the lists and bugzilla that
would of course create issues with stuff like github, and probably
non-logged IRC channels and private messages as well.  However, that
is not our current policy.  Plenty of council decisions happen with
much of the actual discussion not being recorded anywhere.  I'm not
sure you could reasonably operate in any other way, as people do need
the ability to talk things out without having to posture.

I feel like this discussion has already happened in the past though...

-- 
Rich


  reply	other threads:[~2020-01-19 12:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 11:31 [gentoo-dev] New QA Policy Guide Michał Górny
2020-01-19 11:46 ` Ulrich Mueller
2020-01-19 12:08   ` Rich Freeman [this message]
2020-01-19 18:45     ` Kent Fredric
2020-01-19 18:54       ` Rich Freeman
2020-01-19 19:32         ` Kent Fredric
2020-01-19 19:44           ` Rich Freeman
2020-01-19 17:50   ` Thomas Deutschmann
2020-01-19 18:00     ` Michał Górny
2020-01-19 18:44 ` Haelwenn (lanodan) Monnier
2020-01-19 19:24   ` Michał Górny
2020-01-19 20:08   ` Michał Górny
2020-01-19 18:47 ` Kent Fredric
2020-01-19 19:34 ` Robin H. Johnson
2020-01-19 19:39   ` Michał Górny
2020-01-19 20:08   ` Michał Górny
2020-01-19 21:19 ` William Hubbs

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='CAGfcS_kSpEON3jUYaykf7Ccod8vSo=fhVFughfdp6S3wVrjG4Q@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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