mirror of
https://gitee.com/openharmony/community
synced 2024-11-22 22:30:06 +00:00
0913e807a3
* 更新文档图片路径 |
||
---|---|---|
.gitee | ||
meeting-notes | ||
rfcs | ||
sig | ||
todo | ||
zh | ||
LICENSE | ||
README_EN.md | ||
README.md |
OpenHarmony Community
Welcome to the OpenHarmony community.
English | 简体中文
Introduction
The community repository stores the following content:
- Community Governance Organizational Structure
- Contributing to the Community
- Contributor Agreement for Contributing to the Community
- Communications in the Community
- Responses to Security Issues
- Project Logo
Community Governance Organizational Structure
The Project Management Committee (PMC) manages the OpenHarmony community.
Contributing to the Community
See How to Contribute to the OpenHarmony Community.
Signing the Developer Certificate of Origin
You must sign the Developer Certificate of Origin (DCO) before you can contribute to the community.
Sign the DCO and check the signing status.
Communications in the Community
OpenHarmony Mailing List
Address | Introduction | Description |
---|---|---|
contact@openharmony.io | Public mailing list | Public mailing list of the OpenHarmony community. You can send a signed CLA to this mailing list. |
dev@openharmony.io | Development mailing list | Mailing list for discussing development issues in the OpenHarmony community. Any developer can subscribe to this mailing list. |
cicd@openharmony.io | CI mailing list | Mailing list for continuous integration and continuous delivery (CI/CD) of the OpenHarmony community. Any developer can subscribe to this mailing list. |
pmc@openharmony.io | PMC mailing list | Mailing list for PMC discussion. PMC members can subscribe to this mailing list. |
scy@openharmony.io | Mailing list for security issues | Mailing list for reporting OpenHarmony security issues. |
scy-priv@openharmony.io | Security group mailing list | Mailing list for discussing how to handle security issues. Security group members can subscribe to this mailing list. |
Project Logo
Please refer to the trademark usage guidelines from OpenHarmony LOGO.