diff --git a/README.md b/README.md index d83f98ac494f0c67b8627e4e9f8db459adf94628..c59205dbf2958b240f2136890ecc0ad03c6a8ca5 100644 --- a/README.md +++ b/README.md @@ -1,39 +1,55 @@ # infrastructure -#### 介绍 -{**以下是 Gitee 平台说明，您可以替换此简介** -Gitee 是 OSCHINA 推出的基于 Git 的代码托管平台（同时支持 SVN）。专为开发者提供稳定、高效、安全的云端软件开发协作平台 -无论是个人、团队、或是企业，都能够用 Gitee 实现代码托管、项目管理、协作开发。企业项目请看 [https://gitee.com/enterprises](https://gitee.com/enterprises)} +## 基础设施工作组的工作目标和范围 -#### 软件架构 -软件架构说明 +### 工作目标 +* 遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定 +* 该仓为基础设施工作组使用，所有规则及要求解释权归属基础设施工作组 +* Infrastructure SIG 组旨在构建围绕OpenHarmony的基础设施生态，提供网站维护和更新、文档的维护和更新、CICD门禁平台的升级、维护和更新; 同时吸引更多开发者参与共建。 +### 工作范围 -#### 安装教程 + * 将OpenHarmony官网源码开源, 并更新、维护、升级官网架构和内容 +SIG组将不断的吸引开发者为网站不断完善、更新、升级、修正 -1. xxxx -2. xxxx -3. xxxx +* 将OpenHarmony CICD门禁源码开源, 并更新、维护、升级门禁功能 +SIG组将不断的吸引开发者为 CICD 门禁不断完善、更新、升级、修正 -#### 使用说明 +* SIG组将不断的吸引开发者为 SIG组文档、 网站文档、 OpenHarmony技术文档、 OpenHarmony知识体系 并支撑文档体系不断完善、更新、升级、修正 -1. xxxx -2. xxxx -3. xxxx +* 生态扩展 +积极与开发者、高校和社区开发者协作，推动OpenHarmony基础设施建设的进程 -#### 参与贡献 -1. Fork 本仓库 -2. 新建 Feat_xxx 分支 -3. 提交代码 -4. 新建 Pull Request +## 基础设施组成员 +### Leader +- [youthdragon](youthdragon.wangyiming@huawei.com) -#### 特技 +### Committers列表 -1. 使用 Readme\_XXX.md 来支持不同的语言，例如 Readme\_en.md, Readme\_zh.md -2. Gitee 官方博客 [blog.gitee.com](https://blog.gitee.com) -3. 你可以 [https://gitee.com/explore](https://gitee.com/explore) 这个地址来了解 Gitee 上的优秀开源项目 -4. [GVP](https://gitee.com/gvp) 全称是 Gitee 最有价值开源项目，是综合评定出的优秀开源项目 -5. Gitee 官方提供的使用手册 [https://gitee.com/help](https://gitee.com/help) -6. Gitee 封面人物是一档用来展示 Gitee 会员风采的栏目 [https://gitee.com/gitee-stars/](https://gitee.com/gitee-stars/) +- [youthdragon](https://gitee.com/youthdragon) +- [MaDiXin](https://gitee.com/MaDiXin) +- [xzmu](https://gitee.com/xzmu) +- [wylyw78](https://gitee.com/wylyw78) + + +### 会议 + - 会议时间：双周例会，周五 10:00~12：00 + - 会议申报：无 + - 会议链接：腾讯会议或其他会议 + - 会议通知：请[订阅](https://lists.openatom.io/postorius/lists/oh-infrastructure.openharmony.io)邮件列表获取会议链接 + - 会议纪要：查看往期会议纪要，请点此[链接](https://gitee.com/openharmony_infra/meeting-notes) + +### 联系方式(可选) + +- 邮件列表：oh-infrastructure@openharmony.io + + +## 各子项目仓信息 + +官网： + +论坛： + +基础设施工具： \ No newline at end of file diff --git a/license b/license new file mode 100644 index 0000000000000000000000000000000000000000..29f81d812f3e768fa89638d1f72920dbfd1413a8 --- /dev/null +++ b/license @@ -0,0 +1,201 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/meeting-notes/.keep b/meeting-notes/.keep new file mode 100644 index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 diff --git a/meeting-notes/docs/.keep b/meeting-notes/docs/.keep new file mode 100644 index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 diff --git a/zh/infrastructure_governance.md b/zh/infrastructure_governance.md new file mode 100644 index 0000000000000000000000000000000000000000..00470867ec2fc76caaf2a24a112c5a1bd3cf1c4c --- /dev/null +++ b/zh/infrastructure_governance.md @@ -0,0 +1,82 @@ +**SIG 管理指南** + +该文档是 OpenHarmony 社区中的 SIG（Special Interest Group）管理指南初稿。为了保证 SIG 的有效管理和发展，该文档提供了申请新 SIG 的具体流程以及仓库管理和孵化准出的操作指南。 +# 1. **申请创建新SIG流程** +为了保证OpenHarmony社区中SIG的有效管理和发展，需要有规范的流程和评审机制进行支撑，以下是申请新SIG的具体流程： +## 1.1 梳理SIG组工作目标和范围 +在申请新的SIG之前，需要先梳理好该SIG组的工作目标和范围。这个步骤是为了确保SIG组的工作方向和范围能够清晰地呈现，同时也为后续的申请做好准备。 +参考SIG申请[模板](../meeting-notes/docs/openharmony_sig_template.pptx)，该模板中包含了申请时需要填写的相关信息和要求。 +## 1.2 提交SIG申请议题 +在完成SIG申请模板的填写后，需要将[申请议题](https://docs.qingque.cn/s/home/eZQB8yRFQfEFeAxk\_6JKZEE0q?identityId=1tbICPd8j3s)提交给OpenHarmony社区的PMC。该步骤的主要作用是让OpenHarmony社区的PMC能够对该申请进行初步审核。 + +## 1.3 PMC会议评审 +当PMC会议通过SIG申请议题时，即可进行如下步骤操作。 +### 1.3.1 创建自己的新申请SIG： +首先需要将OpenHarmony社区的代码库Fork到自己的Gitee下，并在sig目录下创建自己的SIG文件夹，再将SIG申请模板（sig_template）拷贝到该文件夹下。使用SIG模板创建自己的新SIG，并根据需要进行信息填写。 + +``` +git clone https://gitee.com/YOURGITEE/community + +cd ./community/sig + +cp -r sig_template sig_YOURSIGNAME + +cd sig_YOURSIGNAME +``` + +### 1.3.2 新申请SIG组信息填写 +在创建好自己的新SIG之后，需要根据需要完成新SIG组的信息填写。为便于更好的理解和填写SIG申请模板里的内容，建议先参考已有SIG的描述和说明。 + +``` +mv sig_template_cn.md sig_YOURSIGNAME_cn.md +mv sig_template.md sig_YOURSIGNAME.md +vim sig_YOURSIGNAME_cn.md +vim sig_YOURSIGNAME.md +``` + + ### 1.3.3 新SIG组织信息配置 +在完成新SIG组的信息填写后，还需要完成新SIG组织信息的配置。这个配置文件将会被用于后续SIG组仓库的创建，因此需要准确填写。 + +``` +vim sig/sigs\_list.toml +``` + +### 1.3.4 SIG组运作规范： +SIG组需要定期召开例会，讨论和总结SIG组领域工作，并向OpenHarmony PMC组织进行定期汇报。如果SIG组中的Leader角色有变动，需要及时知会OpenHarmony社区PMC成员，并对组织信息和仓库权限进行相应的调整。 + +# 2. **仓库管理** + +## 2.1 OpenHarmony 项目仓库管理流程 + +OpenHarmony 项目从开源建仓到孵化准出进入主线，需要经历以下几个步骤： + +1. **[申报架构 SIG](https://shimo.im/sheets/StzhuFkEk38enrnl/MODOC) 新建仓库申请的议题**：提交新建仓库的申请。 +2. **[申报架构 SIG](https://shimo.im/sheets/StzhuFkEk38enrnl/MODOC) 孵化准出预审的议题**：进行孵化准出的预审。 +3. **[申报 QA SIG](https://shimo.im/sheets/AQrrKb4pJCUFYkHR/MODOC) 孵化准出终审的议题**：完成孵化准出的终审，并解决所有遗留问题。 + +### 注意事项 + +在整个过程中，需要注意以下几点： + +1. **孵化准出条件**：除了满足基本的合规要求外，还必须完成孵化仓目标准出的 **关联仓的联合构建** 。 +2. **代码交叉检视**：为了实现提交代码的充分检视，要求新建仓库必须 **配置至少 2 名及以上的 Committer 以支持代码交叉检视功能** 。 + +## 2.2 SIG组仓库新增、退休、更名申请： +### 2.2.1 申请架构SIG评审 +参考[模板1--新增、退休、更名](../sig/sig_architecture/meetings/repository_review_template.pptx)准备对应的申请材料，申请[架构SIG](https://shimo.im/sheets/StzhuFkEk38enrnl/MODOC)议题评审。 + +参考[模板2--开源软件引入](../sig/sig_architecture/meetings/OpenHarmony_thirdparty_opensource_software_selection_analysis_templateV1.0.pptx)准备对应的申请材料，申请[架构SIG](https://shimo.im/sheets/StzhuFkEk38enrnl/MODOC)议题评审。 + +### 2.2.2 新增仓电子流申请： +架构SIG评审通过后，新增仓[操作指导](http://ci.openharmony.cn/workbench/ciCommunity)：“操作指南” --> "SIG管理" --> “SIG仓申请”。 +### 2.2.3 仓库退休、更名电子流申请： +架构SIG评审通过后，仓库退休、更名[操作指导](http://ci.openharmony.cn/workbench/ciCommunity)：“操作指南” --> "SIG管理" --> “仓管理”。 + +## 2.3 仓库孵化准出： +### 2.3.1 申请架构SIG孵化预审： +[申请议题](https://shimo.im/sheets/StzhuFkEk38enrnl/MODOC)进行孵化准出架构预审，参考[模板](../sig/sig_architecture/meetings/repository_review_template.pptx) 准备对应的申请材料。 + +### 2.3.2 申请质量SIG孵化准出评审： +[申请议题](https://shimo.im/sheets/AQrrKb4pJCUFYkHR/MODOC)：进行孵化准出评审，参考[准出标准](../sig/sig_qa/guidance_for_incubation_project_graduation_cn.md)准出孵化准出材料。 +### 2.3.3. 提交仓库孵化准出电子流： +质量SIG准出评审通过后，提交[孵化准出电子流](http://ci.openharmony.cn/workbench/ciCommunity)： “操作指南” --> "SIG管理" --> “孵化报告”。 \ No newline at end of file