diff --git a/pgweb/util/contexts.py b/pgweb/util/contexts.py index 7d13862f..35dc384a 100644 --- a/pgweb/util/contexts.py +++ b/pgweb/util/contexts.py @@ -6,6 +6,7 @@ from django.conf import settings sitenav = { 'about': [ {'title': 'About', 'link': '/about/'}, + {'title': 'Governance', 'link': '/about/governance/'}, {'title': 'Policies', 'link': '/about/policies/'}, {'title': 'Feature Matrix', 'link': '/about/featurematrix/'}, {'title': 'Donate', 'link': '/about/donate/'}, @@ -54,6 +55,7 @@ sitenav = { 'developer': [ {'title': 'Developers', 'link': '/developer/'}, {'title': 'Core Team', 'link': '/developer/core/'}, + {'title': 'Committers', 'link': '/developer/committers/'}, {'title': 'Roadmap', 'link': '/developer/roadmap/'}, {'title': 'Coding', 'link': '/developer/coding/'}, {'title': 'CommitFests', 'link': 'https://commitfest.postgresql.org'}, diff --git a/templates/index.html b/templates/index.html index 655918bc..b833e702 100644 --- a/templates/index.html +++ b/templates/index.html @@ -40,6 +40,7 @@ + diff --git a/templates/pages/about/governance.html b/templates/pages/about/governance.html new file mode 100644 index 00000000..b838a3c5 --- /dev/null +++ b/templates/pages/about/governance.html @@ -0,0 +1,75 @@ +{%extends "base/page.html"%} +{%block title%}Governance{%endblock%} + +{%block contents%} +
+This page lists links to pages for the various teams and committees that +comprise the governance hierarchy of the project. Please see the individual +linked pages for more information about each group, including membership +and charter. +
+ ++ The PostgreSQL Core Team + (Core) is the central arbiter of PostgreSQL project + policy and governance. +
+ ++ The PostgreSQL Sysadmin Team + (PGInfra) runs all of the postgresql.org infrastructure. This includes + a wide variety of public and non-public services. +
+ ++ The PostgreSQL Committers + are the people with access to push to the + git repository. +
+ ++ The PostgreSQL Security Team + presides over the reporting and fixing of vulnerabilities related + to PostgreSQL and closely related projects. For security vulnerabilities + in PostgreSQL or any of the installers linked from the + PostgreSQL download page, please email + security@postgresql.org. + For reporting non-security bugs, please visit the + Report a Bug page. + If you are unsure if an issue is a security vulnerability, please err on the + side of caution and email + security@postgresql.org. +
+ ++ The Code of Conduct Committee + are the people who receive and investigate all complaints related to the + PostgreSQL Code of Conduct. +
+ ++ The Contributors Committee + curates the Contributor Profiles + page. +
+ ++ The Sponsors Committee + maintains the Sponsors pages. +
+ ++ Several Non Profit Organizations + serve the PostgreSQL Project in a variety of ways. +
+ +{%endblock%} diff --git a/templates/pages/about/governance/contributors.html b/templates/pages/about/governance/contributors.html new file mode 100644 index 00000000..a7fd55a7 --- /dev/null +++ b/templates/pages/about/governance/contributors.html @@ -0,0 +1,36 @@ +{%extends "base/page.html"%} +{%block title%}Contributors Committee{%endblock%} +{%block contents%} + ++ All Contributor recognition is curated by the Contributor Committee, + who decides on the status of each Contributor, or potential Contributor, + on an individual basis. Decisions are made in accordance with the + Recognized Contributors policy. + The decision of the committee is final unless overridden by the + Core Team. The Contributor Committee strives to meet regularly to + discuss the current pool of candidates. The + Contributor Profiles page is + updated promptly after any decisions are made with respect to additions + or changes. +
+ ++ The current members are: +
++ The size and membership of the Committee is self determined, + but ratified by a simple majority vote of the Core Team. Generally + the goal is that there be a minimum of three people, with no single + company employing a majority of the committee membership. +
+ +{%endblock%} diff --git a/templates/pages/about/governance/sysadmin.html b/templates/pages/about/governance/sysadmin.html new file mode 100644 index 00000000..0f043c05 --- /dev/null +++ b/templates/pages/about/governance/sysadmin.html @@ -0,0 +1,37 @@ +{%extends "base/page.html"%} +{%block title%}Infrastructure Team{%endblock%} +{%block contents%} + ++ The Infrastructure team is responsible for running all of the + postgresql.org infrastructure. This includes a wide variety of + public and non-public services. PostgreSQL website development + is discussed on the + pgsql-www mailing list. + Source code for the postgresql.org web site is stored in a public + GIT repository. +
+ ++ The following people are part of the sysadmin team running the + postgresql.org infrastructure. +
++ In case you want to reach out to the Infrastructure team, please + contact us at sysadmins@lists.postgresql.org +
+ +{%endblock%} diff --git a/templates/pages/about/policies.html b/templates/pages/about/policies.html index 79c39170..9cff1e4a 100644 --- a/templates/pages/about/policies.html +++ b/templates/pages/about/policies.html @@ -45,6 +45,7 @@+ The PostgreSQL Contributor Profiles page + includes people who have made substantial, long-term contributions of time + and effort to the PostgreSQL project. One-time-only or short-term contributions + are not usually considered adequate for listing, unless they involve quite large + amounts of code and time. Financial contributions get listed on the + Sponsors pages, not here. +
+ ++ The Contributor Profiles page + lists Core Team members and two levels of PostgreSQL Contributors: +
++ This section lists people who were in the Core Team, Major Contributor, + or Contributor section, but have stopped contributing for an extended + period of time. +
++ Contributions to the PostgreSQL Project that may be considered by the + committee include, but are not limited to: +
++ The current method of choosing who qualifies as a Contributor is via + simple majority vote of those on the committee. The size and membership + of the Committee is self determined, but ratified by a simple majority + vote of the Core Team. Generally the goal is that there be a minimum of + three people, with no single company employing a majority of the + committee membership. +
+ +{%endblock%} diff --git a/templates/pages/developer/committers.html b/templates/pages/developer/committers.html new file mode 100644 index 00000000..c7267e04 --- /dev/null +++ b/templates/pages/developer/committers.html @@ -0,0 +1,98 @@ +{%extends "base/page.html"%} +{%block title%}Committers{%endblock%} +{%block contents%} + ++ This is the current list of people with access to push to the + git repository. + For technical details on how committing works, see + Committing with Git. + This is just a list of people who currently have access to push to git; for + information on current and previous contributors, see the contributor profiles + section of the web site. +
+ ++ The names are listed here in order of first commit or when added + as a committer, oldest first; this isn't intended to imply anything + about depth of contribution. +
++ Hundreds of developers have successfully contributed work to PostgreSQL + over decades, many acting as individuals, though also many representing + academic institutions and both user and vendor companies. Both the "Author" + and "Committer" fields of such patches will reflect the committer. The actual + author of a patch, if different, is generally listed in the commit message; + reviewers or others who contributed ideas or otherwise helped with the patch + may also be listed. Many patches, in the form in which they are committed, + are the work of multiple people: original author or authors, reviewer(s), + and/or committer. As a result, no simple analysis of duration or depth of + contribution over time is possible from the commit log. The project operates + a system of careful peer review and even committers have their work checked + by other committers and the community as a whole. +
+ ++ New committers are added approximately annually after discussions + and vote among the existing committers. Contributors to PostgreSQL + are selected to be committers based on the following loose criteria: +
++ Generally, new committers are selected March or April and announced on the + Hackers mailing list. +
+ ++ Committers who have become inactive and have not contributed significantly + to the PostgreSQL project in several years are removed as committers. Again, + the review process for this is approximately annual. +
+ +{%endblock%}