feat(doc): Update maintainer list according to activity and add steering commitee member…

[leonrayang]

…ring commitee member

Motivation

Explain here the context, and why you're making that change. What is the problem you're trying to solve.

---

Some maintainers are not active enough, or there are too many overlapping positions within the maintainers.
A steering committee has been added to better achieve community autonomy governance

For a long time, important project decisions have been made by core maintainers through platforms like WeChat. In order to improve project governance and ensure transparency of information, a Steering Committee has been established. The initial members of the Steering Committee are selected from the current core maintainers. Following the principle of vendor neutrality, the committee consists of core members from several companies that have the highest level of contribution and influence in the project.

Modifications

Describe the modifications you've done.

---

@bboyCH4 @jadewang198510 transfer to committer

Types of changes

Show in a checkbox-style, the expected types of changes your project is supposed to have:

---

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Bugfix (non-breaking change which fixes an issue)
• Documentation Update (if none of the other choices apply)
• So on...

Verifying this change

(Please pick either of the following options.)

---

• Make sure that the change passes the testing checks.

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• This can be verified in development debugging
• This can be realized in a mocked environment, like a test cluster consisting in docker

(or)

This change MUST reappear in online clusters, or occur in that specific scenarios.

Does this pull request potentially affect one of the following parts:

Which of the following parts are affected by this change?

---

• Master
• MetaNode
• DataNode
• ObjectNode
• AuthNode
• LcNode
• Blobstore
• Client
• Cli
• SDK
• Other Tools
• Common Packages
• Dependencies
• Anything that affects deployment

Documentation

Is there a chinese and english document modification?

---

• doc
• doc-required
• doc-not-needed
• doc-complete

Review Expection

How long would you like the team to be completed in your contributing?

---

• in-two-days
• weeks
• free-time
• whenever

Matching PR in forked repository

enter the url if has PR in forked repository.

---

PR in forked repository:

[netlify]

✅ Deploy Preview for cubefs-check ready!

Name	Link
🔨 Latest commit	450fa70
🔍 Latest deploy log	https://app.netlify.com/sites/cubefs-check/deploys/66189bf07aba5a0009d2dc99
😎 Deploy Preview	https://deploy-preview-3311--cubefs-check.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mervinkid]

Approve to merge.

[xiaochunhe]

LGTM

[leonrayang]

+1

[Cloudstriff]

+1

[Victor1319]

+1

[sejust]

+1

[cessory]

+1

[bboyCH4]

+1