Describe the enhancement you'd like
We have right now at least four different repos, which you need in order to develop for LibrePhotos. This makes it hard for new people to understand how to develop for it. It also makes the release management tricky.
Possible repositories to merge:
librephotos
librephotos-frontend
librephotos-linux
librephotos-docker
librephotos-mobile
react-pig
react-image-lightbox
We should also look into adding librephotos.docs to it, but we have to figure out how the hosting would work and if github would still host it.
The idea is, that we move to a mono-repo, where we have subfolders for the current different repositories. We could also look into wrappers which manage monorepos like nx or lerna
Describe why this will benefit the LibrePhotos
Easy to understand for new developers, better release management, reviewing of pr with backend and frontend changes is easier, removes dispatch logic from ci/cd pipeline.
I think we should make sure that we can release projects separately. Otherwise we'd have to add version bumps to projects even if there are no changes.
Describe the enhancement you'd like We have right now at least four different repos, which you need in order to develop for LibrePhotos. This makes it hard for new people to understand how to develop for it. It also makes the release management tricky.
Possible repositories to merge:
We should also look into adding librephotos.docs to it, but we have to figure out how the hosting would work and if github would still host it.
The idea is, that we move to a mono-repo, where we have subfolders for the current different repositories. We could also look into wrappers which manage monorepos like nx or lerna
Describe why this will benefit the LibrePhotos Easy to understand for new developers, better release management, reviewing of pr with backend and frontend changes is easier, removes dispatch logic from ci/cd pipeline.