Idea: we could move synctools to a gradle subproject in the davx5-ose repo to simplify working.
The current workflow of having 2 PRs per change (one for synctools, one for DAVx⁵) is annoying.
Reasons for having synctools in a separate repo were:
- modularity → can be achieved with gradle subproject
- independent tests because they run long and on different API levels etc → we could keep two workflows (test core/app, test synctools) and run the "test synctools" workflow only when files in the respective directories are changed.
- reusability in ICSx⁵
- reusability in other projects: I'm not aware of any other FOSS projects using synctools, and it's probably not really possible because it's changing that fast (and people can still use the code when it's in davx5)
What would change if we merge it:
- much easier working because we don't need two PRs for each synctools change
- one "includeBuild" hack less (I just had the problem that AboutLibraries 14.1.0+ makes it impossible to use includeBuild)
- much easier AI access (it could just work in the repo, multi-repo work is more complicated for AI too)
- DAVx5 issues are often synctools issues. Currently we have to duplicate the issues and handle them in both repos. Having all issues in davx5-ose would be much easier, however probably requires better issue tracking (for instance a tag for synctools issues).
- probably another workflow for testing in davx5-ose with more complicated rules than now (should only run when synctools files or dependencies are affected)
Open questions:
Steps:
Idea: we could move synctools to a gradle subproject in the davx5-ose repo to simplify working.
Open questions:
Steps: