public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Marc <dkm@kataplop.net>
To: fche@elastic.org
Cc: bkuhn@sfconservancy.org, overseers@sourceware.org,
	pono@sfconservancy.org, mark@klomp.org
Subject: Re: proposing Sourceware as Software Freedom Conservancy member project
Date: Thu, 01 Sep 2022 21:18:30 +0200	[thread overview]
Message-ID: <87zgfi6gzd.fsf@kataplop.net> (raw)
In-Reply-To: Yw5Q4b/2nqvAi3K4@elastic.org

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!

> This year, we set up a roadmap to improve the services for tracking
> and automation of email based patches and testing
> https://inbox.sourceware.org/overseers/YrLdfDWzq1T4k5xg@wildebeest.org/
> This resulted in the launch of several new or updated services
> (builder.sourceware.org, patchwork.sourceware.org and
> inbox.sourceware.org).  This didn't need any additional funds (except
> for the sourcehut mirror which costs $10 a month).  We are proud to
> operate these services with minimal costs so we can sustain them both
> in good and in bad years.  But that doesn't mean everything has to be
> done on a zero budget.  Financial contributions are more than welcome
> so that if the need arises we can contract for some unusual admin
> stuff or additions to services like bugzilla, buildbot, patchwork,
> public-inbox or sourcehut.
>
> There are a few small-ticket items that we would dearly welcome
> community assistance with.  This is just a draft of a draft, just to
> give you an idea of the scope.  No gigaprojects, just community scale:
> helping each other out.  That kind of low-budget efficiency seems to
> be a perfect match for SFC.

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, and how it would work if/when the project is accepted by the
SFC. 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?

I guess this will be discussed during the upcoming Cauldron during
Mark's presentation?

Thanks again for all your work :)
Marc

             reply	other threads:[~2022-09-01 19:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 19:18 Marc [this message]
2022-09-01 19:47 ` Frank Ch. Eigler
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=87zgfi6gzd.fsf@kataplop.net \
    --to=dkm@kataplop.net \
    --cc=bkuhn@sfconservancy.org \
    --cc=fche@elastic.org \
    --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).