From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Ian Kelling <iank@fsf.org>
Subject: Re: Moving sourceware to the Linux Foundation? No thanks.
Date: Wed, 28 Sep 2022 06:08:50 -0400 [thread overview]
Message-ID: <YzQdMuGc4QVw021c@elastic.org> (raw)
In-Reply-To: <87pmff3my3.fsf@fsf.org>
Hi -
> There is already a built in succession plan you all seem to be ignoring.
> GNU already separately hosts most of same infrastructure that sourceware
> does. If sourceware volunteers all stepped down tomorrow, GNU would be
> ready to immediately step up and host servers, maintain services,
> recruit new volunteers, and that effort would likely be lead by FSF
> sysadmin staff like me. [...]
Excellent point.
In case an emergency occurred, there exists a pool of people who would
certainly jump into help. Depending on the nature of the problem,
with documented SOPs, someone could step in in situ. For a simple
service like sourceware, it's not rocket science. In extremis,
restart things from distributed backups. The essentials of sourceware
content are already exposed for duplication (source repositories,
email archives, release tarballs).
- FChE
next prev parent reply other threads:[~2022-09-28 10:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yw5aTCLyYx8qqN3W@wildebeest.org>
2022-08-31 22:19 ` Proposing Sourceware as SFC member project Jose E. Marchesi
2022-09-01 8:28 ` Mark Wielaard
2022-09-02 18:51 ` Daniel Pono Takamori
2022-09-03 14:07 ` Karen M. Sandler
2022-09-03 16:38 ` Mark Wielaard
2022-09-18 19:42 ` Moving sourceware to the Linux Foundation? No thanks Christopher Faylor
2022-09-25 22:31 ` Mark Wielaard
2022-09-26 14:07 ` Ian Lance Taylor
2022-09-26 17:05 ` Christopher Faylor
2022-09-26 19:57 ` Frank Ch. Eigler
2022-09-27 13:03 ` Carlos O'Donell
2022-09-28 8:53 ` Ian Kelling
2022-10-02 21:15 ` Mark Wielaard
2022-09-28 8:33 ` Ian Kelling
2022-09-28 10:08 ` Frank Ch. Eigler [this message]
2022-09-26 21:53 ` Moving sourceware into the future Mark Wielaard
2022-09-27 17:12 ` Daniel Pono Takamori
2022-09-26 22:21 ` Moving sourceware to the Linux Foundation? No thanks Carlos O'Donell
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=YzQdMuGc4QVw021c@elastic.org \
--to=fche@elastic.org \
--cc=iank@fsf.org \
--cc=overseers@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).