From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: [gentoo-nfp] Re: [gentoo-project] Foundation meeting agenda for April 2018
Date: Mon, 9 Apr 2018 00:25:50 -0400 [thread overview]
Message-ID: <CAAr7Pr_4zEaMrJ86hr9whJ=xW0zMRAWn3m5kodGLj0+aNrJCQA@mail.gmail.com> (raw)
In-Reply-To: <20180408202704.p3f6ktidjnbfb7co@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2384 bytes --]
On Sun, Apr 8, 2018 at 4:27 PM, Matthew Thode <prometheanfire@gentoo.org>
wrote:
> The canonical version of this agenda is located at:
> https://wiki.gentoo.org/wiki/Foundation:Meetings/2018/04
>
> The time / date / location of the meeting are as follows
> Saturday, April 21 2018 22:00 UTC on irc.freenode.net #gentoo-trustees
>
> Alicef:
> - Add Foundation:Consultants reference to https://www.gentoo.org/support
> - This seems to be done already, just need an ack for removal
> - (non-corporate) donors / "friends" page
> - licencing update (with ulm)
>
> klondike: request for accounting / bookkeeping (status update, with K_F)
>
> prometheanfire: openssl ecc update (stabilize 1.1)
>
> Infra update: jmbsvicetto
> Treasurer update: robbat2
>
> Open Bugs: https://bugs.gentoo.org/buglist.cgi?bug_status=
> UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_
> PROGRESS&bug_status=VERIFIED&email2=trustees&emailassigned_
> to2=1&emailcc2=1&emailreporter2=1&emailtype2=substring&known_name=
> TrusteesOpenBugs&list_id=3290194&order=Last%20Changed&query_based_on=
> TrusteesOpenBugs&query_format=advanced&resolution=---
>
> Cleanup: Next meeting: Saturday, May 19 2018 22:00 UTC
>
> Open Floor
>
> =======
> If you have any additions you wish to make, please submit it to the
> gentoo-nfp list at least 48 hours before the meeting is to take place.
>
I would propose that in lieu of the motion requested by Matthias and
Andreas the board should put forth a roadmap
to dissolution. The roadmap might look like the following:
1. Return to financial health by completing tax compliance, and hiring a
bookkeeper / accountant for ongoing accounting work.
2. Exploration of umbrella support of the organization.
3. Dissolution of the Foundation with assets transferred to said
umbrella.
It might contain timelines like:
1. The board expects to secure an accountant by August 2018 and return
to financial health by April 2019.
2. Exploration of umbrella support will begin by August 2018 and last
until Dec 2018 (at which point the board should have an umbrella selected,
or not.)
3. File dissolution papers and transfer remaining assets to umbrella by
August 2019.
I think this sends a much better message than some non-binding statement
(not that this timeline is necessarily binding either.)
-A
> --
> Matthew Thode (prometheanfire)
>
[-- Attachment #2: Type: text/html, Size: 3909 bytes --]
next prev parent reply other threads:[~2018-04-09 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 20:27 [gentoo-nfp] Foundation meeting agenda for April 2018 Matthew Thode
2018-04-09 4:25 ` Alec Warner [this message]
[not found] ` <87woxh77l4.fsf@gentoo.org>
2018-04-08 20:48 ` [gentoo-nfp] Re: [gentoo-project] " Andreas K. Huettel
2018-04-09 6:12 ` Michał Górny
2018-04-09 15:53 ` Matthias Maier
2018-04-09 15:58 ` Matthias Maier
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='CAAr7Pr_4zEaMrJ86hr9whJ=xW0zMRAWn3m5kodGLj0+aNrJCQA@mail.gmail.com' \
--to=antarus@gentoo.org \
--cc=gentoo-nfp@lists.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