From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
binutils@sourceware.org, gdb@sourceware.org
Subject: Sourceware Open Office, Friday 16:00 UTC, new times, new policy
Date: Tue, 9 Apr 2024 00:35:53 +0200 [thread overview]
Message-ID: <20240408223553.GX1292@gnu.wildebeest.org> (raw)
Friday April 12, 16:00 UTC, irc.libera.chat #overseers
To get the right time in your local timezone:
$ date -d "Fri April 12 16:00:00 UTC 2024"
Note this is a new time!
Discussion topics:
- Sourceware 2024 - The Plan
https://inbox.sourceware.org/20240325095827.GI5673@gnu.wildebeest.org/
- Sourceware mitigating and preventing the next xz-backdoor
https://inbox.sourceware.org/20240329203909.GS9427@gnu.wildebeest.org/T/
- Proposed aging inactive users policy
https://inbox.sourceware.org/overseers/ZhQZXogZMozVjIYn@elastic.org/T/
For this meeting we will also have a BBB meeting room:
https://bbb.sfconservancy.org/b/mar-aom-dmo-fko
(But the real discussion will be in the irc channel)
reply other threads:[~2024-04-08 22:36 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240408223553.GX1292@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).