public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Fetter <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Git access?
Date: Tue, 10 Jun 2008 15:12:11 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <1213135511.17340.172.camel@jd-laptop>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<1213135511.17340.172.camel@jd-laptop>

On Tue, Jun 10, 2008 at 03:05:11PM -0700, Joshua D. Drake wrote:
> On Tue, 2008-06-10 at 15:00 -0700, David Fetter wrote:
> > On Tue, Jun 10, 2008 at 09:14:35PM +0200, Magnus Hagander wrote:
> > > > It's an interesting plan, but it's one that's preventing people
> > > > from using the service.  How about shelving that plan for the
> > > > moment and handing out access as needed to developers? :)
> > > 
> > > Please don't. Handing more access out in an uncontrolled way will
> > > give us a lot more work cleaning things up later.
> > 
> > With respect, I must disagree.  This resource is incredibly easy to
> > maintain--and practically useless--because nobody can get on there.
> 
> I think the point is, we don't want to give shell accounts out. Which is
> why we are waiting. That is something I can get behind. We don't need to
> be handing out yet more shell accounts.

Why not?  They can be revoked any time. 

Meanwhile, people's inability to use them is costing us.  People are
hosting projects outside our system, not because they don't like our
system, but because they can't get a workable SCM from pgfoundry or
anywhere else inside our system.

Cheers,
David.
-- 
David Fetter <[email protected]> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: [email protected]

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

view thread (12+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Git access?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox