| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Create a new governance directory page which centralizes access to the
various existing pages for project governance teams and committees. In
passing, also move some content from the wiki to their own pg.o pages
(committers, sysadmins), and create non-existing pages (contributors
committee).
There are undoubtedly some missed opportunities here for general
improvement as well as other unmentioned governance groups, but this is
a good start.
|
|
Moving forwards we'll have three types of sponsors:
- Contributing - those that the sponsor team are responsible for.
- Financial - those who donate to an NPO.
- Servers - those who provide servers/infrastructure.
For the financial sponsors, there are a few rules:
- "NPO" means a recognised NPO, (which includes SPI and PGCA).
- Each NPO may choose whether or not to list any sponsors on this page.
- Each NPO may define the criteria under which sponsors are listed, and
any levels they wish to use.
- Conference/event sponsorship does not count; it must be sponsorship of the
organisation itself.
- Sponsors may be listed once under each NPO they have donated to.
Note that the same sponsor may be listed in any or all of the categories
(contributing, financial, servers).
Patch by myself and Jonathan.
|
|
Once someone has fixed the signups, we should of course re-enable it,
but "no link" is better than a broken link.
|
|
There were no direct links to the CommitFest application from
the developers section, even though CommitFest are a key part of
PostgreSQL development. This adds said links, and provides a brief
explanation of what CommitFest are.
Reviewed-by: Magnus Hagander <magnus@hagander.net>
|
|
eccfb71c did not correctly invite people who were not in the
allow-listed domains. This uses a "shared join" link that
allows this to occur.
This is considered a temporary fix to ensure new users can still
sign up for the community Slack account. A future commit will
direct people to a better solution.
Reported-by: Stephen Frost <sfrost@snowman.net>
|
|
This pointed at a previous resource used to moderate sign-in that
has sinced been removed.
Author: Melih Mutlu <m.melihmutlu@gmail.com>
Author: Jonathan Katz <jonathan.katz@excoventures.com>
|
|
* Move links to current manuals to /docs/, decommission /docs/manuals/
* Add link to /docs/current/ with a large button
* Add links to /docs/devel/ at the bottom of the version table
* Remove translated manuals from left nav menu, since they are in the
right one
* Remove redundant wording around "comprehensive manual"
* Clean up some incorrect template tags
Discussion: https://www.postgresql.org/message-id/CABUevEymaWDL4JywHxBDBATUUPPrAf4_tGwin4CtGFdQ5tx5Hg@mail.gmail.com
|
|
|
|
The French docs had one link in http and one in https as noted by
Lætitia. In passing I also adjusted the japanese to link to the https
version directly as one is available. The remaining one (Chinese) does
not appear to have a responding https server, so that one is left as
http.
|
|
- Don't use inline event handlers
- Simplify some of the wording
- Replace the package download list with nice buttons
Design by me & Jonathan, code by me, review by Jonathan and others.
|
|
This provides information about other projects that people can
contribute to outside of the core PostgreSQL software. Includes
descriptions of each project, how they are used, and how one can
get involved.
Authors: Andreas 'ads' Scherbaum <ads@pgug.de>, myself
|
|
|
|
...because this is what the page actually is, and it may be clearer
to people navigating the website.
|
|
Some this disappeared, likely during the conversion to the new website.
This adds the FAQ page back in with some fresh content.
|
|
|
|
This creates a consolidated area to reference all of the notes from
previous releases of PostgreSQL, as current releases only keep the
the notes for that specific major release of PostgreSQL.
|
|
Changes by myself and Jonathan Katz
Review by Jonathan Katz and Daniel Gustafsson
|
|
|
|
|
|
In a quest to reach pep8, use spaces to indent rather than tabs.
|
|
While the permanent redirect will fix this over the course of time,
it is still better that we do not reference the old path from pgweb.
|
|
|
|
|
|
|
|
|
|
This had dropped off after the site refresh, but should be there.
|
|
This takes into account some pages that have been deprecrated,
some new pages, and some updated URLs.
|
|
Part of the website refresh; this points the "History" page to
the current version of the documentation, using "current" as
the pointer.
|
|
render_to_response does not work on newer django, so it needs to be
replaced. And using a speicfic context actually overcomplicates things,
it's easier to just use a wrapper function. For those cases where we
don't need NavContext, just use render() (the new shortcut function from
django), which also removes the need to use RequestContext.
|
|
This happens after a git gc which moves this into packed-refs. So when
this happens, look in packed-refs. If packed-refs also cannot be found,
just return a made up value instead of crashing.
|
|
|
|
Publish the community recognition guidelines developed by the PostgreSQL Core
Committee from a navigation off of the "Community" section. Add URLs from
several other pages on the PostgreSQL website in order to access the guidelines:
* Donate
* Events
* User Groups
Additionally, this patch updates the contact email address for donation questions
to the PostgreSQL Funds Group.
|
|
Also noted by Christoph Berg
|
|
One link was updated and one missed in
df4a433b195a26393f82aad14d22147b9e63c069. This makes them consistent.
Pavel Luzanov
|
|
|
|
In passing make it require ssl, make it no longer csrf-exempt,
and make it require a login so we don't let unauthenticated emails
through.
|
|
The pwn module has never been used, as the pwn are simply sent to
-announce and nothing else. We've kept the code and model around for
doing it on the site for years now and it's unused, so let's remove it
to cut down on maintenance cost.
|
|
Move manage.py up one step, set up a new wsgi.py file, and adjust
relative paths that refer to other directories for the new project
layout that we need to use in django 1.8.
|
|
|
|
link but it is for sure better than pointing to 9.2.2...
|
|
|
|
|
|
This will allow us to increase the cache times in the browser for our
CSS, which almost never changes.
Enables a new value to be used in templates, {{gitrev}}, which can be
used to bust pretty much any URL. We could do this for all the images
in the templates as well, but since most of them almost never change,
we'll just enable it manually for each individual image as it becomes
necessray - or just use a ?1, ?2 etc for those.
Enabled by default for CSS and JavaScript links, since those are much
more likely to be changed without having the URL changed.
Cache times aren't increased yet - we'll do that later one we're sure
that all existing caches are expired first.
|
|
This new page is served from the archives backend, and has been enhanced
to contain the combination of the contents of both pages.
|
|
Jonathan Katz
|
|
|
|
This also changes the main URL to look at events to be /about/events/
instead of /about/eventsarchive/, and reuses /about/eventsarchive/ to
be the actual achive. Also separates out the training archive to it's
own page at /about/eventsarchive/training/, for easier browsing.
|
|
|
|
|
