[pygeoapi] MOTION: Renaming 'master' branch to 'main' in all pygeoapi repositories

[Paul van Genuchten]

+1, good initiative

Bye, Paul



> On 14 Jun 2021, at 21:00, pygeoapi-request at lists.osgeo.org wrote:
> 
> Send pygeoapi mailing list submissions to
> 	pygeoapi at lists.osgeo.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.osgeo.org/mailman/listinfo/pygeoapi
> or, via email, send a message with subject or body 'help' to
> 	pygeoapi-request at lists.osgeo.org
> 
> You can reach the person managing the list at
> 	pygeoapi-owner at lists.osgeo.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pygeoapi digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: MOTION: Renaming 'master' branch to 'main' in all
>      pygeoapi repositories (Just van den Broecke)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 14 Jun 2021 11:03:33 +0200
> From: Just van den Broecke <justb4 at gmail.com>
> To: pygeoapi at lists.osgeo.org
> Subject: Re: [pygeoapi] MOTION: Renaming 'master' branch to 'main' in
> 	all pygeoapi repositories
> Message-ID: <3ae251f5-e0c2-d100-a8fa-bfa93c43db36 at gmail.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> +1
> 
> On 13/06/2021 15:33, Tom Kralidis wrote:
>> Hi PSC:
>> 
>> At our Gitter meeting on 2021-06-11 [1], there was discussion on renaming
>> our default branch from 'master' to 'main' (thanks to Jeff McKenna for 
>> bringing
>> this topic to the meeting).? Numerous projects have made similar updates 
>> (example
>> in [2]), and GitHub has made the transition relatively seamless as well [3].
>> 
>> In the pygeoapi project, this impacts the following repositories:
>> 
>> - source code [4]
>> - demo [5]
>> - website [6]
>> 
>> Note that any 'master' protected branches or pull requests will get updated
>> accordingly.
>> 
>> This will also require anyone who has forked pygeoapi to update their fork.
>> 
>> I'm willing to make the relevant changes along with 
>> planning/announcements/documentation
>> (following the great example set in [2]).
>> 
>> Having said this, I motion to rename the default branch from 'master' to 
>> 'main'
>> for the abovementioned repositories.
>> 
>> I will start with my +1.
>> 
>> ..Tom
>> 
>> [1] https://github.com/geopython/pygeoapi/wiki/Meetings-2021-06-11 
>> <https://github.com/geopython/pygeoapi/wiki/Meetings-2021-06-11>
>> [2] https://github.com/MapServer/MapServer/wiki/Renamed-Default-Branch 
>> <https://github.com/MapServer/MapServer/wiki/Renamed-Default-Branch>
>> [3] https://github.com/github/renaming <https://github.com/github/renaming>
>> [4] https://github.com/geopython/pygeoapi 
>> <https://github.com/geopython/pygeoapi>
>> [5] https://github.com/geopython/demo.pygeoapi.io 
>> <https://github.com/geopython/demo.pygeoapi.io>
>> [6] https://github.com/geopython/pygeoapi.io 
>> <https://github.com/geopython/pygeoapi.io>
>> 
>> _______________________________________________
>> pygeoapi mailing list
>> pygeoapi at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/pygeoapi
>> 
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> pygeoapi mailing list
> pygeoapi at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pygeoapi
> 
> 
> ------------------------------
> 
> End of pygeoapi Digest, Vol 23, Issue 4
> ***************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pygeoapi/attachments/20210615/eb4a9e4e/attachment.html>