This makes it super difficult to know where to look for certain features but more importantly makes it very cumbersome to get an overview of certain APIs.
Example: where do you file an issue that relates to one of the APIs? This is difficult to tell with this many repos. It could fit into many places.
Furthermore, it is not easy to maintain distributed repos when it comes to CI/CD and maintaining documentation / READMEs across the different repositories as it always requires separate commits.
Current situtation
There seem to be 39 repositories @public-transport. Some of these are only small scripts that extend some of the other APIs.
This issue could be used to come up with some kind of strategy for how to simplify the repo structure surrounding the public transport API.
We could also use it to collect benefits and drawbacks of monorepos.
Considering, GitHub and SEO, it might actually be super beneficial for visibility. If we have bigger single repos, they can be more easily starred and searchable on the internet.
Motiviation
Currently, there are a lot (a lot) of repos surrounding @public-transport and https://github.com/public-transport/transport.rest.
This makes it super difficult to know where to look for certain features but more importantly makes it very cumbersome to get an overview of certain APIs.
Example: where do you file an issue that relates to one of the APIs? This is difficult to tell with this many repos. It could fit into many places.
Furthermore, it is not easy to maintain distributed repos when it comes to CI/CD and maintaining documentation / READMEs across the different repositories as it always requires separate commits.
Current situtation
There seem to be
39repositories @public-transport. Some of these are only small scripts that extend some of the other APIs.There are
554repos @derhuerst. I assume that some of these are forks, but https://github.com/derhuerst/vbb-modules shows that there is definitely a lot.Strategy
This issue could be used to come up with some kind of strategy for how to simplify the repo structure surrounding the public transport API.
We could also use it to collect benefits and drawbacks of monorepos.
Considering, GitHub and SEO, it might actually be super beneficial for visibility. If we have bigger single repos, they can be more easily starred and searchable on the internet.