MIME-Version: 1.0
In-Reply-To: <4FDDAA9F0200002500048597@gw.wicourts.gov>
References: <4FDDAA9F0200002500048597@gw.wicourts.gov>
Date: Sun, 17 Jun 2012 16:27:59 +0100
Message-ID: 
 <CA+OCxozggGgpNSEyhzGhQsatpvc1HApKgY7eOGd9ANk_zj+Lcg@mail.gmail.com>
Subject: Re: Some restructuring of the download section
From: Dave Page <dpage@pgadmin.org>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: "pgsql-www@postgresql.org" <pgsql-www@postgresql.org>
Content-Type: multipart/alternative; boundary=14dae9cfc7e6bf9aac04c2acb1f6

--14dae9cfc7e6bf9aac04c2acb1f6
Content-Type: text/plain; charset=ISO-8859-1

On Sunday, June 17, 2012, Kevin Grittner wrote:
>
>
> In terms of confusing entries, though, describing the non-yum option
> as a "one click installer" makes it sound like it is the fast and
> easy way to do this.  My experiences with the yum packages is that
> there are no clicks needed.  I type the apt-get command or pick the
> package in the GUI package manager and a few secons later I have a
> running PostgreSQL instance without any further interaction, and
> which will automatically be updated with new minor releases.  I think
> we should provide some guidance on the reasons one would want to pick
> one or the other.
>

(this is background info, not an argument against the proposed changes):

Well the whole point is that they are faster and easier to get started -
one package contains server, docs, GUI etc, and following a few clicks
everything is up and running. Personally I dislike the term 1-click
installer as it's clearly inaccurate (it's more like 5 clicks), but that's
the name that has become known and recognised.

The platform native packaging systems are marginally easier to update
(StackBuilder will update the installers), but have proven in the past to
confuse some users because it's hard to know what to install (though part
of what Magnus has done aims to make that easier), and they all install
software but don't do any of the setup for you - no initdb, no service
setup etc.

The reason the original design was implemented, and the installers were
written, is that this was a real problem that caused regular emails to
webmaster@postgresql.org and other places. We reduced that to practically
zero by putting the 'no-brainer' option at the top of the page.


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--14dae9cfc7e6bf9aac04c2acb1f6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br>On Sunday, June 17, 2012, Kevin Grittner  wrote:<blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<br>
In terms of confusing entries, though, describing the non-yum option<br>
as a &quot;one click installer&quot; makes it sound like it is the fast and=
<br>
easy way to do this. =A0My experiences with the yum packages is that<br>
there are no clicks needed. =A0I type the apt-get command or pick the<br>
package in the GUI package manager and a few secons later I have a<br>
running PostgreSQL instance without any further interaction, and<br>
which will automatically be updated with new minor releases. =A0I think<br>
we should provide some guidance on the reasons one would want to pick<br>
one or the other.<br>
</blockquote><div><br></div><div>(this is background info, not an argument =
against the proposed changes):</div><div><br></div><div>Well the whole poin=
t is that they are faster and easier to get started - one package contains =
server, docs, GUI etc, and following a few clicks everything is up and runn=
ing. Personally I dislike the term 1-click installer as it&#39;s clearly in=
accurate (it&#39;s more like 5 clicks), but that&#39;s the name that has be=
come known and recognised.</div>
<div><br></div><div>The platform native packaging systems are marginally ea=
sier to update (StackBuilder will update the installers), but have proven i=
n the past to confuse some users because it&#39;s hard to know what to inst=
all (though part of what Magnus has done aims to make that easier), and the=
y all install software but don&#39;t do any of the setup for you - no initd=
b, no service setup etc.<span></span></div>
<div><br></div><div>The reason the original design was implemented, and the=
 installers were written, is that this was a real problem that caused regul=
ar emails to <a href=3D"mailto:webmaster@postgresql.org">webmaster@postgres=
ql.org</a> and other places. We reduced that to practically zero by putting=
 the &#39;no-brainer&#39; option at the top of the page.</div>
<div><br></div><br><br>-- <br>Dave Page<br>Blog: <a href=3D"http://pgsnake.=
blogspot.com" target=3D"_blank">http://pgsnake.blogspot.com</a><br>Twitter:=
 @pgsnake<br><br>EnterpriseDB UK: <a href=3D"http://www.enterprisedb.com" t=
arget=3D"_blank">http://www.enterprisedb.com</a><br>
The Enterprise PostgreSQL Company<br><br>

--14dae9cfc7e6bf9aac04c2acb1f6--