From: Mark Wielaard <mark@klomp.org>
To: gcc-rust@gcc.gnu.org
Subject: Sourceware infrastructure presentation and community Q&A
Date: Tue, 15 Nov 2022 22:46:17 +0100 [thread overview]
Message-ID: <Y3QIqbOwAFnC/nRn@wildebeest.org> (raw)
In-Reply-To: <YxpziWafU0BiZXgZ@wildebeest.org>
This Friday, 18 November, at 16:00 UTC (11:00am Eastern, 17:00 Central
European Time) the FSF will host a session on their BBB server about
the current sourceware infrastructure and future plans.
https://www.fsf.org/events/sourceware-infrastructure-a-presentation-and-community-q-a
https://inbox.sourceware.org/overseers/6e9cde97-d880-5343-6cfd-16a648cf67f6@fsf.org/
We like to discuss how to use the new infrastructure setup this last
year, builder, try/ci/full buildbots, bunsen testsuite analysis,
patchwork patch tracking, handling patches/email with public-inbox,
b4, the sourcehut mirror. And the future of Sourceware as a Software
Freedom Conservancy member project. (*)
This presentation is for everybody who likes to discuss (and wants to
help with) automating the infrastructure to make contributing to our
projects more fun and more productive.
(*) Similar to the BoF we intended to do at the Cauldron this year:
https://gnu.wildebeest.org/~mark/sourceware/presentation.html
next prev parent reply other threads:[~2022-11-15 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 18:49 Proposing Sourceware as SFC member project Mark Wielaard
2022-09-08 22:58 ` Sourceware accepted " Mark Wielaard
2022-09-09 10:11 ` Philip Herron
2022-09-09 10:40 ` Mark Wielaard
2022-11-15 21:46 ` Mark Wielaard [this message]
2022-12-31 22:57 ` Sourceware infrastructure presentation and community Q&A Mark Wielaard
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=Y3QIqbOwAFnC/nRn@wildebeest.org \
--to=mark@klomp.org \
--cc=gcc-rust@gcc.gnu.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).