Policy on reusable workflows for document repositories

[ronaldtse]

There are 3 types of document repositories:

1. End-user document repositories. These only need the simplest build workflow and provides the artifacts for the user to download.
2. CI document repositories. These repositories are the core release tests for Metanorma and they need to be built in many ways.
3. Internal document repositories. These repositories are tests for Metanorma, and need to be tested in many ways, but they are not blockers for the CI flow.

For public repositories that require private fonts, they can use those fonts.

Currently we have "two kinds of workflows" (as per @CAMOBAP):

• "internal" we just reuse workflow from metanorma/ci. It's not for the end users, because it's hard to read it, but they are general and cover almost all our document repos.
• "end-user" workflow like S-102-Product-Specification. It's compact, much easier to understand because it the self-contained, but they don't cover all use cases.

Originally posted by @CAMOBAP in https://github.com/metanorma/iso-10303-2/issues/286#issuecomment-1624777447

[CAMOBAP]

@ronaldtse thanks for the answers, let me specify:

1. can I assume that all public repositories except mn-samples-* are end-user document repositories?
2. it's mn-sample-* repository only, right?
3. private repositories i.e. iso-* ones, right?

[ronaldtse]

CI document repositories.

• mn-samples-* (public + private)
• mn-templates-* (public + private)

Internal document repositories

I actually don't have a list of particular repos we want to test with outside the ones above.

End-user repositories

All public and private repositories should be considered end-user repositories.

[CAMOBAP]

Document repos updated