[postgis-tickets] [SCM] postgis.net branch hugo updated. 15f855f77a7e59de1b5a27eb35eb5956629efa4f
git at osgeo.org
git at osgeo.org
Wed Mar 30 22:04:31 PDT 2022
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "postgis.net".
The branch, hugo has been updated
via 15f855f77a7e59de1b5a27eb35eb5956629efa4f (commit)
from 16f81dc9bff2a36650243a096853f3eb9cfbc1ad (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 15f855f77a7e59de1b5a27eb35eb5956629efa4f
Author: Regina Obe <lr at pcorp.us>
Date: Thu Mar 31 01:01:26 2022 -0400
CHANGES
1. Change post permlink format to slug from title, with that it uses
title slug if no slug specified, but can define a slug to override
default behavior. Intention is to keep old links the same as before.
2. Fix formatting of rfcs, make them single column with no related side
junk. Add core contributor guidelines rfc
3. Fiddle with styling some more. Change font to arial from metropolis
diff --git a/assets/sass/_custom.sass b/assets/sass/_custom.sass
index f078302..c7b41fd 100644
--- a/assets/sass/_custom.sass
+++ b/assets/sass/_custom.sass
@@ -69,3 +69,23 @@ h2
#footer
margin-left: -1.5em
margin-right: -1.5em
+
+div.map
+ float: left
+ margin-right: 40px
+
+#footer
+ margin-left: -3em
+ margin-right: -3em
+
+#footer
+ clear: both
+ background: #468
+ padding-top: 2em
+ padding-left: 3em
+ padding-right: 3em
+ padding-bottom: 0px
+ margin-left: -2.5em
+ margin-right: -2.5em
+ margin-bottom: -4em
+ color: white
\ No newline at end of file
diff --git a/assets/sass/_override.sass b/assets/sass/_override.sass
index 65e3569..5093238 100644
--- a/assets/sass/_override.sass
+++ b/assets/sass/_override.sass
@@ -12,4 +12,4 @@
@media screen and (min-width: $mobile-menu-breakpoint)
color: #000
.nav_close
- background-color: black
+ background-color: black
\ No newline at end of file
diff --git a/assets/sass/_variables.sass b/assets/sass/_variables.sass
index 663c239..f99ffe6 100644
--- a/assets/sass/_variables.sass
+++ b/assets/sass/_variables.sass
@@ -27,7 +27,7 @@ $single-column-breakpoint: 42rem
html
--color-mode: 'lit'
- --light: #fff
+ --light: #ffffff
--dark: #000
--bg: #011d2b
--haze: #f2f2f2
@@ -35,7 +35,7 @@ html
--accent: var(--gray)
--text: #000
--header-text: var(--dark)
- --font: Metropolis, sans-serif
+ --font: Arial, Metropolis, sans-serif
--theme: #0077b8
--ease: cubic-bezier(.19,1,.22,1)
--code-bg: var(--dark)
diff --git a/config/_default/config.toml b/config/_default/config.toml
index 19b5cef..61c0ed5 100644
--- a/config/_default/config.toml
+++ b/config/_default/config.toml
@@ -13,7 +13,7 @@ event = "events"
[permalinks]
'/pages/' = '/:filename/'
- '/post/' = '/:year/:month/:day/:title/'
+ '/post/' = '/:year/:month/:day/:slug/'
'/events/' = '/events/:filename/'
'/rfcs/' = '/rfcs/:filename/'
'/' = '/:filename/'
diff --git a/content/pages/documentation.md b/content/pages/documentation.md
index 3eea8f5..c7ecb8f 100644
--- a/content/pages/documentation.md
+++ b/content/pages/documentation.md
@@ -31,7 +31,7 @@ Versions that have reached end of life can still be downloaded from [PostGIS Rel
{{< /col>}}
{{< col "right">}}
-## Search Docs
+# Search Docs
Type search criteria here and enter:
@@ -44,26 +44,21 @@ window.location.href=url;
}
</script>
-## Tutorials
+# Tutorials
-* [Introduction to PostGIS](https://postgis.net/workshops/postgis-intro/)
+* Introduction to PostGIS [English](/workshops/postgis-intro/) [pdf en](/workshops/postgis-intro/PostGISIntro.pdf) [Chinese (Simplified)](/workshops/zh_Hans/postgis-intro/) [Spanish](/workshops/zh_Hans/postgis-intro/) [pdf es](/workshops/es/postgis-intro/PostGISIntro.pdf)
* [Crunchy Data Interactive PostGIS Learning Portal](https://learn.crunchydata.com/postgis)
-## Books
+# Books
+
+* [PostGIS In Action](http://www.postgis.us) - 3rd Edition (PostGIS 2.5, 3-3.1 and highlights of upcoming 3.2, PostgreSQL 11-13) (664 pages) Released August 2021 English
* [PostGIS 2 Analisis Espacial Avanzado 2nd](https://cartosig.webs.upv.es/postgis-analisis-espacial-avanzado-segunda-edicion/) - (PostGIS 2.4, PostgreSQL 10) released Sept 2018 Spanish
* [PostGIS Cookbook 2nd](https://www.packtpub.com/application-development/postgis-cookbook-second-edition) Released March 2018 (PostgreSQL 9.6) English
* [Mastering PostGIS](https://www.packtpub.com/big-data-and-business-intelligence/mastering-postgis) - covers PostGIS 2.2, released in May 2017, English
-* [PostGIS In Action](http://www.postgis.us) - 3rd Edition (PostGIS 2.5-3+, PostgreSQL 11-13 in progress) 2nd Edition (Covers PostGIS 2.0-2.1, PostgreSQL 9.1-9.3 (highlights of 9.4) - Released April 2015 English
* [PostGIS Essentials](https://www.packtpub.com/big-data-and-business-intelligence/postgis-essentials) - (PostGIS 2.2 released April 2015)
-## Cheatsheets
-
-* [PostGIS 2.1 Cheat Sheet](http://www.postgis.us/downloads/postgis21_cheatsheet.pdf)
-* [PostGIS 2.1 Raster Cheat Sheet](http://www.postgis.us/downloads/postgis21_raster_cheatsheet.pdf)
-* [PostGIS 2.1 Topology Cheat Sheet](http://www.postgis.us/downloads/postgis21_topology_cheatsheet.pdf)
-
-## Web Sites
+# Web Sites
* [Planet PostGIS](http://planet.postgis.net) - keep a pulse on what people are saying about PostGIS and learn how to take advantage of new features as they are added.
* [GIS Stack Exchange](http://gis.stackexchange.com/questions/tagged/postgis) may already have your answer: search before you ask!
diff --git a/content/post/2018/11-22_postgis-2.2.8.md b/content/post/2018/11-22_postgis-2.2.8.md
index af6b26a..66efedc 100644
--- a/content/post/2018/11-22_postgis-2.2.8.md
+++ b/content/post/2018/11-22_postgis-2.2.8.md
@@ -1,5 +1,5 @@
---
-title: PostGIS 2.2.8 EOL
+title: PostGIS 2.2.8
layout: post
category: news
tags: [release,2.2,EOL]
diff --git a/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md b/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md
index 288bda9..31af0d2 100644
--- a/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md
+++ b/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md
@@ -1,5 +1,6 @@
---
title: Upgrading raster from 2.* to 3.*
+slug: tip-upgrading-raster-from-2-3
layout: post
category: tips
tags: [newbie, upgrade]
diff --git a/content/rfcs/rfc01.md b/content/rfcs/rfc01.md
index 62b5ccd..15bda18 100644
--- a/content/rfcs/rfc01.md
+++ b/content/rfcs/rfc01.md
@@ -7,11 +7,14 @@ lastmod: 2022-03-01
draft: false
status: Draft
type: rfc
+relatedInSidebar: false
+singlecolumn: true
+sidebar: false
---
This document describes the functions of the PostGIS Project Steering Committee determines membership, and process used to carry out those functions.
-### Functions of the Project Steering Committee
+# Functions of the Project Steering Committee
The two primary functions of the PSC are:
@@ -22,9 +25,9 @@ The two primary functions of the PSC are:
The PSC is expected to be able to speak and act on behalf of the PostGIS project.
-### Codebase Control
+# Codebase Control
-#### Quality Control Mechanisms
+## Quality Control Mechanisms
The quality control mechanisms, which are the responsibility of the PSC, currently include:
@@ -36,11 +39,11 @@ In general, once write access has been granted, developers are allowed to make c
Removal of write access to the source code repository is handled as a proposal to the committee as described below in the 'Decision Process' section.
-#### Compliance with Legal Measures
+## Compliance with Legal Measures
Control over the codebase also extends to ensuring that it complies with all relevant legal requirements. This includes copyright and licensing amongst other issues. The Submitter guidelines document will include a section on copyright and licensing compliance.
-### Project Management
+# Project Management
The PSC will share responsibility and make decisions over issues related to the management of the overall direction of the PostGIS project and its external visibility. These include, but are not limited to:
@@ -53,11 +56,11 @@ The PSC will share responsibility and make decisions over issues related to the
It is the responsibility of the PSC to ensure that issues critical to the future of the PostGIS project are adequately attended to. This may the formation and oversight of sub-committees for particular purposes.
-## Decision Process
+# Decision Process
Written proposals are submitted to the the postgis-dev mailing list for discussion and voting. Proposals with significant technical detail should be written on the PostGIS wiki as an RFC, and an e-mail announcing the proposal, with a link to the RFC, should be sent to the postgis-dev mailing list. Proposals can be made by any interested party, not just PSC members.
-### Voting
+# Voting
* Proposals must be available for review for at least two business days before a decision can be made.
* Respondents may vote “+1” to indicate support for the proposal and a willingness to support implementation.
@@ -72,7 +75,7 @@ Written proposals are submitted to the the postgis-dev mailing list for discussi
* Addition and removal of members from the committee, as well as selection of a Chair should be handled as a proposal to the committee.
* The Chair is the ultimate adjudicator in cases of disputes about voting or breakdown of the voting system
-### When is a Vote Required?
+## When is a Vote Required?
* Any change to committee membership (new members, removing inactive members)
* Changes to project infrastructure (e.g. tool, location or substantive configuration)
@@ -84,11 +87,11 @@ Written proposals are submitted to the the postgis-dev mailing list for discussi
* Anything dealing with relationships with external entities such as OSGeo
* Anything that might be controversial
-## Committee Membership
+# Committee Membership
The PSC is made up of individuals consisting of technical contributors (e.g. developers) and prominent members of the PostGIS user community. There is no set number of members for the PSC.
-### Adding Members
+## Adding Members
Any member of the postgis-dev mailing list may nominate someone for committee membership at any time. Only existing PSC committee members may vote on new members. Nominees must receive a majority vote from existing members to be added to the PSC.
@@ -103,27 +106,27 @@ Once people are voted into the PSC, the following tasks must be done
* Add them to LDAP postgis group
* Add them to LDAP shell group and install their sshkey in their account on download.osgeo.org (needed so they can upload source tarballs and docs to download.osgeo.org/postgis) - again requires SAC member at moment to do
-### Stepping Down
+## Stepping Down
If for any reason a PSC member is not able to fully participate then they are free to step down. If a member is not active (e.g. no voting, no IRC or email participation) for a period of two months then the committee reserves the right to seek nominations to fill that position. Should that person become active again, they would require a nomination.
-## Membership Responsibilities
+# Membership Responsibilities
-### Guiding Development
+## Guiding Development
Members should take an active role guiding the development of new features they feel passionate about. Once a change request has been accepted and given a green light to proceed does not mean the members are free of their obligation. PSC members voting “+1” for a change request are expected to stay engaged and ensure the change is implemented and documented in a way that is most beneficial to users. Note that this applies not only to change requests that affect code, but also those that affect the web site, technical infrastructure, policies and standards.
-### IRC Meeting Attendance
+## IRC Meeting Attendance
PSC members are expected to participate in pre-scheduled IRC development meetings. If known in advance that a member cannot attend a meeting, the member should let the meeting organizer know via e-mail.
-### Mailing List Participation
+## Mailing List Participation
PSC members are expected to be active on both the postgis-users and postgis-dev mailing lists, subject to open source mailing list etiquette. Non-developer members of the PSC are not expected to respond to coding level questions on the developer mailing list, however they are expected to provide their thoughts and opinions on user level requirements and compatibility issues when RFC discussions take place.
-## Composition of the PSC
+# Composition of the PSC
The PostGIS development team has been effectively working under a PSC for several years but the process was not documented. This RFC will be distributed to the postgis-users and postgis-dev mailing lists for comment, and all substantive comments will be addressed appropriately before this RFC is accepted using the voting process defined herein.
@@ -131,7 +134,6 @@ The current Project Steering Committee members are:
* Raúl Marín Rodríguez
* Regina Obe
- * Bborie Park
* Darafei Praliaskouski
* Paul Ramsey (Chair)
* Sandro Santilli
diff --git a/content/rfcs/rfc02.md b/content/rfcs/rfc02.md
index 5610e75..aa53c13 100644
--- a/content/rfcs/rfc02.md
+++ b/content/rfcs/rfc02.md
@@ -5,6 +5,9 @@ category: rfcs
date: "2008-10-31"
draft: false
type: rfc
+relatedInSidebar: false
+singlecolumn: true
+sidebar: false
---
Getting into Alignment
diff --git a/content/rfcs/rfc05.md b/content/rfcs/rfc05.md
new file mode 100644
index 0000000..32c93c4
--- /dev/null
+++ b/content/rfcs/rfc05.md
@@ -0,0 +1,147 @@
+---
+title: "RFC-5: PostGIS Core Contributor Guidelines"
+author: Regina Obe
+version: 2.0
+category: rfcs
+date: "2022-03-21"
+draft: false
+type: rfc
+relatedInSidebar: false
+singlecolumn: true
+sidebar: false
+---
+
+# Changes to this file
+This RFC should be only changed by PostGIS PSC members. All PSC members must agree to the terms of the changes before the change is considered final except in the case of wording changes and formatting that do not alter the terms of the guidelines.
+
+# Purpose
+To formalize source tree access, and specify some guidelines for primary source committers and patch submitters.
+
+# Election to Core Contributors Group
+ Permission for write source tree access to our primary repo (https://git.osgeo.org/gitea/postgis/postgis.git) shall be provided to contributors only if accepted by the PostGIS Project Steering Committee. A proposal should be written to the PSC for new contributors and voted on normally. It is not necessary to write an RFC document for these votes, a proposal to postgis-dev is sufficient. After approval, the approved contributor shall be given write access to the PostGIS source repo and also added to the documentation under the section Core Contributors Present
+
+Removal of write access should be handled by the same process.
+
+The contributor should have demonstrated commitment to PostGIS and knowledge of the PostGIS source code and processes to the committee's satisfaction, usually by reporting bugs, submitting patches, and/or actively participating in the PostGIS mailing list(s).
+
+The contributor should also be prepared to support any new feature or changes in future releases that the contributor commits to the PostGIS source tree, or to find someone to which to delegate responsibility to should the contributor stop being available to support the portions of code the contributor is responsible for.
+
+All core contributors should also be a member of the postgis-dev mailing list so they can stay informed on policies, technical developments and release preparation.
+
+New core contributors are responsible for having read, and understood this document.
+
+# Code and Documentation Conventions
+
+* C code should follow our designated Style Guidelines to the best of your abilities
+* To accomplish Guidelines standards, we have implemented the use of editorconfig. Our repo as of version 2.4 now contains a .editorconfig file which editors configured with editorconfig support abide by.
+* We ask all developers to work with an editor that has editorconfig support. Many editors have it or have it as plugins.
+* All source code in GIT should be in Unix text format as opposed to DOS text mode with possible exception of .bat files.
+* Each new/changed function should be documented in the official docs following our [Documentation Guidelines](https://trac.osgeo.org/postgis/wiki/DevWikiDocNewFeature)
+
+# Repo Administrator
+One member of the Project Steering Committee will be designated as the Repo Administrator. That person will be responsible for giving write access to folks, updating the CREDITS, and other repo related management.
+
+Paul Ramsey is currently designated as the Repo Administrator.
+
+# Commit and Bug, Feature Tracking Practices
+
+The following are considered good source commit and tracking practices for the PostGIS project.
+
+ 1. Use meaningful descriptions for commit log entries. Format the git log to have a succint oneline description optionally followed by a detailed description after an empty line. Keep lines within 70 columns. Include trac ticket references in the detailed description. Ticket references will be signaled to trac so they can close tickets if "Closes #xxx" is found in the commit log or only result in comments if "References #xxx" is found. References to pull requests are better encoded as full links.
+ 2. We allow contributions via patches (on trac or via mailing lists) or pull requests from our primary or [CodeMirrors git mirrors]. If you are given a patch or pull request from a community person, make sure to keep their names in the commit log (`git commit --author "Name Surname <email>"`) and NEWS file. DO NOT USE the `MERGE` button on [CodeMirrors git mirrors] as mirrors will be overridden and the merged commit will be discarded; merge manually to official repo instead.
+ 3. We use https://trac.osgeo.org/postgis for planning so make sure pending changes have tickets there so they are not overlooked when cutting releases. If you forget to add trac ticket references in a commit log, edit the trac ticket and put the notes in, such as "Fixed in master ..git hash and in branches/3.0 <githas>". The 'r' character enables Trac to create a hyperlink from the ticket to the changeset.
+ 4. Make sure the NEWS file is updated in master branch for new features/breaking changes and in all the stable branches for bugfixes.
+ 5. Never commit new features to a stable branch without permission of the PSC or release manager. Normally only fixes should go into stable branches.
+ 6. New features go in the master branch.
+ 7. Only bug fixes should be committed to the master branch during pre-release code freeze, without permission from the PSC or release manager.
+ 8. Significant changes to the master branch, in particular breaking backward-compatibility, should be discussed on the postgis-dev list before you make them, and larger changes will require an RFC approved by the PSC.
+ 9. As a general rule, do not create new branches in the official repository. An exception to this rule is for when you want all CI bots to test your changes before pushing them to the target branch, in which case prefix your branch with a `test/` string.
+ 10. When committing new features or significant changes to existing source code, the committer should take reasonable measures to insure that the source code continues to build and work on the most commonly supported platforms (currently Linux, FreeBSD, Mac, and Windows), either by testing on those platforms directly, running CI tests, or by getting help from other developers working on those platforms. If new files or library dependencies are added, then the configure.in, Makefile.in and related documentations should be kept up to date.
+ 11. After each commit, verify that all the build bots are happy on this page - https://trac.osgeo.org/postgis/ and if their unhappiness is caused by your commit, fix the issue before making any other changes.
+
+
+# Committer Tracking
+
+A list of all core contributors is listed in the manual under the section "Core Contributors Present" in file doc/introduction.xml. This will be the responsibility of the PSC to keep up to date:
+
+* Full name: the users actual name.
+* A brief indication of areas of responsibility.
+
+This will be the responsibility of the documentation lead (currently Regina Obe) to manage. All stable non-EOL'd documents should list this information for core contributors.
+
+# Projects under PostGIS umbrella
+
+The PostGIS project has 3 additional sub-projects under it's umbrella. These projects may be impacted by changes in the core PostGIS project and have their own community of developers.
+
+Current list of these are:
+
+* Docker PostGIS - (https://github.com/postgis/docker-postgis) community managed docker builds of PostGIS.
+* PostGIS Java - ( https://github.com/postgis/postgis-java ) Java bindings for PostGIS
+* PostGIS Workshop (https://github.com/postgis/postgis-workshops) - Workshop material for PostGIS
+
+# Relationship with other Projects
+
+Some parts of the PostGIS code base are dependent on other upsteam projects or other projects rely heavily on functionality in PostGIS. Changes in those areas should go first into those upstream projects and then applied to PostGIS. In event of major changes to PostGIS, said projects should be regression tested (before a PostGIS release) to ensure the latest version still works with the latest RTM version of PostGIS.
+
+Currently the list of those areas is :
+
+* postgresql ( https://www.postgresql.org)
+* geos ( https://libgeos.org)
+* proj ( https://proj.org)
+* gdal ( https://gdal.org)
+* sfcgal (https://sfcgal.org)
+
+GIS FOSS suites that may be impacted by PostGIS major release:
+* mapserver (https://mapserver.org)
+* geoserver (https://geoserver.org)
+* openjump (http://openjump.org)
+* qgis (https://qgis.org)
+* gvSig (https://www.gvsig.org)
+* pgRouting (https://www.pgrouting.org/)
+* mobilitydb (https://mobilitydb.com/)
+* pgpointcloud (https://github.com/pgpointcloud)
+* osm2pgsql + other openstreetmap components (mapnik etc) (https://www.openstreetmap.org/)
+
+
+# Legal
+
+Core contributors are the front line gatekeepers to keep the code base clear of improperly contributed code. It is important to the PostGIS users, developers and the OSGeo foundation to avoid contributing any code to the project without it being clearly licensed under the project license.
+
+Generally speaking the key issues are that those providing code to be included in the repository understand that the code will be released under the original GPL license, and that the person providing the code has the right to contribute the code. The core contributor that accepts and committs the code should verify the understanding of the contributor unless the committer is very comfortable that the contributor understands the license (for instance frequent contributors).
+
+If the contribution was developed on behalf of an employer (on work time, as part of a work project, etc) then it is important that an appropriate representative of the employer understand that the code will be contributed under the GPL license. The arrangement should be cleared with an authorized supervisor/manager, etc.
+
+The code should be developed by the contributor, or the code should be from a source which can be rightfully contributed such as from the public domain, or from an open source project under a compatible license.
+
+All unusual situations need to be discussed and/or documented.
+
+Core contributors should adhere to the following guidelines, and may be personally legally liable for improperly contributing code to the source repository:
+
+* Make sure the contributor (and possibly employer) is aware of the contribution terms.
+* Code coming from a source other than the contributor (such as adapted from another project) should be clearly marked as to the original source, copyright holders, license terms and so forth. This information can be in the file headers, but should also be added to the project licensing file if not exactly matching normal project licensing.
+* Existing copyright headers and license text should never be stripped from a file. If a copyright holder wishes to give up copyright they must do so in writing to the OSGeo foundation before copyright messages are removed. If license terms are changed it has to be by agreement (written in email is ok) of the copyright holders.
+* Code with licenses requiring credit, or disclosure to users should be added to LICENSE.TXT.
+* When substantial contributions are added to a file (such as substantial patches) the author/contributor should be added to the list of copyright holders for the file.
+* If there is uncertainty about whether a change is proper to contribute to the code base, please seek more information from the project steering committee, or the foundation legal counsel.
+* New contributors and company contributors should be added to the credits in doc/introduction.xml of the latest release of the PostGIS manual.
+* It is the responsibility of the document lead to ensure when new enhancements are added or breaking changes are made, these are noted in the relevant branch/NEWS as soon as conveniently possible. The note should include the trac # (unless a major feature with many tickets) and contributors to the feature/change.
+
+# Bootstrapping
+
+The following existing committers will be considered authorized PostGIS committers as long as they each review the committer guidelines, and agree to adhere to them. The administrator will be responsible for checking with each person. Current committers are listed in alphabetical order with (P) to denote current Project Steering Committee members
+**TODO: this might have been the boot strap but not current developer list not sure we even need a bootstrap here **
+
+* Jorge Arévalo
+* Nicklas Avén
+* Mark Cave-Ayland (P)
+* Olivier Courtin
+* Chris Hodgson (P)
+* Mark Leslie
+* Mateusz Loskot
+* Kevin Neufeld
+* Regina Obe (P) Documentation Lead
+* Bborie Park (P)
+* Pierre Racine
+* Paul Ramsey (P) SVN Administrator
+* Sandro Santilli (P)
+* David Zwarg
-----------------------------------------------------------------------
Summary of changes:
assets/sass/_custom.sass | 20 +++
assets/sass/_override.sass | 2 +-
assets/sass/_variables.sass | 4 +-
config/_default/config.toml | 2 +-
content/pages/documentation.md | 19 +--
content/post/2018/11-22_postgis-2.2.8.md | 2 +-
.../2022/01-14_tip-upgrading-raster-from-2-3.md | 1 +
content/rfcs/rfc01.md | 36 ++---
content/rfcs/rfc02.md | 3 +
content/rfcs/rfc05.md | 147 +++++++++++++++++++++
10 files changed, 202 insertions(+), 34 deletions(-)
create mode 100644 content/rfcs/rfc05.md
hooks/post-receive
--
postgis.net
More information about the postgis-tickets
mailing list