public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Subject: Sourceware accepted as SFC member project
Date: Fri, 9 Sep 2022 00:50:00 +0200	[thread overview]
Message-ID: <YxpxmPLN4FKOblr6@wildebeest.org> (raw)
In-Reply-To: <Yw5aEEqCSZgqb8Cd@wildebeest.org>

Hi,

We are very grateful for the public replies and suggestions received
to our proposal, which were all very positive. And we are happy to
report that the SFC's Evaluations Committee has voted to accept
Sourceware as a Conservancy member project. If people are interested
in, or want to help out with, the next steps they are invited to join
the sourceware overseers list.

https://sourceware.org/pipermail/overseers/2022q3/018834.html

Thanks,

Chris Faylor <cgf@sourceware.org>
Frank Eigler <fche@sourceware.org>
Mark Wielaard <mark@klomp.org>

  reply	other threads:[~2022-09-08 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 18:42 Proposing Sourceware " Mark Wielaard
2022-09-08 22:50 ` Mark Wielaard [this message]
2022-11-15 21:35   ` Sourceware infrastructure presentation and community Q&A Mark Wielaard
2022-12-31 22:53     ` 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=YxpxmPLN4FKOblr6@wildebeest.org \
    --to=mark@klomp.org \
    --cc=bzip2-devel@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).