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

[Ashish Kumar]

+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.


On Mon, 24 Apr 2023 at 23:11, Rajat Shinde <rajatshinde2303 at gmail.com>
wrote:

> +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 at 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 at lists.osgeo.org] *On
>> Behalf Of *Vicky Vergara
>> *Sent:* Tuesday, April 18, 2023 12:56 AM
>> *To:* pgRouting developers mailing list <pgrouting-dev at 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 at 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 at lists.osgeo.org] *On
>> Behalf Of *Vicky Vergara
>> *Sent:* Monday, April 17, 2023 9:38 PM
>> *To:* pgRouting developers mailing list <pgrouting-dev at 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 at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>>
>> _______________________________________________
>> pgrouting-dev mailing list
>> pgrouting-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20230425/105b630d/attachment.htm>