Re: patch - BigSQL packages on Download - Mailing list pgsql-www

From Dave Page
Subject Re: patch - BigSQL packages on Download
Date
Msg-id CA+OCxoxhWs_egW2ETzVkocxSE4Tv67nwFUOq3vYdny+-QUSODQ@mail.gmail.com
Whole thread Raw
In response to patch - BigSQL packages on Download  ("Rader, David" <davidr@openscg.com>)
Responses Re: patch - BigSQL packages on Download  (Dave Page <dpage@pgadmin.org>)
Re: patch - BigSQL packages on Download  ("Rader, David" <davidr@openscg.com>)
Re: patch - BigSQL packages on Download  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: patch - BigSQL packages on Download  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-www
Hi

On Fri, Apr 29, 2016 at 5:15 PM, Rader, David <davidr@openscg.com> wrote:
> Attached is a proposed patch for the Windows, OS X, and Linux download pages
> to include the BigSQL.org packages for download.
>
> Please review for approval

I think there are a number of issues with this:

- The descriptions should be kept much shorter, a couple of lines at
most like the other entries.

- There are factual inaccuracies - your toolchain is not 100% Open
Source as stated. BitRock InstallBuilder is closed source.

- I don't believe one platforms description should discuss other
platforms - e.g, lose "This distribution is consistent across Windows,
Mac OS X, and Linux". If the general feeling is that it should be
included, then it should be added for the EDB packages as well.

- There should not be any mention of sandboxes on these pages. These
are intended to be very simple pages getting users up and running with
minimal confusion, not listing every possible option available to
them.

In general though, I do not feel it's appropriate to list these
packages at all, given that they make silent outbound HTTP calls
during installation, without the user being made aware of that or
being given any option to object. That could easily be considered a
privacy issue by people, one that may come back to bite us for hosting
the downloads on our primary listing.

I'm also somewhat concerned by some Python services that were left
running when I tried out the Mac version. Why would I have any Python
services running when I've installed PostgreSQL? If they're used by
your package manager, why are they not started and stopped as
required?

[Opinions are mine as a community member, not my employers]

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

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



pgsql-www by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: conference slides in wiki
Next
From: Dave Page
Date:
Subject: Re: patch - BigSQL packages on Download