From: "Frank Ch. Eigler" <fche@redhat.com>
To: Karsten Wade <kwade@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: Looking for service/server operators
Date: Thu, 16 Mar 2017 19:40:00 -0000 [thread overview]
Message-ID: <20170316194025.GB26386@redhat.com> (raw)
In-Reply-To: <38cb7ae6-4463-d381-44ef-0a9d4c601b07@redhat.com>
Hi -
> I'm wondering who is responsible for what happens at sourceware.org?
Hey there, I guess.
> I was alerted that projects had migrated from fedorahosted.org, and
> I'm curious what all is hosted here now?
We recently welcomed elfutils, lvm2 (back), publican, plus all the
older GNU etc. stuff.
> I've also heard the hardware is seriously aging, and I'd like to
> work with someone to make sure that this service is taken care
> of. [...]
The hardware is around 5 years old, but is running reasonably well.
(16-core, E5620, 72GB-RAM, 3T disk). It may not be worthwhile to get
an only sligthly-better new box, as migration downtimes are a hassle.
But, not to look a gift horse in the mouth, what did you have in mind?
- FChE
next prev parent reply other threads:[~2017-03-16 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 19:15 Karsten Wade
2017-03-16 19:40 ` Frank Ch. Eigler [this message]
2017-03-16 19:54 ` Karsten Wade
2017-07-25 20:41 ` Karsten Wade
2017-07-26 15:33 ` Christopher Faylor
2017-07-26 16:50 ` Frank Ch. Eigler
2017-12-12 18:43 ` Karsten Wade
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=20170316194025.GB26386@redhat.com \
--to=fche@redhat.com \
--cc=kwade@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).