From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Subject: Re: Sourceware infrastructure presentation and community Q&A
Date: Sat, 31 Dec 2022 23:51:01 +0100 [thread overview]
Message-ID: <Y7C81dWqqPIszZbR@wildebeest.org> (raw)
In-Reply-To: <Y3QE4eZDTBNhCs6s@wildebeest.org>
On Tue, Nov 15, 2022 at 10:30:09PM +0100, Mark Wielaard wrote:
> 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 (*)
Thanks to everybody who could attend last month. For those who
couldn't the html slides and markdown sources with the presenter notes
are here:
https://gnu.wildebeest.org/blog/mjw/2022/11/20/new-services-for-sourceware-sfc-fsf/
And a (video) recording is here:
https://media.libreplanet.org/u/libreplanet/m/sourceware-infrastructure-a-presentation-and-community-q-a/
We hope to have answered all questions, but if we missed anything, or
you want to help with the infrastructure please contact us at the
overseers mailinglist or file a sourceware infrastucture bug:
https://sourceware.org/mailman/listinfo/overseers
https://sourceware.org/bugzilla/buglist.cgi?component=Infrastructure&product=sourceware
Next year Sourceware will be 25 years. Happy new year!
(*) The Software Freedom Conservancy is currently running a fundraiser:
https://sfconservancy.org/sustainer/#YearInReview
prev parent reply other threads:[~2022-12-31 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 18:39 Proposing Sourceware as SFC member project Mark Wielaard
2022-09-08 22:46 ` Sourceware accepted " Mark Wielaard
2022-11-15 21:30 ` Sourceware infrastructure presentation and community Q&A Mark Wielaard
2022-12-31 22:51 ` Mark Wielaard [this message]
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=Y7C81dWqqPIszZbR@wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@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).