Removing Issues tab on all georchestra "sub"-projects

[f-necas]

In order to avoid going into multiple projects, what if we remove all Issues tab in project settings :

All issues would be created under georchestra/georchestra project.
They could be labeled, or something like that.

[f-necas]

An opnion on it @landryb @pmauduit @fvanderbiest @edevosc2c ?

[edevosc2c]

I'm for keeping issues on each distinct GitHub repository. Having everything in one repo would be a big mess in my opinion.

If it's to have a global view of all the issues, you can achieve that through GitHub projects.

[f-necas]

The idea was to avoid duplicating milestones, labels, issues across projects to get "kanban projects" automated and simplified.

I tried to put a 24.1.0 milestone on

• Georchestra gn4.4.5 rebase geonetwork#297
• [gateway/ldap] - Replace oAuthProvider with a more generic name  #4268

And only georchestra's one ended up automatically in project board : https://github.com/orgs/georchestra/projects/18/views/2

[edevosc2c]

I can see two on my side.

[f-necas]

Yes but the second one was added manually

[edevosc2c]

What do you mean by manually? For an issue to appear on a GitHub project, it has to be added to the project.

The filter applies to what issues has been added to the project. Not on a global scale to all the GitHub repository across the GitHub organization.

[pmauduit]

In order to avoid going into multiple projects, what if we remove all Issues tab in project settings

👍

[edevosc2c]

I see more downsides than benefits to have ALL the issues in one repo. One big downside is to have an ever increase of number of issues to the point that you feel you are overwhelmed by them.

Also, some users don't have anything to do with the other repositories. For instance, gabriel only works for georchestra gateway so he is subscribed to the notifications of georchestra-gateway only: https://github.com/georchestra/georchestra-gateway/watchers and not the georchestra main repo: https://github.com/georchestra/georchestra/watchers

If you move all the issues into the main georchestra repo, gabriel for example will have a hard time keeping up with the issues related to his project.

Anyway, if you want to understand how other projects deals with releases in a GitHub projects way, just look at how big open source projects do. Like newpipe: https://github.com/orgs/TeamNewPipe/projects?query=is%3Aclosed or yt-dlp: https://github.com/orgs/yt-dlp/projects?query=is%3Aopen or Kubernetes! : https://github.com/orgs/kubernetes/projects?query=is%3Aopen