public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev-announce] New QA Policy Guide
Date: Sun, 19 Jan 2020 12:31:52 +0100	[thread overview]
Message-ID: <dadd63ebaaa10cafb821b87aa37864a543b5cc3d.camel@gentoo.org> (raw)

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

Hello,

In the light of the recent misunderstandings, I have started working
on an official Policy Guide [1].  The Guide is meant to provide
a focused list of officially approved QA policies, along with their
rationale and any other useful information.

This should supplement devmanual [2] with clear information on what is
enforceable policy, and what is merely a suggestion (or possibly
outdated information, which is a common problem for devmanual).

The current document contents were approved by the QA project.  However,
it is by no means complete.  Further existing policies (as well as new
policies) will be documented there as they are approved by QA team.

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].

Enjoy!


[1] https://projects.gentoo.org/qa/policy-guide/
[2] https://devmanual.gentoo.org/
[3] https://gitweb.gentoo.org/proj/policy-guide.git/
[4] https://bugs.gentoo.org/enter_bug.cgi?product=Documentation&component=Policy+Guide
[5] https://github.com/gentoo/policy-guide

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

                 reply	other threads:[~2020-01-19 11:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=dadd63ebaaa10cafb821b87aa37864a543b5cc3d.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev-announce@lists.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