From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-nfp@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] [gentoo-nfp] Foundation meeting agenda for April 2018 - update2
Date: Wed, 11 Apr 2018 23:31:14 -0500 [thread overview]
Message-ID: <20180412043114.56zzg67anl6tgcio@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2729 bytes --]
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
If you have a new item, make a new thread on the gentoo-nfp list. One
item per thread. If I missed an item please let me know (and point me
to it). New submissions need to be recieved at least 48 hours before
the meeting is to take place.
Agenda Follows
==============
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)
community-items:
- Formalize Gentoo GLEP 39 as a bylaw (src: tamiko)
- https://archives.gentoo.org/gentoo-nfp/message/72cd545080420eab7cb1403cea7caab4
- GDPR (src: mrueg)
- enoemail (send the email you sent us to the nfp list)
- Formalize Gentoo's org structure (src: prometheanfire)
- https://archives.gentoo.org/gentoo-nfp/message/944b824fc1d1ca89bcae2d1c3f0520b7
- https://archives.gentoo.org/gentoo-nfp/message/58dbc3cbbb11dc3be2c0ceb3ad8a2059
- Formalize Gentoo Foundation's control over Gentoo infrastructure (src: drobbins)
- https://archives.gentoo.org/gentoo-nfp/message/151b44012a649a98a5e5268d3ed35bdd
- Trustees enforce CoC for Council (src: drobbins)
- enoemail (send the email you sent us to the nfp list)
- Trustees place user representitive on the council (src: drobbins)
- enoemail (send the email you sent us to the nfp list)
- Add reopen nominations option to ballot (src: k_f)
- https://archives.gentoo.org/gentoo-nfp/message/c7412600866cd650c9d9b147f3a83966
- present financial reports for 2013-2017
- https://archives.gentoo.org/gentoo-nfp/message/a498b27e5f49db25e2fd3fc8586ca777
- contact greg eben for finance and legal advice
- https://archives.gentoo.org/gentoo-nfp/message/6e2c1974935494b7791e3958ef7e7562
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
--
Matthew Thode (prometheanfire)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2018-04-12 4:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180412043114.56zzg67anl6tgcio@gentoo.org \
--to=prometheanfire@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