From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Cc: council <council@gentoo.org>
Subject: [gentoo-dev-announce] Agenda for the council meeting 2017-12-10 18:00 UTC
Date: Sat, 09 Dec 2017 20:39:54 +0100 [thread overview]
Message-ID: <16099994.eYkbcOoAGA@pinacolada> (raw)
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
Agenda for the council meeting 2017-12-10 18:00 UTC
===================================================
0. Roll call
------------
1. Lack of enough package maintainers [1]
-----------------------------------------
Anything that can be done?
2. Update of GLEP 42 [2,3]
------------------------
Removal of the detached signature requirement, clarifications on translations
and file names
3. Final review of GLEP 74 [4,5]
--------------------------------
Full-tree verification using Manifest files
4. Restricting gentoo-dev/-project posting [6]
----------------------------------------------
* Restricting posting to both gentoo-dev and gentoo-project, while creating a
gentoo-experts list?
* Restricting posting to gentoo-dev and moving all official business there?
* Restricting posting to gentoo-dev and moving all official business to a
revived restricted gentoo-council list?
* Moderating lists instead?
5. Open bugs with council participation
---------------------------------------
* Bug 637274 - Missing summaries for 20170514 and 20170611 council meetings
[7]
* Bug 637328 - GLEP 14 needs to be updated [8]
* Bug 635344 - [TRACKER] manifest-hashes replacement [9]
6. Open floor
-------------
[1] https://archives.gentoo.org/gentoo-project/message/
4771bc564060b7ab1f64d5c094105493
[2] https://archives.gentoo.org/gentoo-dev/message/
6f070b64892d2e351bd51b2ffa1dc64e
[3] https://gitweb.gentoo.org/data/glep.git/log/?h=glep42-update
[4] https://archives.gentoo.org/gentoo-project/message/
7d189934e371842fc799ba1eead3d01f
[5] https://www.gentoo.org/glep/glep-0074.html
[6] https://archives.gentoo.org/gentoo-dev/message/
6e7cc13cd850be7dbd86376d3a197a16
[7] https://bugs.gentoo.org/637274
[8] https://bugs.gentoo.org/637328
[9] https://bugs.gentoo.org/635344
--
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 --]
reply other threads:[~2017-12-09 22:53 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=16099994.eYkbcOoAGA@pinacolada \
--to=dilfridge@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-dev-announce@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