This information can be useful when trying to debug issues with the
community auth and the wonders of distributed data...
No actual django model is created because django still doesn't support
multi-column primary keys. Thus no tool to use the data yet other than
psql.
This is primarily to enable the "make STYLE=website html" build
option of the PostgreSQL docs, as the pgweb docs page uses
the "base.css" file to render the documentation. By updating the
dynamic doc.css generation file, we can allow the builders of the
documentation to better preview what their documentation will look
like when it is loaded onto the website.
Presently, the dynamic "docs.css" is unused in pgweb or the core
project, and as those are the two biggest consumers of the
documentation styles, this is an apparent safe vector to make this
change.
Preivously the requirement was "should not have 50% or more" members
from a single company, which basically ruled out any organisation of two
people. This was never the intention, so instead change to say "no more
than 50%", which specifically allows for the case of exactly half.
Raising a generic exception generates a http 500 internal error and a
stackdump. Instead raising PermissionDenied appopriately turns it into a
http 403 forbidden response.
Per discussion in $THREAD, it Survey is unmaintained. While it offers
some nice user interactivity, because it is unmaintained it should not
be visible on the website.
It is only commented out, so that we can re-enable in the future. The
archives will remain available, albeit obfuscated.
Thread: https://postgr.es/m/BBF56CF4-2065-45C5-B61F-D616F0CB2743%40yesql.se
This was partially implemented through the system, and given that the
community auth system already assumes email is unique there is no need
to not expose it to the actual login process as well.
When a new PostgreSQL branch is created, any "devel" notes for that branch
become immediately unavailable, which would make any shared devel links around
that dead.
This adjusts this logic such that any release notes for a release, beta or
otherwise, is now available by redirect the user to the release notes' permanent
home.
Reported By: Andres Freund <andres@anarazel.de>, who also mostly authored the
patch over email.
