Align CLOMonitor coverage with delivered repository inventory

Open
#102 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
tooling

Research direction

Start by reviewing policy issue #16, SUBPROJECTS.md, the global replication groups, and the current CLOMonitor configuration. Compare the four omitted repositories with the existing coverage policy; this issue is done when a maintainer decision is recorded, including any exclusions, so a separate cncf/clomonitor PR can be opened.

Written by the indexing model from the issue text.

Description

Context

An audit has been conducted and confirmed that SUBPROJECTS.md and the global replication groups now cover all 45 public Microcks repositories consistently.

However, the CNCF CLOMonitor configuration currently covers 20 repositories: 19 delivered components with community + code checks and microcks.io with docs. The current report remains healthy at A / 98.49%.

Four repositories classified as delivered components are missing:

  • microcks-mcp-server
  • microcks-agent-skills
  • api-tooling
  • homebrew-tap

There is no existing CLOMonitor issue or pull request covering them.

Decision needed

The existing policy from #16 assigns community + code to delivered components. CLOMonitor also offers code-lite, recommended for secondary code repositories.

@lbroudoux @SebastienDegodez, should we:

  1. Add all four repositories with community + code for consistency with the existing policy;
  2. Use community + code-lite for selected secondary tooling repositories; or
  3. Intentionally exclude any of them, documenting why CLOMonitor coverage is not relevant?

Once agreed, we can submit a separate PR to cncf/clomonitor. No upstream PR should be opened before this decision.

Dominant language
No language data
Stars
8
Forks
41
Avg merge
1d 1h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microcks/.github

All issues in microcks/.github

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.