public inbox for gentoo-qa@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio “Flameeyes” Pettenò" <flameeyes@gmail.com>
To: gentoo-qa@lists.gentoo.org
Cc: qa@gentoo.org
Subject: [gentoo-qa] Roll-call for the team members and requesting a new election
Date: Sat, 21 Aug 2010 19:46:45 +0200	[thread overview]
Message-ID: <1282412805.445.47.camel@yamato.local> (raw)

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

First off, checking the current list of QA members, please answer just
to make sure you are active and still interested of being part of the
team:

 - Mark Loeser
 - Diego Elio Pettenò (here);
 - Markos Chandras
 - Christian Ruppert
 - Piotr Jaroszyński
 - Tomas Chvatal
 - Ned Ludd (not on qa@g.o alias)
 - Sven Wegener
 - Torsten Veller
 - Joshua Jackson (not on qa@g.o alias)
 - Mike Frysinger
 - Samuli Suominen (not on project page)
 - Brian Ferring (not on project page)

After this I'd like to call for an election of a new lead; I have asked
privately for Mark to resign, or call up new elections himself, so that
I could avoid to state it this way but I see no other choice.

Given the current (sorry) state of QA, working mostly leadless (Mark
seems to be around when you're complaining he's not around), and with
most members apathetic about all kind of issues, I'm proposing myself as
new lead.

The role of the lead in this project cannot be simply a "supervising"
one, given that it's the only member of the team that devrel is
interested in hearing from (situation that, by itself, should probably
be changed); it requires actual leading and decision-taking, especially
given the current situation where many policies have never been written
down, and our documentation resources for developers are scattered and
outdated.

Given that I for one feel like the lead should be an active presence in
the project, together with my offer to step up I promise that if I ever
were to find myself in a situation where I wouldn't be able to find the
time to keep up with my duties, I'd be resigning and asking for new
elections right away.

-- 
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/

If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/


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

             reply	other threads:[~2010-08-21 18:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 17:46 Diego Elio “Flameeyes” Pettenò [this message]
2010-08-21 18:08 ` [gentoo-qa] Re: Roll-call for the team members and requesting a new election Markos Chandras
2010-08-21 18:15 ` [gentoo-qa] " Mark Loeser
     [not found] ` <AANLkTikiW2QOUnXw1kR2kmPATujABGy0VQ1_u-L6eVpK@mail.gmail.com>
2010-08-21 18:18   ` [gentoo-qa] " Diego Elio “Flameeyes” Pettenò
2010-08-21 19:51 ` Christian Ruppert
2010-08-21 20:11   ` Markos Chandras
2010-08-21 20:55   ` [gentoo-qa] List of non-integrated QA tools/scripts [WAS: Re: Roll-call for the team members and requesting a new election] Diego Elio “Flameeyes” Pettenò
2010-08-21 20:34 ` [gentoo-qa] Re: Roll-call for the team members and requesting a new election Tomáš Chvátal

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=1282412805.445.47.camel@yamato.local \
    --to=flameeyes@gmail.com \
    --cc=gentoo-qa@lists.gentoo.org \
    --cc=qa@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