Re: Adding PgLife link

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Adding PgLife link
Date: 2013-06-21 15:39:47
Message-ID: 20130621153947.GC20414@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Fri, Jun 21, 2013 at 03:53:57PM +0100, Dave Page wrote:
> > That is not Bruce's decision to make, it is the decision of the
> > sysadmin team who are responsible for the maintenance and day to day
> > running of all postgresql.org services. The sysadmin team will only
> > provide hosting for services that can be properly and efficiently
> > managed.
>
> Huh - wrote that pre-coffee and just realised it may be taken the
> wrong way. I'm not saying pglife can't be properly and efficiently
> managed - I don't know, I have no idea how it's been built. Just that
> the sysadmin team would be looking at that before taking on another
> service to maintain.

Agreed, and I don't think PgLife can be efficiently managed. PgLife
uses Perl, CPAN modules, Javascript, Procmail, and cron jobs, and these
would need to be maintained by the sysadmin team. Frankly, there
doesn't seem to be enough interest in even linking to PgLife, so I don't
see how having the sysadmin team maintain it makes any sense.

I do think the new display of unrelease backbranch commits will be
helpful, and I will keep making improvements as people suggest things.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Josh Berkus 2013-06-21 17:40:45 Re: Adding PgLife link
Previous Message Dave Page 2013-06-21 14:53:57 Re: Adding PgLife link