public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Kelling <iank@fsf.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Moving sourceware to the Linux Foundation? No thanks.
Date: Wed, 28 Sep 2022 04:33:30 -0400	[thread overview]
Message-ID: <87pmff3my3.fsf@fsf.org> (raw)
In-Reply-To: <20220926195716.GD7916@redhat.com>


"Frank Ch. Eigler via Overseers" <overseers@sourceware.org> writes:

> Hi -
>
>> I see two important points that ought to be discussed on this topic.
>
> Thanks for joining the discussion.
>
>> The first is succession planning.  Sourceware is essentially a community
>> project with a relatively small number of people keeping it going.  It
>> needs trusted and capable people to step it to continue to maintain it.
>> Where are those people going to come from?  We shouldn't simply hope
>> that it will keep carrying on as before.
>
> Fair, we need to attend to recruiting more helpers.  (It was with this
> in mind that some folks got root on sourceware in the last few years.)
> With some moderate funding, the small amount of IT effort this place
> requires could be filled out with talented part-timers.  OTOH, it's
> not an emergency, and the system is not complicated, running
> off-the-shelf basic RHEL8 for the core stuff (git, mail, mailing
> lists, http, ssh, authentication).

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. There are currently 3 tech team members,
https://www.fsf.org/about/staff-and-board there's been about that many
for a long time, like a decade now, and we aren't going anywhere . GNU
infrastructure is a large part of every FSF tech team member's job that
we do full time. If you want to make succession plans, we should be part
of that planning.

-- 
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7  DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org

  parent reply	other threads:[~2022-09-28  8:47 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 [this message]
2022-09-28 10:08                   ` Frank Ch. Eigler
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=87pmff3my3.fsf@fsf.org \
    --to=iank@fsf.org \
    --cc=fche@redhat.com \
    --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).