Module repositories

[marcomicera]

Modules hierarchy

Hierarchy is achieved with GitHub templates by creating other independent repositories that share the git history.

• qmstr/module (issues)
  • qmstr/builder (issues)
    • qmstr/cmake-builder (issues)
    • qmstr/python3-builder (issues)
    • qmstr/maven-builder (issues)
  • qmstr/analyzer (issues)
    • ...
  • qmstr/reporter (issues)
    • qmstr/json-reporter (issues)
    • ...

Some repos still do not exist: this is intentional.

Order of development

Issues should be addressed starting from the top level of the hierarchy, i.e., modules.
Reason: once we update a parent template repository, children must rebase to its HEAD.

An example of cascading

When qmstr/module is considered to be complete, we can start addressing issues belonging to repos of the lower layer (as of now, qmstr/builder). From that point, qmstr/builder's git history will continue on its own.

In case of oversight

If qmstr/module needs to be changed while qmstr/builder is being developed, the latter can cherry-pick common-fixes from the former.