Re: Adding PgLife link

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Adding PgLife link
Date: 2013-06-23 16:30:54
Message-ID: CABUevEy5XfY45-Ep9Ha+ERsEfyki7deL9xWmQkGLArKXqVqDiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Fri, Jun 21, 2013 at 9:00 PM, Jonathan S. Katz
<jonathan(dot)katz(at)excoventures(dot)com> wrote:
> On Jun 21, 2013, at 1:40 PM, Josh Berkus wrote:
>
>>
>>> 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.
>>
>> Well, I think we should link to it.
>
> I think if it is something that can help show more visibility into how the community works and thus by extension help grow it, we should profile it somewhere on the site.
>
> An alternative option to linking or hosting is to create a page on .org that keeps PgLife in an iframe. That way we can have the PgLife content on .org but do not need to fully maintain it. We would probably need to write some code on the .org frontend to ensure PgLife is up before loading it, but that maintenance should be minimal.

Ugh. That sounds like a really bad idea IMO. Iframes suck both to set
up and to use :) If we want to do that, we should just link to it and
be done.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Bruce Momjian 2013-06-23 18:15:15 Re: Adding PgLife link
Previous Message Magnus Hagander 2013-06-23 16:30:11 Re: Adding PgLife link