Replies: 3 comments 6 replies
-
An opnion on it @landryb @pmauduit @fvanderbiest @edevosc2c ? |
Beta Was this translation helpful? Give feedback.
-
👍 |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions