public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed

From: Mark Wielaard <mark@klomp.org>
To: gcc@gcc.gnu.org, gdb@sourceware.org, binutils@sourceware.org,
	 libc-alpha@sourceware.org
Cc: Dodji Seketeli <dodji@seketeli.org>,
	"Jose E. Marchesi" <jemarch@gnu.org>,
	 Guinevere Larsen <blarsen@redhat.com>
Subject: After Cauldron - online mini BoFs and Fosdem
Date: Wed, 27 Sep 2023 17:46:53 +0200	[thread overview]
Message-ID: <9ca90cd013675a960d47ee09fa4403f69405e9f2.camel@klomp.org> (raw)

Hi all,

Cauldron was really great. Seeing everybody in person again.
One item that came up was about meeting more frequently and/or in
smaller (virtual) groups.

If people want to have online mini BoFs to follow up on some discussion
they had at Cauldron, or for some periodic meetup, then please remember
that The Software Freedom Conservancy is extending the use of their Big
Blue Button instance https://bbb.sfconservancy.org/ to Sourceware
projects that want to host video meetings.

Please create an account at https://bbb.sfconservancy.org/b/signup then
contact admin-requests@sourceware.org with the name and email you used
and the kind of project/BoF/meeting you want to run to activate the
account.

Note: Anyone is able to join a meeting, accounts are only required to
create new meetings.

Also Doji, Jose and Gwen (on CC) are trying to coordinate a Fosdem
devroom for the various projects. Please contact them if you want to
help out with that.

Cheers,

Mark

https://sfconservancy.org/news/2023/aug/15/exit-zoom/
https://fosdem.org/2024/

next             reply	other threads:[~2023-09-27 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 15:46 Mark Wielaard [this message]
2023-10-03 12:37 ` Anyone interesting to submit a GCC devroom request proposal at FOSDEM? (was Re: After Cauldron - online mini BoFs and Fosdem) Dodji Seketeli
2023-10-16 18:31   ` David Malcolm
2023-10-17 14:24     ` Thomas Schwinge

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=9ca90cd013675a960d47ee09fa4403f69405e9f2.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=blarsen@redhat.com \
    --cc=dodji@seketeli.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jemarch@gnu.org \
    --cc=libc-alpha@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

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).