Choose best solution for repo for R wrapper generator

[grzanka]

Consider couple of options:

• subdirectory in libamtrack/library repo
• another repo linked via git submodule mechanizm

Write down pros and cons, taking special care about project release cycle and versioning

[Sharon131]

Subdirectory: Pros:

• less problems with setting up Github Actions
• we already pushed prototype of generator to libamtrack/library repository
• we can setup working directory for workflow in Github Actions as R package generator directory

Cons:

• new R package generator will be right next to the old one in directory tree and that could be confusing
• there could be a problem in finding older versions of generator in all the commits of libamtrack and reverting to old version of generetor reverts also version of libamtrack

Another repo as submodule: Pros:

• separate place for code and issues
• we have more certainty that issues cosidering R package generator will not be overlooked because of not related ones (they will not get lost)
• there should be no problem in including submodule in workflow in Github Actions (easy command)

Cons:

• we do not have sufficient permission to create new repository in libamtrack group (can be solved)
• we can use specific commit from submodule repository, but every time we add new version of generator we would need to change commit number in testing workflow in Github Actions. (could be solved by setting tracking to stable branch that contains only subsequent versions of generator)
• there might be a problem when switching branch in git versions <= 2.13. if we switch to branch, that does not include submodule yet it will see it as changes to be committed. In newer versions it can be solved by running command git checkout --recurse-submodule instead git checkout. That command could be also set as alias. Problem description in section "Issues with submodules" : https://git-scm.com/book/en/v2/Git-Tools-Submodules
• there might be a major problem with already pushed prototype and adding submodule. Problem described in sections "Switching from subdirectories to submodules": https://git-scm.com/book/en/v2/Git-Tools-Submodules . Although, problem will not appear if names are not the same.

Another thing is that to use package generator in Github Action when it is in seperate repo, it would have to be cloned, because submodule does not know it is used as submodule and cannot reference master repo. So, in that case package generator does not need to be a submodule, it could be just a seperate repo.

I think, that seperate repo would be better despite more complicated setup. It should be easier to maintain later.

[grzanka]

I'd opt for new repository