PgRouting Incubation Status - Revision history

Cvvergara: /* Document Status */

2023-11-27T16:57:33Z

Document Status

Cvvergara: /* Code Copyright Review adding detailed information of automatic check on licenses */

2023-10-28T18:04:12Z

Code Copyright Review adding detailed information of automatic check on licenses

Cvvergara: /* Foundation Membership links to preparation of OSGeo logo change*/

2023-10-28T17:56:49Z

Foundation Membership links to preparation of OSGeo logo change

Cvvergara: /* Community Functioning adding docker */

2023-10-28T13:40:49Z

Community Functioning adding docker

Cvvergara: /* Community Functioning adding ubuntu GIS*/

2023-10-28T13:37:30Z

Community Functioning adding ubuntu GIS

Cvvergara: /* Community Functioning formatting*/

2023-10-28T13:35:11Z

Community Functioning formatting

Cvvergara: /* Infrastructure Transition updating links */

2023-10-28T13:33:14Z

Infrastructure Transition updating links

Cvvergara: /* Infrastructure Transition */

2023-10-28T13:13:05Z

Infrastructure Transition

Cvvergara: /* Infrastructure Transition format fixing and adding more information*/

2023-10-28T12:57:37Z

Infrastructure Transition format fixing and adding more information

Cvvergara: /* Infrastructure Transition update about domains*/

2023-10-28T12:36:06Z

Infrastructure Transition update about domains

@@ Line 1: / Line 1: @@
 = Document Status =
-'''IncCom Document Number''': X
+'''IncCom Document Number''': [https://trac.osgeo.org/osgeo/ticket/2784 2784]
 '''Version''': 0.1

@@ Line 112: / Line 112: @@
 ; Has a [[Code Provenance Review]] document been prepared for the project?
 No, work is in progress.
-* We have checked our C++ files and have an [https://github.com/pgRouting/pgrouting/blob/main/.github/workflows/check-files.yml#L39 automated license checker] for that
+* Verification on the project's C/C++ C++ files and
 ; Have issues raised in the provenance review been adequately addressed?

@@ Line 98: / Line 98: @@
 ; Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
-: If not, indicate when this will occur.
+If not, indicate when this will occur.
-We currently reflect our OSGeo Community Project status on https://pgrouting.org.  We will update to reflect as a project once we complete incubation.
+: The project currently reflect our OSGeo Community Project status on https://pgrouting.org.
 ; Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
-We currently use green colors and have the Community Project logo prominently displayed on the https://pgrouting.org home page.
+: * The project, currently use green colors
 == Code Copyright Review ==

@@ Line 71: / Line 71: @@
 : yes/no (and any caveats) Yes and there are many
 * [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS]
 * [https://packages.debian.org/search?keywords=pgrouting debian]

@@ Line 71: / Line 71: @@
 : yes/no (and any caveats) Yes and there are many
 * [https://packages.debian.org/search?keywords=pgrouting debian]
 * [https://apt.postgresql.org PostgreSQL PGDG distribution for debian and Ubuntu]

@@ Line 62: / Line 62: @@
 == Community Functioning ==
-; Is there a functioning user support mechanisms (ie. mailing list)? mailing list https://lists.osgeo.org/mailman/listinfo/pgrouting-dev and https://lists.osgeo.org/mailman/listinfo/pgrouting-users
+; Is there a functioning user support mechanisms (ie. mailing list)?
-There is also a gitter channel https://gitter.im/pgRouting/pgrouting which is also accessible via matrix: #pgRouting_pgrouting:gitter.im
+: developers mailing list https://lists.osgeo.org/mailman/listinfo/pgrouting-dev and
 : indicate the available user support mechanisms, and whether they seem to be functioning well (are getting used and get answers).

@@ Line 57: / Line 57: @@
 : * Releases source >= 2.0.0 can be found on https://github.com/pgRouting/pgrouting/releases
 : * Data for workshops are held on https://download.osgeo.org/pgrouting/workshops/
 == Community Functioning ==

@@ Line 54: / Line 54: @@
 Using github for source and workshops
 : * Releases source < 2.0.0 can be found on: https://download.osgeo.org/pgrouting/source/
 : * Releases source >= 2.0.0 can be found on https://github.com/pgRouting/pgrouting/releases
 : * Data for workshops are held on https://download.osgeo.org/pgrouting/workshops/

@@ Line 29: / Line 29: @@
 ; Has the projectname.osgeo.org domain been populated with the projects web presence?
-: If not why, and has the project page got a prominent link to the real home?
+If not why, and has the project page got a prominent link to the real home?
-: Project already has a long standing domain for website
+: Project already has a long standing domain for website:
 : https://pgrouting.org and
 : https://docs.pgrouting.org
-: Created a http://pgrouting.osgeo.org as that redirects to https://pgrouting.org.
+: http://pgrouting.osgeo.org redirects to https://pgrouting.org.
 ; Is the OSGeo bug tracker being used for the project?
-: If not, why? No to keep source control and issue tracker in sync. Issue Tracker is: https://github.com/pgrouting/pgrouting/issues
+If not, why?
 ; Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
-: If not, why? Yes we have two.  One for users: https://lists.osgeo.org/mailman/listinfo/pgrouting-users and one for developers https://lists.osgeo.org/mailman/listinfo/pgrouting-developers
+If not, why?
 ; Is the OSGeo SVN being used for the project?
-: If not, why? Using https://github.com/pgrouting/pgrouting
+If not, why?
-; Are binary and source downloads available from https://download.osgeo.org ?
+; Are binary and source downloads available from https://download.osgeo.org?
-: If not, why?  new source downloads are on https://github.com/pgRouting/pgrouting/releases,
+If not, why?
-workshops and data for workshops are held on https://download.osgeo.org/pgrouting/
+Using github for source and workshops
 == Community Functioning ==