From: Jeffrey A Law <law@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: rosalia@galassi.org, overseers@sourceware.cygnus.com, paulb@cygnus.com
Subject: Re: an article that talks about sourcefourge and itanium
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <7920.959698486@upchuck> (raw)
In-Reply-To: <200005301446.KAA08704@devserv.devel.redhat.com>
In message < 200005301446.KAA08704@devserv.devel.redhat.com >you write:
>
> I think at this point it might be a question of what do we want out of
> Red Hat? (watch out, there is a "careful what you wish for, you might
> get it" element to this). Do we want IS to leave us alone? Do we
> want them to handle everything (and if so can they provide the kind of
> service we're looking for)? Do any of us want to be (full/part time
> or consultant) sysadmins? Do we want to farm out specific tasks to
> sysadmin? Do we want to automate those tasks so they don't need
> farming out?
At one time we wanted sysadmin basically out of the loop (except for backups),
that was mostly because sysadmin was unwilling/unable to provide the kind of
services we needed (high volume mail, shell access for some external folks,
potential root access for some folks, etc etc).
I don't know if the climate in sysadmin has changed enough that we would
want further involvement from the sysadmin staff.
I still believe that if someone wants to take on sourceware as an official
part/full time task that some kind of arrangement can be made.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: rosalia@galassi.org, overseers@sourceware.cygnus.com, paulb@cygnus.com
Subject: Re: an article that talks about sourcefourge and itanium
Date: Tue, 30 May 2000 08:05:00 -0000 [thread overview]
Message-ID: <7920.959698486@upchuck> (raw)
Message-ID: <20000530080500.BihLuFjK8RNvc2F0rkdCWQdaBRm6CTJdhRDmlnqJZ-o@z> (raw)
In-Reply-To: <200005301446.KAA08704@devserv.devel.redhat.com>
In message < 200005301446.KAA08704@devserv.devel.redhat.com >you write:
>
> I think at this point it might be a question of what do we want out of
> Red Hat? (watch out, there is a "careful what you wish for, you might
> get it" element to this). Do we want IS to leave us alone? Do we
> want them to handle everything (and if so can they provide the kind of
> service we're looking for)? Do any of us want to be (full/part time
> or consultant) sysadmins? Do we want to farm out specific tasks to
> sysadmin? Do we want to automate those tasks so they don't need
> farming out?
At one time we wanted sysadmin basically out of the loop (except for backups),
that was mostly because sysadmin was unwilling/unable to provide the kind of
services we needed (high volume mail, shell access for some external folks,
potential root access for some folks, etc etc).
I don't know if the climate in sysadmin has changed enough that we would
want further involvement from the sysadmin staff.
I still believe that if someone wants to take on sourceware as an official
part/full time task that some kind of arrangement can be made.
jeff
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Mark Galassi
2000-05-28 19:17 ` Mark Galassi
2000-12-30 6:08 ` Jim Kingdon
2000-05-30 7:46 ` Jim Kingdon
2000-12-30 6:08 ` Tom Tromey
2000-05-30 8:34 ` Tom Tromey
2000-12-30 6:08 ` Jeffrey A Law [this message]
2000-05-30 8:05 ` Jeffrey A Law
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=7920.959698486@upchuck \
--to=law@cygnus.com \
--cc=kingdon@redhat.com \
--cc=overseers@sourceware.cygnus.com \
--cc=paulb@cygnus.com \
--cc=rosalia@galassi.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).