Skip to content

Latest commit

 

History

History
54 lines (43 loc) · 3.13 KB

GOVERNANCE.md

File metadata and controls

54 lines (43 loc) · 3.13 KB

Governance

Table of Contents

  1. Overview
  2. Roles and Responsibilities
  3. Community Engagement
  4. Contributing
  5. Code of Conduct
  6. Licenses

Overview

KusionStack is an open-source tech stack designed to empower platform teams in developing production-ready, self-service Internal Developer Platforms (IDPs).

This documentation defines and documents the governance framework for the KusionStack project.

Roles and Responsibilities

KusionStack the community defines the following roles and responsibilities:

  • Members: Use KusionStack projects and provide feedback.
  • Contributors: Actively participate in iterating the KusionStack projects, including both code and non-code contributions.
  • Approvers: On top of being a contributor, review and approve code and documentation contributions.
  • Maintainers: On top of being an approver, make and set technical design decisions and directions.

More details on roles and responsibilities including the criteria for each can be found in ROLES.md.

Community Engagement

  • Communication Channels:
    • Slack
    • X
    • Medium
    • WeChat (Chinese)
    • DingTalk: 42753001 (Chinese)
  • Regular Meetings:
    • The community meets every other Thursday. The next on is Oct.17th, 2024.
    • The recordings and meeting notes will be posted in GitHub discussions.
  • Offline Engagements:
    • All forms of engagements are welcomed! Majority of the KusionStack maintainers are located in Shanghai, China and will be regularly attending conferences in the industry. Please reach out via the communication channels above!

Contributing

Code of Conduct

KusionStack follows the CNCF Code of Conduct.

Licenses

KusionStack projects are distributed under the [Apache-2.0 licenses]. The license texts can be found in each project repository. Some examples:

More detailed license scan including analysis on 3rd party dependencies can be found in each project's README. Some examples: