MIME-Version: 1.0
References: <20190122140025.GA27301@msg.df7cb.de>
 <20190130154803.GF4383@msg.df7cb.de>
 <20190227150932.GE25213@msg.df7cb.de>
In-Reply-To: <20190227150932.GE25213@msg.df7cb.de>
From: Dave Page <dpage@pgadmin.org>
Date: Wed, 8 Jul 2020 14:08:34 +0100
Message-ID: 
 <CA+OCxowkHqCxk5A4e1VRYOLzj7s+_Pm47WZ2=qpbUz7A2BzO2A@mail.gmail.com>
Subject: Re: apt.postgresql.org django app for www.postgresql.org
To: Christoph Berg <myon@debian.org>,
 PostgreSQL WWW <pgsql-www@postgresql.org>,
	Adrian Vondendriesch <adrian.vondendriesch@credativ.de>
Content-Type: multipart/alternative; boundary="000000000000cd4f0405a9edce86"
Precedence: bulk

--000000000000cd4f0405a9edce86
Content-Type: text/plain; charset="UTF-8"

Hi

On Wed, Feb 27, 2019 at 3:09 PM Christoph Berg <myon@debian.org> wrote:

> Re: To PostgreSQL WWW 2019-01-30 <20190130154803.GF4383@msg.df7cb.de>
> > Updated for python3. I had to fix several places where {{package}} was
> > rendered as "Package Object". The new syntax is {{package.package}}.
>
> Ping?
>

 I spent a bunch of time playing with this, as I intend to get repo
browsing for both Yum and Apt onto the website.

There was quite a bit of work to do to get it working with modern versions
of Django and Python 3. Once I got through enough of that to start looking
at the actual functionality what I found was *really* comprehensive.
Unfortunately I think there's actually far more there than we should put on
the main website.

- I think the QA section is clearly something that's aimed at you as
maintainers of the apt repos. This definitely doesn't belong on the main
website in my opinion.

- The madison interface is also interesting (academically), but I think is
of little use to the vast majority of our users; I'm not even sure that the
majority of Debian/Ubuntu users would know about rmadison.

- Similarly, I think the binary and source package pages are far more
comprehensive than most of our users need or would care about.

One of the biggest barriers of adoption to PostgreSQL is the perceived
complexity, including that of getting it up and running. That's why I'm
spending a lot of time at the moment trying to simplify and clarify the
download and installation processes. I think what we have in this patch
will simply be information overload for most of our users.

My suggestion is that we incorporate a relatively simple browser into the
main website, which allows users to easily browse the available packages
and see the details of them. I already have the repo scanning part of that
done for both apt and yum, generating JSON output in a way that can be
integrated with our download server sync process, which can load that into
the website database.

I would support a separate site (probably under apt.enterprisedb.com) that
supports the level of functionality you have in your patch; and I think
much, if not all of the code you currently have could be used for that.
This could of course be linked from the main website.

Thanks.

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

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

--000000000000cd4f0405a9edce86
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Wed, Feb 27, 2019 at 3:09 PM Christoph Berg &lt;=
<a href=3D"mailto:myon@debian.org" target=3D"_blank">myon@debian.org</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Re: To =
PostgreSQL WWW 2019-01-30 &lt;<a href=3D"mailto:20190130154803.GF4383@msg.d=
f7cb.de" target=3D"_blank">20190130154803.GF4383@msg.df7cb.de</a>&gt;<br>
&gt; Updated for python3. I had to fix several places where {{package}} was=
<br>
&gt; rendered as &quot;Package Object&quot;. The new syntax is {{package.pa=
ckage}}.<br>
<br>
Ping?<br></blockquote><div><br></div><div>=C2=A0I spent a bunch of time pla=
ying with this, as I intend to get repo browsing for both Yum and Apt onto =
the website.</div><div><br></div><div>There was quite a bit of work to do t=
o get it working with modern versions of Django and Python 3. Once I got th=
rough enough of that to start looking at the actual functionality what I fo=
und was *really* comprehensive. Unfortunately I think there&#39;s actually =
far more there than we should put on the main website.</div><div><br></div>=
<div>- I think the QA section is clearly something that&#39;s aimed at you =
as maintainers of the apt repos. This definitely doesn&#39;t belong on the =
main website in my opinion.</div><div><br></div><div>- The madison=C2=A0int=
erface is also interesting (academically), but I think is of little use to =
the vast majority of our users; I&#39;m not even sure that the majority of =
Debian/Ubuntu users would know about rmadison.</div><div><br></div><div>- S=
imilarly, I think the binary and source package pages are far more comprehe=
nsive than most of our users need or would care about.</div><div><br></div>=
<div>One of the biggest barriers of adoption to PostgreSQL is the perceived=
 complexity, including that of getting it up and running. That&#39;s why I&=
#39;m spending a lot of time at the moment trying to simplify and clarify t=
he download and installation processes. I think what we have in this patch =
will simply be information overload for most of our users.</div><div><br></=
div><div>My suggestion is that we incorporate a relatively simple browser i=
nto the main website, which allows users to easily browse the available pac=
kages and see the details of them. I already have the repo scanning part of=
 that done for both apt and yum, generating JSON output in a way that can b=
e integrated with our download server sync process, which can load that int=
o the website database.</div><div><br></div><div>I would support a separate=
 site (probably under <a href=3D"http://apt.enterprisedb.com">apt.enterpris=
edb.com</a>) that supports the level of functionality you=C2=A0have in your=
 patch; and I think much, if not all of the code you currently have could b=
e used for that. This could of course be linked from the main website.</div=
></div><div><br></div><div>Thanks.</div><div><br></div>-- <br><div dir=3D"l=
tr">Dave Page<br>Blog: <a href=3D"http://pgsnake.blogspot.com" target=3D"_b=
lank">http://pgsnake.blogspot.com</a><br>Twitter: @pgsnake<br><br>Enterpris=
eDB UK: <a href=3D"http://www.enterprisedb.com" target=3D"_blank">http://ww=
w.enterprisedb.com</a><br>The Enterprise PostgreSQL Company<br></div></div>

--000000000000cd4f0405a9edce86--