Hi all,

https://etherpad.openeuler.org/p/community-gov-weeklymeeting

Agenda

1. Review the actions from last meetings

1) Several process for the development @yangli https://gitee.com/openeuler/community/issues/I1EM1E?from=project-issue https://docs.qq.com/doc/DWllVcWRLS1dTZWJX https://docs.qq.com/doc/DWnJ4a2ZWYklxSUd5 https://docs.qq.com/doc/DWmVnVEVqWVZ5aUNB https://gitee.com/openeuler/community/pulls/502

BIG THANKS to Yangli

2) Compatibility Status: ongoing - Hardware in the south band 南向硬件: OK - Software in the north band 北向软件: 不叫兼容性。目标是北向软件能够进入openEuler源；当前没有进入的，整一个列表让用户知道从哪里获取，放在Gitee上，不在openEuler网页上。 2020-05-19: no progress 2020-06-16: Deadline 2020-09-15

3) The repository community re-design - Governance(including the introduction to TC, SIGs and etc.) can be displayed in the website. - Technical information such as openeuler.ymal can be still in gitee repo. Question: has this been considered in the re-design of openEuler website? @George @genedna.

2. Review the issues from the community 1) about statistics (metrix) Fred Li submitted the requirements about metrics. See LoC: https://gitee.com/opensourceway/community/issues/I1JEUD Group by organization: https://gitee.com/opensourceway/community/issues/I1JEWL accumulated data: https://gitee.com/opensourceway/community/issues/I1JF0I https://gitee.com/opensourceway/community/issues/I1K2I0 Find more in https://gitee.com/opensourceway/community/

2) @genedna, this is about Summer of Code 2020 https://gitee.com/openeuler/community-issue/issues/I1K0LE

3) 部分openeuler仓库源码还带有厂商标志 https://gitee.com/open_euler/dashboard/issues?id=I1K60F https://gitee.com/src-openeuler/pcs

4) what is your opinion on such foundamental knowledge about contribution? https://gitee.com/openeuler/community/issues/I1IY20?from=project-issue https://gitee.com/openeuler/community/issues/I1I6Y7?from=project-issue

Such should be considered. We need consider more training or guidance in various ways, like video training, guidance, blog, openness.

3. Review the pull requests from the community 1) There are many SIGs created or being created, but it seems that the SIGs categories are not clear. Has it or will it lead to issues? examples: education: https://gitee.com/openeuler/community/pulls/558 desktop-app: https://gitee.com/openeuler/community/pulls/566 contributors don't know which sig one software like matlab shoud be in.

Conclusion: We need review the SIG status periodically. Incubation/mentoring may be required, or in other words, there should be one more requirement about the SIG team members with experience. Openness is another shortage.

2) The README for release manager. May we take some time to review it? https://gitee.com/openeuler/community/pulls/502

4. Open discussion 1) form zyp, to improve the issues handling, it is proposed to add 2 functions: - assign the issues to owners - add bugzilla will be discussed in today's infrastructure weekly meeting.

Actions from this meeting: @George to create one issue in website to follow the requirement: - Governance(including the introduction to TC, SIGs and etc.) can be displayed in the website.

@genedan to check with Houjian on https://gitee.com/src-openeuler/pcs

@Fred Li to add one label like "sig/governance“ in community.

@Fred Li to open one issue to improve the SIGs.