Prepare for release on website.

README.md

@@ -1,26 +1,26 @@
 # openEO Project Steering Committee
 
-This document describes how the openEO Project Steering Committee determines membership, and makes decisions on openEO project issues. The openEO project is concerned with all repositories (software and specifications etc.) found under https://github.com/Open-EO.
+This document describes how the openEO Project Steering Committee determines membership, and makes decisions on openEO project issues. The openEO project is concerned with all repositories (software and specifications etc.) found under <https://github.com/Open-EO>.
 
-In brief the committee votes on proposals on https://github.com/Open-EO/PSC/issues. Proposals are available for review for at least two business days, and a single veto is sufficient to delay progress though ultimately a majority of members can pass a proposal.
+In brief the committee votes on proposals on <https://github.com/Open-EO/PSC/issues>. Proposals are available for review for at least two business days, and a single veto is sufficient to delay progress though ultimately a majority of members can pass a proposal.
 
 ## Members
 
-Matthias Mohr is declared initial Chair of the openEO Project Steering Committee. The initial list of members of the Project Steering Committee is:
+The initial list of members of the Project Steering Committee is:
 
-* Jeroen Dries (@jdries)
-* Luca Foresta (@lforesta)
-* Alexander Jacob (@aljacob)
-* Miha Kadunc (@mkadunc)
-* Matthias Mohr (**chair**, @m-mohr)
-* Markus Neteler (@neteler)
-* Edzer Pebesma (@edzer)
+* Jeroen Dries ([@jdries](https://github.com/jdries))
+* Luca Foresta ([@lforesta](https://github.com/lforesta))
+* Alexander Jacob ([@aljacob](https://github.com/aljacob))
+* Miha Kadunc ([@mkadunc](https://github.com/mkadunc))
+* Matthias Mohr (**chair**, [@m-mohr](https://github.com/m-mohr))
+* Markus Neteler ([@neteler](https://github.com/neteler))
+* Edzer Pebesma ([@edzer](https://github.com/edzer))
 
 The current list will be maintained by the openEO chair on this page and will be published to the openEO web pages, too.
 
 ## Detailed Process
 
-1. Proposals are written up and submitted on https://github.com/Open-EO/PSC/issues/new for discussion and voting, by any interested party, not just committee members.
+1. Proposals are written up and submitted on <https://github.com/Open-EO/PSC/issues/new> for discussion and voting, by any interested party, not just committee members.
 2. Proposals need to be available for review for at least two business days before a final decision can be made. Public holidays count as business days.
 3. Respondents may vote `+1` to indicate support for the proposal and a willingness to support implementation.
 4. Respondents may vote `-1` to veto a proposal, but must provide clear reasoning and alternate approaches to resolving the problem within the two days.
@@ -49,7 +49,7 @@ Generally speaking, technical decisions should be made by consensus within openE
 
 * The Chair is the ultimate adjudicator if things break down.
 * The absolute majority rule can be used to override an obstructionist veto, but it is intended that in normal circumstances vetoers need to be convinced to withdraw their veto. We are trying to reach consensus.
-* Software components that at least two other software repositories under https://github.com/Open-EO depend on, must implement a review system for breaking changes (e.g. GitHub Pull Request Approvals) that require a certain number of approvals: 2 dependants require 1 approval, more than 2 dependants require 2 approvals. Exceptions for this must go through the PSC process.
+* Software components that at least two other software repositories under <https://github.com/Open-EO> depend on, must implement a review system for breaking changes (e.g. GitHub Pull Request Approvals) that require a certain number of approvals: 2 dependents require 1 approval, more than 2 dependents require 2 approvals. Exceptions for this must go through the PSC process.
 
 ## Committee Membership
 
@@ -61,8 +61,10 @@ Any member of the openEO mailing list may nominate someone for committee members
 
 If for any reason a PSC member is not able to fully participate then they certainly are free to step down. If a member is not active (e.g., no voting or email participation) for a period of 12 months then the PSC reserves the right to seek nominations to fill that position. Should that person become active again then they would certainly be welcome, but would require a nomination.
 
-## Meta
+## History
 
-Author: Edzer Pebesma, mostly copied from https://gdal.org/development/rfc/rfc1_pmc.html#rfc-1
+This document is based on the [GDAL Project Management Committee Guidelines](https://gdal.org/development/rfc/rfc1_pmc.html#rfc-1) and was accepted by the openEO project board on October, 7 2020.
 
-Status: Accepted by PBM, non-PBM comittee members still need to accept their nomination.
+The following changes have been made thereafter:
+
+* None yet