public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-project@lists.gentoo.org,
	gentoo dev announce <gentoo-dev-announce@lists.gentoo.org>
Subject: [gentoo-project] Call for agenda items - Council meeting 2019-02-10
Date: Thu, 31 Jan 2019 17:28:12 +0100	[thread overview]
Message-ID: <2beb3305-396f-8b10-e2a1-4008d8505fa9@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 778 bytes --]

Hi all,

In almost two weeks from now, there will be a council meeting again. Now
is the time to raise and prepare agenda items that you want us to
discuss and/or vote upon.

Please respond to this message on the gentoo-project mailing list with
agenda items.

The final agenda will be sent out on 2019-02-04, so please make sure
you post any agenda items before that, or we may not be able to
accommodate it into the next meeting.

The meeting itself will happen on 2019-02-10 19:00 UTC [1] in the
#gentoo-council FreeNode IRC channel.


1. https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190210T19

-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-01-31 16:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 16:28 Kristian Fiskerstrand [this message]
2019-01-31 19:11 ` [gentoo-project] Call for agenda items - Council meeting 2019-02-10 Rich Freeman
2019-01-31 19:18   ` Kristian Fiskerstrand
2019-01-31 19:27   ` [gentoo-project] Appeals of Moderation Decisions Rich Freeman
2019-01-31 23:21     ` Raymond Jennings
2019-02-02  6:38       ` desultory
2019-02-02  7:06         ` Raymond Jennings
2019-02-02  6:34     ` desultory
2019-02-02 13:41       ` Rich Freeman
2019-02-03  4:22         ` desultory
2019-02-03 11:44           ` Andreas K. Huettel
2019-02-03 12:23             ` Michał Górny
2019-02-04  4:56               ` desultory
2019-02-04  5:39                 ` Michał Górny
2019-02-05  5:01                   ` desultory
2019-02-03 13:41             ` Kristian Fiskerstrand
2019-02-03 13:53               ` Andreas K. Huettel
2019-02-03 14:26                 ` Kristian Fiskerstrand
2019-02-03 15:51                   ` Kristian Fiskerstrand
2019-02-04  1:38                     ` Chí-Thanh Christopher Nguyễn
2019-02-04  4:59                       ` desultory
2019-02-04 13:05                       ` Andreas K. Huettel
2019-02-05 13:05                         ` Chí-Thanh Christopher Nguyễn
2019-02-05 13:05                           ` Kristian Fiskerstrand
2019-02-05 13:17                             ` Chí-Thanh Christopher Nguyễn
2019-02-04 13:45                       ` Rich Freeman
2019-02-05  5:01                         ` desultory
2019-02-05 12:47                         ` Chí-Thanh Christopher Nguyễn
2019-02-04  4:58                     ` desultory
2019-02-04  4:57                 ` desultory
2019-02-03 11:53           ` Rich Freeman
2019-02-04  5:05             ` desultory

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=2beb3305-396f-8b10-e2a1-4008d8505fa9@gentoo.org \
    --to=k_f@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