Add the MAINTANERS.md.

[xuezhaojun]

After the PR is merged, we should also update information in cncf repo: https://github.com/cncf/foundation/blob/2a58de4421a73db2c72f4ebe0795d8533ad1901e/project-maintainers.csv?plain=1#L1004

The motivation

• Community users should using this doc to quickly find the maintainer for their problem in a specific area of ocm.
• Quick glice to show the company/org of every maintainer.

The 2 options we have, and Pros and Cons

After going throught the graduated projects of cncf, we have found 2 pattern of MAINTAINER list.

Type1, json or yaml format, IaC, configuration style file

For examples:

• istio
• cilium

Usually, the project's infrustructure team will setup a bot or ci tool to sync these teams configuration to github teams, then each repo under the org can leverage github teams to create the codeowners file.

Using cilium for an example:

1. it has a repo team-manager to sync the configuration files to their github org teams.
2. it using a codeowners file instead of owners file in their main repo.

The Pros are:

1. github teams plus codeowners can bring more fine-grained permission management.
2. the sync from "file changes" to actual projects is smooth, no second operation are needed.

The Cons are:

1. it's complex to setup.
2. it needs extra effort in tooling.

Type2, markdown format, human read friendly, document style file

For examples:

• kubevela
• prometheus

Obviously, it's much easier to setup but it's not suitable when we have a lot of sub projects or work groups or teams.

The path

We will first add a type 2 MAINTAINER.md, in this step, we will discuss and figure out what teams and work-group we need to create.

Next, when we have enough members and maintainers we will invest the more automatic way -- to create a type 1 MAINTAINER list, we may even can recurit from the community.

[xuezhaojun]

Some questions:

• Is ocm-vscode-extension in our maintain scope?
• Should we addon the “Bootstrap Contributor” and “Emeritus Members” in this list? Llke [kubevela](https://github.com/kubevela/community/blob/dc3edce4c78ddb989c2cb9a9e120e75e047f3aa0/OWNERS.md?plain=1#L56C4-L56C20)
• Related issue: What’s the process and result of seperating policy?
• Need to avoid single point failure of each repo.

[xuezhaojun]

/assign @qiujian16
/assign @mikeshng

[qiujian16]

Integrations and Addons should be good enough

[xuezhaojun]

Changed.

[qiujian16]

we cannot have only one maintainer for this.

[xuezhaojun]

Another name in OWNERS file is David, added in here.

[xuezhaojun]

But I wondor whether David want to do review work of this sdk-go repo, as someone from community may throw PRs and questions to him because his name is under this repo.

[qiujian16]

we might need to tweak the sdk-go owner file

[mikeshng]

Could we have the format of:

name, company, [list of repos]

to eliminate duplicated contents?

[xuezhaojun]

Could we have the format of:

name, company, [list of repos]

to eliminate duplicated contents?

@mikeshng That way we may end with duplicated list of repos.

And I'm not sure whether we want to keep the [overall list] and [maintainers in different areas] in a same page.

For example, in prometheus, it's sperated:

• https://prometheus.io/governance/#team-members
• https://github.com/prometheus/prometheus/blob/main/MAINTAINERS.md

After we add all maintainers in the list, we shoult have toc to take a reivew

[xuezhaojun]

How about add a note here to clearify the different level of maintainibility? @qiujian16

Note: We welcome all community contributors to develop their addons in or out of the ocm-io and link them here.
The maintainers of integrations and addons only need to be responsible for their own repos.

[qiujian16]

yes, I think it is ok.

[xuezhaojun]

@qiujian16 The Integrations and Addons part is removed, added a "Note" to describe, and also link the "Integrations and Addons" section of website. Please take another look, thanks!

[mikeshng]

Should we add the community repo? It's one of our pinned repos.

[xuezhaojun]

Should we add the community repo? It's one of our pinned repos.

Good point, a new section of "Community and Docs" added.

[xuezhaojun]

tamalsaha is added as the PR is going to merge.

[mikeshng]

/lgtm

[qiujian16]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiujian16, xuezhaojun

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qiujian16]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment