public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@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: <200005301531.IAA15889@ferrule.cygnus.com> (raw)
In-Reply-To: <200005301446.KAA08704@devserv.devel.redhat.com>

Jim> I think at this point it might be a question of what do we want
Jim> out of Red Hat?  (watch out, there is a "careful what you wish
Jim> for, you might get it" element to this).  Do we want IS to leave
Jim> us alone?  Do we want them to handle everything (and if so can
Jim> they provide the kind of service we're looking for)?  Do any of
Jim> us want to be (full/part time or consultant) sysadmins?  Do we
Jim> want to farm out specific tasks to sysadmin?  Do we want to
Jim> automate those tasks so they don't need farming out?

I think:

* We should have someone work on sourceware full time.  As I see it
  the work would involve automating things to the extent possible, so
  that project maintainers wouldn't need constant help to do simple
  things (tweak mailing lists, user maintenance, etc)
* We should get IS to help if they agree with our agenda
  (they didn't always)
* I don't want to be a sysadmin ever again

Tom

WARNING: multiple messages have this Message-ID

From: Tom Tromey <tromey@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:34:00 -0000	[thread overview]
Message-ID: <200005301531.IAA15889@ferrule.cygnus.com> (raw)
Message-ID: <20000530083400.Rd07LXifmBYCCE0CckzpkGWPN_UvnGbR7AVX1XuItYw@z> (raw)
In-Reply-To: <200005301446.KAA08704@devserv.devel.redhat.com>

Jim> I think at this point it might be a question of what do we want
Jim> out of Red Hat?  (watch out, there is a "careful what you wish
Jim> for, you might get it" element to this).  Do we want IS to leave
Jim> us alone?  Do we want them to handle everything (and if so can
Jim> they provide the kind of service we're looking for)?  Do any of
Jim> us want to be (full/part time or consultant) sysadmins?  Do we
Jim> want to farm out specific tasks to sysadmin?  Do we want to
Jim> automate those tasks so they don't need farming out?

I think:

* We should have someone work on sourceware full time.  As I see it
  the work would involve automating things to the extent possible, so
  that project maintainers wouldn't need constant help to do simple
  things (tweak mailing lists, user maintenance, etc)
* We should get IS to help if they agree with our agenda
  (they didn't always)
* I don't want to be a sysadmin ever again

Tom

  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   ` Jeffrey A Law
2000-05-30  8:05     ` Jeffrey A Law
2000-12-30  6:08   ` Tom Tromey [this message]
2000-05-30  8:34     ` Tom Tromey

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=200005301531.IAA15889@ferrule.cygnus.com \
    --to=tromey@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).