From: Carlos O'Donell <carlos@redhat.com>
To: overseers@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: Choice of distribution for new sourceware.org server?
Date: Thu, 06 Feb 2020 01:45:00 -0000 [thread overview]
Message-ID: <bf2e3d28-2ff6-6052-a029-d0548eacb740@redhat.com> (raw)
In-Reply-To: <20200206013050.GA16275@cgf.cx>
On 2/5/20 8:30 PM, Christopher Faylor wrote:
> On Wed, Feb 05, 2020 at 08:05:01PM -0500, Carlos O'Donell wrote:
>> May I ask why CentOS 8 was chosen as the distribution choice for
>> the new sourceware.org servers?
>>
>> Is there any reason that RHEL 8 was not chosen?
>>
>> Alternatively Fedora Server on a faster update cycle?
>>
>> Was there any requirement or discussion around which distribution
>> to choose for the new server?
>>
>> I can see RHEL 8 serving as a better platform than CentOS 8, particularly
>> if Red Hat donates the licenses.
>>
>> Likewise using Fedora Server would keep all of our services running on
>> the latest distribution with access to new server-side tooling for CI.
>>
>> Thank you for your time!
>
> I have suggested Fedora in the past and would be happy to be using it.
I would also be happy to see us use Fedora.
> I don't know what the difference would be between CentOS 8 and RHEL 8
> though.
For us?
* Directly faster security updates since CentOS 8 lags RHEL.
* Access to ELS if we want to keep the server alive longer.
* Support for things we don't have the time to fix or are outside our scope (kernel bugs).
- Usually here we can rely on internal access to Red Hat experts.
Do these things matter to us?
Otherwise dog-fooding Fedora Server would give us the latest packages
for services that sourceware could offer, but we'd have to update once
a year. It would force us to actively track the software we're using and
look at well supported alternatives e.g. postfix + mailman/public inbox vs.
qmail + ezmlm.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-02-06 1:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 1:05 Carlos O'Donell
2020-02-06 1:30 ` Christopher Faylor
2020-02-06 1:34 ` Frank Ch. Eigler
2020-02-06 1:51 ` Carlos O'Donell
2020-02-06 2:02 ` Frank Ch. Eigler
2020-02-06 2:16 ` Carlos O'Donell
2020-02-06 14:49 ` Frank Ch. Eigler
2020-02-06 15:10 ` Carlos O'Donell
2020-02-06 15:19 ` Frank Ch. Eigler
2020-02-06 16:36 ` Carlos O'Donell
2020-02-06 16:46 ` Christopher Faylor
2020-02-06 16:49 ` Frank Ch. Eigler
2020-02-06 1:45 ` Carlos O'Donell [this message]
2020-02-06 6:05 ` Christopher Faylor
2020-02-06 14:50 ` Carlos O'Donell
2020-02-06 15:11 ` Lukas Berk
2020-02-06 15:22 ` Carlos O'Donell
2020-02-06 15:20 ` Christopher Faylor
2020-02-06 17:05 ` Carlos O'Donell
2020-02-06 18:28 ` Joseph Myers
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=bf2e3d28-2ff6-6052-a029-d0548eacb740@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@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).