From 3a86047014e9db589fbb27b4e8a7d00f3595d723 Mon Sep 17 00:00:00 2001 From: lihengwei Date: Wed, 3 Apr 2024 16:05:00 +0800 Subject: [PATCH] feature: adjust README.en.md Signed-off-by: lihengwei --- README.en.md | 108 +++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 79 insertions(+), 29 deletions(-) diff --git a/README.en.md b/README.en.md index c739d68..9b8ab6a 100644 --- a/README.en.md +++ b/README.en.md @@ -1,38 +1,88 @@ -###Mission -QA team aims to test softwares make up openEuler release, our goal is to improve openEuler community quality and testing capability. - -###Scope -Main activities: -- Build test capability and involve community developers to participate, use and contribute -- Draft, release and maintain release criteria -- Develop and maintain test tools which promote code development and execution efficiency -- Make test plan and choose the cases according the release plan -- Running test open days which focuse on testing a specific feature or component - -### Repositories and description managed by this SIG -The repositories related to QA are listed below -- https://gitee.com/openeuler/avocado +# QA SIG + +QA(Quality Assurance) project team tests the openEuler community release software, with the goal of continuously improving the release quality and community testing ability of the openEuler community. The main activities include: + +- Build community testing capabilities to engage, use, and contribute more community developers +- Develop test tools to improve code development efficiency and test coverage +- Develop test plan and plan test activities according to release plan +- Develop, publish and maintain release standards for managed releases +- Operational Testing Open Day event focusing on testing of new features and critical components + +# Organizational session + +- Open meeting time: every Wednesday afternoon, 4:00 ~5:00 Beijing time, please subscribe to qa@openeuler.org for conference related information + +# Member + +### Maintainer List + +- wu_fengguang +- charlie_li(@charlie_li), since October 2019 +- wubodong(@walkingwalk), since November 2019 +- kuhnchen(@kuhnchen18), since December 2019 +- speacher +- rigorous +- lemon-higgins +- lutianxiong +- disnight, since December 2021 + +### Committer List + +- Air9(@air9),since january 2020 +- wsf0824(@wsf0824),since December 2019 +- panny060(@panny060),since December 2019 +- jiuhanjiu(@jiuhanjiu),since December 2019 + +# maintainer/committer campaign & exit rules + +### basic rules + +1. Candidates have strong sense of responsibility and traceable contributions to QA sig +2. Maintainer has a clear understanding of sig development and can provide constructive advice, committer has professional ability to responsible warehouse/feature, etc. +3. Number of people required: maintainer [5, 9]; committer depends on the development type sig of the community. No upper limit is set temporarily. It is not recommended to exceed 15. +4. The election process is open and democratic, conclusions are reached as soon as possible, and specific actions are taken to solve the remaining problems, which can be closed quickly. +5. committer campaigns quarterly, maintainer campaigns semi-annually, review of contributions of existing members semi-annually + +### Maintainer campaign rules (January/July of each year): + +1. Become a commiter for more than one quarter, and participate in QA-sig regular meetings for half a year (attendance rate>=75%) +2. Participate in the community version release test as a feature test owener, record the whole process information (process data/test strategy/test report/problem data, etc.) in the community and test platform according to the process (the total number of defect issues in QA warehouse pr+ community is greater than 40) +3. As a test expert, build 1 or more special test capabilities from zero for the community and incorporate them into the version operation +4. Other series of contributions (process change/engineering capability, etc.) that have a greater impact on QA PS: Except for 1, which is a mandatory option, the rest can satisfy one item. The final conclusion shall be subject to the review conclusion of the regular meeting. + +### Committer election rules (January/April/July/October of each year): + +1. Participation in QA-sig meetings for one quarter (attendance rate>=75%) +2. Participate in a feature test as a community feature tester, and make certain contributions to the community and test platform (the total number of defects in the pr+ community of QA warehouse is greater than 20) +3. As a test engineer, participate in the construction, contribution and maintenance of 1 or more community specific tests (pr and issue quantity requirements are the same as 2) +4. Other series of contributions to QA (process change/engineering capability, etc.) PS: Except 1 is a mandatory option, the rest can satisfy one item, and the final conclusion shall be subject to the review conclusion of the regular meeting. + +### Rules for Maintaininger/Committer Exit + +1. No contribution in QA-sig for nearly 6 months +2. Documenting historical contributions in QA and community + +### Maintainer/Committer handover mechanism + +1. The handover request should be submitted one month before the committer campaign meeting by community mail to qa mailbox, and reviewed at the latest committer campaign meeting. +2. The minimum contribution of handover personnel shall meet the requirements of committer (qa participation time may be relaxed as appropriate) + +# contact information + +- [qa@openeuler.org](mailto:qa@openeuler.org) + +# list of items + +Project Name: QA repository Address: + - https://gitee.com/openeuler/avocado-vt - https://gitee.com/openeuler/tp-libvirt - https://gitee.com/openeuler/tp-qemu -- https://gitee.com/openeuler/quality-assurance +- https://gitee.com/openeuler/QA - https://gitee.com/openeuler/EulerRobot - https://gitee.com/openeuler/compiler-test - https://gitee.com/openeuler/package-reinforce-test - https://gitee.com/openeuler/integration-test - https://gitee.com/openeuler/container-test - https://gitee.com/openeuler/test-tools - -Maintainers -- wu_fengguang -- charlie_li(@charlie_li) -- wubodong(@walkingwalk) -- kuhnchen(@kuhnchen18) -- speacher -- rigorous - -### Mailing list -qa@openeuler.org -### Conference Information -welink -Conference INFO will be sent by mail (qa@openeuler.org) bi-weekly at wednesdays 4 p.m for about an hour. +- https://gitee.com/openeuler/mugen -- Gitee