From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Aaron Bauman <bman@gentoo.org>
Subject: Re: [gentoo-project] Council meeting Sunday 10/June/2018 18:00 UTC
Date: Sun, 10 Jun 2018 18:43:58 +0200 [thread overview]
Message-ID: <5836713.2cGbn1WedG@pinacolada> (raw)
In-Reply-To: <2619723.dyicR4dehs@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Am Sonntag, 10. Juni 2018, 18:34:37 CEST schrieb Andreas K. Huettel:
> > Additionally, the project liaison should be given some avenue of reprisal.
> > First thought would be to introduce an all hands developer vote be called
> > to unseat that project liaison.
> > e.g. council appointed, but developer community removed.
>
> That could be doable, but we need to make sure that this is not an "easy
> process". [...]
Just to expand on this a bit, if any such rule is introduced, it should work
the same way as the main rule - the liaison can only be unseated by
constructive vote, i.e., voting for a replacement. This makes sure the office
is never vacant.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-06-10 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 17:44 [gentoo-project] Council meeting Sunday 10/June/2018 18:00 UTC Andreas K. Huettel
2018-06-08 17:57 ` Michał Górny
2018-06-08 18:05 ` Andreas K. Huettel
2018-06-08 18:02 ` Andreas K. Huettel
2018-06-10 15:24 ` Aaron Bauman
2018-06-10 16:34 ` Andreas K. Huettel
2018-06-10 16:43 ` Andreas K. Huettel [this message]
2018-06-10 16:52 ` Aaron Bauman
2018-06-10 17:19 ` Rich Freeman
2018-06-10 17:25 ` Andreas K. Huettel
2018-06-10 19:51 ` [gentoo-project] Re: SPI as an alternate foundation Matthew Thode
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=5836713.2cGbn1WedG@pinacolada \
--to=dilfridge@gentoo.org \
--cc=bman@gentoo.org \
--cc=gentoo-project@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