From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Marc <dkm@kataplop.net>, pono@sfconservancy.org, mark@klomp.org
Subject: Re: proposing Sourceware as Software Freedom Conservancy member project
Date: Thu, 1 Sep 2022 15:47:16 -0400 [thread overview]
Message-ID: <20220901194716.GA19631@redhat.com> (raw)
In-Reply-To: <87zgfi6gzd.fsf@kataplop.net>
Hi -
> Thanks for everything! As a (very minor) contributor of the GCC-Rust, I
> can see how the CI is really helpful. The public-inbox looks also very
> interesting (Mark listed some of the nice features this tool offers,
> I've already looked at piem), thanks!
Our pleasure!
> > There are a few small-ticket items that we would dearly welcome
> > community assistance with. [...]
>
> I understand that the best would be to offer manpower, but you also
> mention funding. It's not clear (at least for me) how it's currently
> working
Basically, Red Hat has been covering all the direct costs, and folks
inside and outside the company have been working together to keep
things running.
> and how it would work if/when the project is accepted by the SFC.
This arrangement would let outside donors, even very small ones, pool
contributions toward future infrastructure projects.
> I don't feel qualified for any of the small-tickets you list but
> would still like to help if possible. If there's a way to donnate to
> the project, could you explain how?
If the SFC proposal is accepted, this will be straightforward.
> I guess this will be discussed during the upcoming Cauldron during
> Mark's presentation?
I believe so.
- FChE
next prev parent reply other threads:[~2022-09-01 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 19:18 Marc
2022-09-01 19:47 ` Frank Ch. Eigler [this message]
2022-09-01 20:47 ` Christopher Faylor
2022-09-02 11:10 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2022-08-30 18:03 Frank Ch. Eigler
2022-09-01 14:19 ` Elena Zannoni
2022-09-01 18:10 ` Christopher Faylor
2022-09-02 10:14 ` Mark Wielaard
2022-09-01 18:45 ` Corinna Vinschen
2022-09-01 18:54 ` Frank Ch. Eigler
2022-09-02 10:51 ` Mark Wielaard
2022-09-02 11:47 ` Mark Wielaard
2022-09-05 12:20 ` Dodji Seketeli
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=20220901194716.GA19631@redhat.com \
--to=fche@redhat.com \
--cc=dkm@kataplop.net \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=pono@sfconservancy.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).