Expand the purpose of the repository

[zorp]

I would like to suggest we expand the purpose of this repository to include more governance related materiale. My thoughts are to:

• Rename the repository from governance_report_template to Governance or Governance_templates
• Introduce templates related to governance:
  • Role descriptions.
  • Terms of Reference (ToR) - Kommissorium på dansk.
  • Meeting structure
  • Meeting agendas and meeting minutes
  • and many more

I would like feedback to my idea of using this repro and thereby place governance related templates and guidelines in close connection to the governancemodel itself.

Attached is an example of a template I think should be included in this repro.

Produktkoordinator_arbejdsbeskrivelse.md

[janhalen]

Ok... That is definately possible.

Where should the templates then live? In their own repos?

The reason i ask is the risks connected to monorepos if you want to have a lot of different results/implementations of them.

E.g. if we want a dynamic form based template for the governance evaluation "thing", then it would be easier to keep it in a repo for it self. If your want the governance repo to render a webpage at some point, it would be most effective if that part of the governance implementation (showing it on a webpage) is kept in a seperate repo too and maintained by a seperate team. (following the principles of least privilledge) Or maybe you are just thinking of this new Governance repo as a document storage?

I think the idea of deciding on a better and more efficient structure is GREAT, and i would love to help make the needed changes, but I think we need to decide on these questions first, before we start making automations, deployments etc.

[zorp]

The way forward must be to keep this repo as-is because it is supposed to the dynamic form based template for governance evaluation.

Then a new repo called governance_template must be created with the purpose of being the template that can render into a webpage like the documentation template. That will be most in line with what we must accomplish. In the future all OS2-products must then use the project template for the main repo, the documentation template for the documentation website and the governance template to generate all the governance related information and there will also be a communication template repo that I know @sissekaliaswendyfan is working on.

To sum up my conclusion

We must provide different github templates that each OS2-product must use and maintain within their organisations:

• Project template -> template for the main code repo.
• Documentation template -> template for the project documentation, a website is generated.
• Governance template -> template for the OS2 related governance of the project, a website is generated. (Maybe there is a potential conflict with some files in the project template, we have to work around that).
• Communication template -> template for communication around the project, a website is generated.