From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-nfp@lists.gentoo.org
Subject: Re: [gentoo-nfp] Proposal: fix election duration & scheduling
Date: Sat, 29 Jun 2019 22:01:38 +0100 [thread overview]
Message-ID: <YZFZTNCE.KOX56DFH.4ZD3ADOP@LU2AU5JZ.3NIMKVSA.KKMVW4O4> (raw)
In-Reply-To: <robbat2-20190629T052039-877647330Z@orbis-terrarum.net> (from robbat2@gentoo.org on Sat Jun 29 06:55:39 2019)
[-- Attachment #1: Type: text/plain, Size: 2577 bytes --]
On 2019.06.29 06:55, Robin H. Johnson wrote:
> This is a personal nit that I'd like to see resolved from running &
> scheduling the Trustee elections, but also appreciate input from
> everybody at large. I feel this should be considered and voted on at
> the
> AGM.
>
> Problem:
> - Scheduling the Foundation election is constrained by the AGM and
> recordation date requirements in bylaws & state laws.
> - The entire time period of the election has tended to drag on too
> long
> generally.
>
> To work backwards from the AGM, can we agree to set recommended
> periods
> for the election timeline:
>
> Election cycle preamble:
> YYYY/June/xx: June meeting sets formal approval of dates
> YYYY/June/16: AGM date announcement ~60 days window
>
> YYYY/July/01: Proposed recordation date, must be at least 10 days
> after June meeting ** [bylaw requirement??]
>
> primary election (30 days):
> YYYY/July/01: nomination opens, 14 days
> YYYY/July/15: nomination closes
> YYYY/July/14: setup day, 1 day
> YYYY/July/15: voting opens, 14 days
> YYYY/July/29: voting closes
> YYYY/July/30: voting results, 1 day
>
> secondary election (16 days):
> YYYY/July/30: nomination opens (automatically triggered by the primary
> result publication), 7 days
> YYYY/August/05: nomination closes
> YYYY/August/06: setup, 1 day
> YYYY/August/07: voting opens, 7 days
> YYYY/August/13: voting closes
> YYYY/August/14: voting results, 1 day
>
> AGM:
> YYYY/August/15: AGM date
That all works for me. My preference is to see it written in time before
AGM as the AGM is not fixed.
>
> Concerns:
> Could somebody with a more rules-lawyer oriented thought process
> confirm
> how the 10-60 days in Bylaw 3.7 constrain the recordation date?
The two are not strictly connected.
The 10-60 day window is for the AGM announce. Its straight out of
the NM statutes.
New trustees take their seats at the end of the AGM. The AGM is
their last chance at due diligence.
The Record date is the date when the list of potential participants
in the forthcoming election is closed. Its public purpose is a call for
new members to join if they want to participate in the election.
>
> --
> 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
>
--
Regards,
Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
arm64
[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-29 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 5:55 [gentoo-nfp] Proposal: fix election duration & scheduling Robin H. Johnson
2019-06-29 21:01 ` Roy Bamford [this message]
2019-06-30 6:15 ` Robin H. Johnson
2019-06-30 8:48 ` Roy Bamford
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=YZFZTNCE.KOX56DFH.4ZD3ADOP@LU2AU5JZ.3NIMKVSA.KKMVW4O4 \
--to=neddyseagoon@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