public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
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 January 12, 18:00 UTC
Date: Thu, 11 Jan 2024 21:20:33 +0100	[thread overview]
Message-ID: <20240111202033.GA17321@gnu.wildebeest.org> (raw)

Happy new year!
This Friday will be the first Sourceware Open Office of 2024.

Join us this Friday, January 12, in #overseers on irc.libera.chat
from 18:00 till 19:00 UTC. 

For any questions or ideas about any Sourceware service and/or
integration of cgit, bugzilla, mailinglists, snapshots, mirrors,
archiving, gitsigur, secure supply chains, public-inbox, b4,
patchwork, bbb, buildbot (now including a risc-v board), etc.

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)

If you want to run your own meetings for any Sourceware project you
can create your own account at https://bbb.sfconservancy.org/b/signup
which we can then activate for you. Note: Anyone is able to join a
meeting, accounts are only required to create new meetings.

Of course you are welcome to drop into the #overseers channel at any
time and we can also be reached through email and bugzilla:
https://sourceware.org/mission.html#organization

Thanks to the Conservancy we now also have a donation page:
  https://sourceware.org/donate.html
to fund accelerating tasks the community feels most useful.
More details about our relationship with the Conservancy here:
https://sfconservancy.org/blog/2023/nov/27/sourceware-thanks-conservancy/

If you aren't already and want to keep up to date on Sourceware
infrastructure services then please also subscribe to the overseers
mailinglist. https://sourceware.org/mailman/listinfo/overseers

We are also on the fediverse these days:
https://fosstodon.org/@sourceware

The Sourceware Project Leadership Committee also meets once a month
to discuss all community input. The committee will set priorities and
decide how to spend any funds, negotiate with hardware and service
partners, create budgets together with the Conservancy, or decides
when a new fundraising campaign is needed. Up till now we have been
able to add new services without needing to use any of the collected
funds. Our hardware partners have also been very generous with
providing extra servers when requested. The current committee includes
Frank Ch. Eigler, Christopher Faylor, Ian Kelling, Ian Lance Taylor,
Tom Tromey, Jon Turney, Mark J. Wielaard and Elena Zannoni.

                 reply	other threads:[~2024-01-11 20:20 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=20240111202033.GA17321@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).