[pgrouting-dev] Proposal for Cleanup of pgRouting/Workshop Github Repository

[Vicky Vergara]

Hello Rajat,
I think cleaning up that repo is going to be good.
I see your detailed proposal, and I think it is very clear on how to
proceed so we do not lose any information
Thanks for the proposal, from my part it is a thumbs up.
Let's wait until next monday to see if someone else has a suggestion on how
to proceed with the cleanup.
Thanks for your efforts





On Mon, Dec 21, 2020 at 1:21 PM Rajat Shinde <rajatshinde2303 at gmail.com>
wrote:

> Hello all,
>
> The pgRouting community proposes cleanup of pgRouting/Workshop Github
> repository [1].
> We should only have the following branches:
> main [2]
> develop
> gh-pages
>
> Some of the problems are:
>
>    - Some of the branches are 10 years old such as "FOSS4G2011" branch
>    [3] which is already published at [4].
>    - The FOSS4G Hokkaido workshop is not yet published on the pgRouting
>    Workshop website [5] and the development of the "develop/hokkaido" branch
>    is stalled since 2015 [6].
>    - Many branches start with "develop/" (the "/" normally indicates it
>    belongs to a repository named develop).
>
> This last example is causing some development issues: We are working on
> having a configured workshop and had to name the working branch as
> "general-develop" branch due to the lack of "develop" branch and many
> existing "develop/foo" branches, creating confusion about the correct
> branch for developing.
>
> Proposal to cleanup of the Workshop repository:
> Remember that Github handles tags with semantic versioning, the latest
> version corresponds to the last pushed tag and any new tags for the stalled
> branches will not be versioned tags.
>
> The cleanup would comprise of following steps:
>
>    1. Make sure that tags exist for the international FOSS4G workshops
>       1. Find the versioned number corresponding to the international
>       branch
>       2. If it does not exist, then create a tag with the name:
>       FOSS4G<YEAR><PLACE>
>       3. Delete the branch
>    2. Make sure that tags exist for the local FOSS4G workshops
>       1. These are not versioned
>       2. Find a corresponding tag for the local branch
>       3. If it does not exist, then create a tag with the name:
>       <PLACE><LAST YEAR OF MODIFICATION>
>       4. Delete the branch
>    3. Rename "general-develop" to "develop"
>       1. Create branch "develop" based on "general-develop"
>       2. Delete branch "general-develop"
>    4. Rename "master" to "main"
>       1. Create branch "main" based on "master"
>       2. Pending the delete of "master" until things work properly on
>       Github for branch "main"
>
> If this proposal is accepted, I will open an administrative issue on the
> pgRouting/Workshop Github repository [7], to keep track of all the steps
> mentioned. The related tags will be placed as Github issues and before
> removing any branch, a comment will be posted to get thumbs up. A comment
> will follow post removal of the branch as well.
>
> Thanks!
> Kind regards,
> pgRouting Team
>
> [1] https://github.com/pgRouting/workshop/branches/all
> [2] https://github.com/github/renaming
> [3] https://github.com/pgRouting/workshop/tree/foss4g2011
> [4] https://workshop.pgrouting.org/0.6.1/en/index.html
> [5] https://workshop.pgrouting.org/
> [6] https://github.com/pgRouting/workshop/tree/develop/hokkaido
> [7] https://github.com/pgRouting/workshop
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>


-- 

Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany

Vicky Vergara
Operations Research

eMail: vicky at georepublic.de
Web: https://georepublic.info

Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9

Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20201221/71e11c64/attachment.html>