[pgrouting-dev] Motion: DOI for the all of the pgRouting projects

pgRouting pgrouting-dev
1

Hello all,

Base on this:

https://lists.osgeo.org/pipermail/projects/2023-April/000353.html

The following motion:

Create a DOI for:

pgrouting
osm2pgrouting
pgRoutingLayer
workshop

Regards

Vicky

2

+0. I’m not against or for it.

I’m not sure how much work is involved. On the postgis side, we never finished. No one could understand why we needed yet another thing we needed to maintain. Dave McKenna took initiative and created it for us and we’ve never updated it.

So I think we need have someone take ownership of it and make sure it can be updated whenever a new release is done. Otherwise it will just get stale.

From: pgrouting-dev [mailto:pgrouting-dev-bounces@lists.osgeo.org] On Behalf Of Vicky Vergara
Sent: Monday, April 17, 2023 9:38 PM
To: pgRouting developers mailing list pgrouting-dev@lists.osgeo.org
Subject: [pgrouting-dev] Motion: DOI for the all of the pgRouting projects

Hello all,

Base on this:

https://lists.osgeo.org/pipermail/projects/2023-April/000353.html

The following motion:

Create a DOI for:

pgrouting

osm2pgrouting

pgRoutingLayer

workshop

Regards

Vicky

3

I’ve already registered to zendo.

Somewhere I read that it updates automatically on the latest release on github or something like that.

(need to re-read to find the link to that statement)

On Mon, Apr 17, 2023 at 8:32 PM Regina Obe <lr@pcorp.us> wrote:

+0. I’m not against or for it.

I’m not sure how much work is involved. On the postgis side, we never finished. No one could understand why we needed yet another thing we needed to maintain. Dave McKenna took initiative and created it for us and we’ve never updated it.

So I think we need have someone take ownership of it and make sure it can be updated whenever a new release is done. Otherwise it will just get stale.

From: pgrouting-dev [mailto:pgrouting-dev-bounces@lists.osgeo.org] On Behalf Of Vicky Vergara
Sent: Monday, April 17, 2023 9:38 PM
To: pgRouting developers mailing list <pgrouting-dev@lists.osgeo.org>
Subject: [pgrouting-dev] Motion: DOI for the all of the pgRouting projects

Hello all,

Base on this:

https://lists.osgeo.org/pipermail/projects/2023-April/000353.html

The following motion:

Create a DOI for:

pgrouting

osm2pgrouting

pgRoutingLayer

workshop

Regards

Vicky

pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev

4

Yah I recall that being the case. So it should work fine since that is your primary.

From: pgrouting-dev [mailto:pgrouting-dev-bounces@lists.osgeo.org] On Behalf Of Vicky Vergara
Sent: Tuesday, April 18, 2023 12:56 AM
To: pgRouting developers mailing list pgrouting-dev@lists.osgeo.org
Subject: Re: [pgrouting-dev] Motion: DOI for the all of the pgRouting projects

I’ve already registered to zendo.

Somewhere I read that it updates automatically on the latest release on github or something like that.

(need to re-read to find the link to that statement)

On Mon, Apr 17, 2023 at 8:32 PM Regina Obe <lr@pcorp.us> wrote:

+0. I’m not against or for it.

I’m not sure how much work is involved. On the postgis side, we never finished. No one could understand why we needed yet another thing we needed to maintain. Dave McKenna took initiative and created it for us and we’ve never updated it.

So I think we need have someone take ownership of it and make sure it can be updated whenever a new release is done. Otherwise it will just get stale.

From: pgrouting-dev [mailto:pgrouting-dev-bounces@lists.osgeo.org] On Behalf Of Vicky Vergara
Sent: Monday, April 17, 2023 9:38 PM
To: pgRouting developers mailing list <pgrouting-dev@lists.osgeo.org>
Subject: [pgrouting-dev] Motion: DOI for the all of the pgRouting projects

Hello all,

Base on this:

https://lists.osgeo.org/pipermail/projects/2023-April/000353.html

The following motion:

Create a DOI for:

pgrouting

osm2pgrouting

pgRoutingLayer

workshop

Regards

Vicky

pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev

5

+1

Maybe, only having DOI for the main pgRouting project makes more sense. But its not a harm to have DOIs for all of them.

Thanks and regards,
Rajat

On Tue, Apr 18, 2023 at 12:13 AM Regina Obe <lr@pcorp.us> wrote:

Yah I recall that being the case. So it should work fine since that is your primary.

From: pgrouting-dev [mailto:pgrouting-dev-bounces@lists.osgeo.org] On Behalf Of Vicky Vergara
Sent: Tuesday, April 18, 2023 12:56 AM
To: pgRouting developers mailing list <pgrouting-dev@lists.osgeo.org>
Subject: Re: [pgrouting-dev] Motion: DOI for the all of the pgRouting projects

I’ve already registered to zendo.

Somewhere I read that it updates automatically on the latest release on github or something like that.

(need to re-read to find the link to that statement)

On Mon, Apr 17, 2023 at 8:32 PM Regina Obe <lr@pcorp.us> wrote:

+0. I’m not against or for it.

I’m not sure how much work is involved. On the postgis side, we never finished. No one could understand why we needed yet another thing we needed to maintain. Dave McKenna took initiative and created it for us and we’ve never updated it.

So I think we need have someone take ownership of it and make sure it can be updated whenever a new release is done. Otherwise it will just get stale.

From: pgrouting-dev [mailto:pgrouting-dev-bounces@lists.osgeo.org] On Behalf Of Vicky Vergara
Sent: Monday, April 17, 2023 9:38 PM
To: pgRouting developers mailing list <pgrouting-dev@lists.osgeo.org>
Subject: [pgrouting-dev] Motion: DOI for the all of the pgRouting projects

Hello all,

Base on this:

https://lists.osgeo.org/pipermail/projects/2023-April/000353.html

The following motion:

Create a DOI for:

pgrouting

osm2pgrouting

pgRoutingLayer

workshop

Regards

Vicky

pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev

pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev

6

+0

I’m not sure how relevant would this be for pgRouting. I have seen DOIs for academic publications, but as of now, this seems a bit uncommon to me for source code repositories.

If not much work is involved, this can be considered for pgRouting.

···

Regards,
Ashish.