From: Alec Warner <antarus@gentoo.org>
To: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: Re: [gentoo-nfp] Non-contactable Members
Date: Tue, 9 Jul 2019 12:19:26 -0700 [thread overview]
Message-ID: <CAAr7Pr91U2EB=5fzOHz2EvDoyYZsuWD8uMrROMCgvVMTPPrjdw@mail.gmail.com> (raw)
In-Reply-To: <16bd8206c60.27c9.26c0c48bea5b0fcc301150500db51b7d@iee.org>
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
On Tue, Jul 9, 2019 at 12:05 PM M. J. Everitt <m.j.everitt@iee.org> wrote:
> On 9 July 2019 7:53:50 pm "Robin H. Johnson" <robbat2@gentoo.org> wrote:
>
> > On Tue, Jul 09, 2019 at 07:48:42PM +0100, M. J. Everitt wrote:
> >> On 9 July 2019 7:43:33 pm Aaron Bauman <bman@gentoo.org> wrote:
> >> > The following list of individuals currently have email addresses on
> file with
> >> > the Foundation which have bounced from the gentoo-foundation-announce
> mailing
> >> > list. If you intend to participate in this election cycle please
> email
> >> > trustees@gentoo.org with an updated email address.
> > ...
> >> > On Behalf of the Trustees,
> >> Forgive me, but haven't these members been retired??
> > Retiring a developer does not automatically revoke your Foundation
> > membership.
> >
> > I'd like to point out this clause under bylaw 7.1 [1]:
> > "Each member shall be responsible for notifying the foundation of
> > changes to such member's, electronic mail address and public gpg key."
> >
> > [1]
> >
> https://wiki.gentoo.org/wiki/Foundation:Bylaws#Section_7.1._Books_and_Records
> >
> > --
> > Robin Hugh Johnson
> > Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
> > E-Mail : robbat2@gentoo.org
> > GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
> > GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
>
> How does this reconcile with the requirement that all trustee members must
> be Gentoo developers?! And/or can only become members as a result of
> competing the developer quizzes. This seems rather bizarre, no?!
>
The Foundation has members (who can be anyone[0]), a board of trustees (who
must be active developers) and officers (some of whom can be anyone; but
some officer posts are restricted to trustees only, and thus are also
restricted to developers.)
The board is formed of active developers to sustain a relationship with the
developer community.
Is this unclear?
-A
[0]
https://wiki.gentoo.org/wiki/Foundation:Bylaws#Section_4.3._Admission_of_Members
[-- Attachment #2: Type: text/html, Size: 3074 bytes --]
next prev parent reply other threads:[~2019-07-09 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 18:42 [gentoo-nfp] Non-contactable Members Aaron Bauman
2019-07-09 18:48 ` M. J. Everitt
2019-07-09 18:50 ` Doug Freed
2019-07-09 18:53 ` Robin H. Johnson
2019-07-09 19:05 ` M. J. Everitt
2019-07-09 19:19 ` Alec Warner [this message]
2019-07-09 19:22 ` Michał Górny
2019-07-09 21:23 ` Michael Everitt
2019-07-10 6:28 ` Ulrich Mueller
2019-07-10 8:53 ` Michał Górny
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='CAAr7Pr91U2EB=5fzOHz2EvDoyYZsuWD8uMrROMCgvVMTPPrjdw@mail.gmail.com' \
--to=antarus@gentoo.org \
--cc=gentoo-nfp@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