From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Calling for Gentoo Quality Assurance (QA) team members
Date: Thu, 14 Nov 2013 22:52:33 +0100 [thread overview]
Message-ID: <201311142252.45051.dilfridge@gentoo.org> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 1342 bytes --]
Dear fellow Gentoo developers,
in its last session the Council has decided that the current QA team is being
dissolved [1]. This, however, does not mean that we don't need a QA team!
Exactly the opposite, an active Quality Assurance team is important for the
whole (meta)distribution.
The role, the abilities and the purpose of the Gentoo QA team are detailed in
GLEP 48 [2]. If you are interested in contributing to Gentoo Quality
Assurance, please consider officially becoming part of the Gentoo QA team.
How?
Send us *within two weeks* an e-mail at council@gentoo.org and tell us you're
interested. Maybe add a sentence or two on what you plan to contribute and
where you see important issues. That's all.
Acceptance is by secret majority vote of the Council members; we will inform
you of the decision as soon as possible.
The Council formally takes over the role of QA team lead for six weeks from
now; afterwards, the team members will elect their lead on their own.
We are looking forward to hear from you.
Best,
Andreas for the whole Council team
[1] http://www.gentoo.org/proj/en/council/meeting-logs/20131112-summary.txt
[2] http://www.gentoo.org/proj/en/glep/glep-0048.html
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
reply other threads:[~2013-11-14 22:37 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=201311142252.45051.dilfridge@gentoo.org \
--to=dilfridge@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-dev-announce@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