March 2020 - Community - mailweb.openeuler.org

Re: [community governance] update the committer list of storage sig
by wubo (T) 10 Jul '20

10 Jul '20

+1 I'm in favor of her as a committer. > -----邮件原件----- > 发件人: liuzhiqiang (I) > 发送时间: 2020年3月31日 20:46 > 收件人: community(a)openeuler.org; wubo (T) <wubo40(a)huawei.com>; Huyan > (B) <hu.huyan(a)huawei.com>; Huyan (B) <hu.huyan(a)huawei.com> > 抄送: linfeilong <linfeilong(a)huawei.com>; Yanxiaodan > <yanxiaodan(a)huawei.com> > 主题: [community governance] update the committer list of storage sig > > Hi all, > > Due to personal reason, @hy-euler is no longer serving as a committer for > storage sig. @hy-euler has done a great work as a committer. Deeply thank > @hy-euler for all her contributions to the storage sig. > > As the tasks of this team is growing, we need a new committer to take over > @hy-euler job. @volcanodragon has beening contributing for a long time, and he > has shown skills in open source community. > So I elect @volcanodragon as a new committer. > > I would like to hear our current contributors' opinions on elect @volcanodragon > as a new committer. > > -- > Regards > liuzhiqiang26

3 6

[community governance]Nonimate @blueskycs2c as committer
by Fred Li 02 Apr '20

02 Apr '20

Hi all, Currently there are 2 members working as committers for community governance. You can find the details [1]. As the tasks of this team is growing, ( [2] is the open or ongoing tasks), if there are more committers working on those, that would be great to the team. @blueskycs2c has beening contributing for not such long time, but she has shown warm heart, skills in open source community and good understanding on community culture and governance. Please find her contribution to the repo community in [3]. And evey outside of this repo, she has many valuable proposals and findings, and [4] is one of them. I would say due to limitations of Gitee, it is not easy to search out all her contributions, so the following is only a few part. I would like to hear our current contributors' opinions on nonimating her as committer. [1] https://gitee.com/openeuler/community#the-rest-of-folders-under-this-repo [2] https://gitee.com/openeuler/community/wikis/All%20the%20open%20tasks%20abou… [3] https://gitee.com/openeuler/community/pulls/223 https://gitee.com/openeuler/community/pulls/186 https://gitee.com/openeuler/community/pulls/144 [4] #I1C1PUSet the programming language of the package -- Regards Fred Li (李永乐)

5 6

[community governance] update the committer list of storage sig
by Zhiqiang Liu 31 Mar '20

31 Mar '20

Hi all, Due to personal reason, @hy-euler is no longer serving as a committer for storage sig. @hy-euler has done a great work as a committer. Deeply thank @hy-euler for all her contributions to the storage sig. As the tasks of this team is growing, we need a new committer to take over @hy-euler job. @volcanodragon has beening contributing for a long time, and he has shown skills in open source community. So I elect @volcanodragon as a new committer. I would like to hear our current contributors' opinions on elect @volcanodragon as a new committer. -- Regards liuzhiqiang26

1 0

openEuler Community Governance Weekly meeting
by Liyongle (Fred) 30 Mar '20

30 Mar '20

Please join the weekly meeting and discuss how to improve the community governance. - Time 10:00-11:00 am, Tuesday, Beijing Time; 2:00-3:00 am, Tuesday, UTC. Agenda - pending issues from last week - key tasks we need to discuss [2] - Metrics: who is who; Zhangxia - Metrics: organizations; Ivye - Metrics: what has happened before and after openEuler 20.03 LTS was release. Zhongjun - open discussion - Meeting link: https://welink-meeting.zoom.us/j/175956455 [1] https://gitee.com/openeuler/community/blob/master/meeting_records/README.md [2] https://gitee.com/openeuler/community/wikis/All%20the%20open%20tasks%20abou…

1 0

openEuler Community Governance Weekly meeting
by Liyongle (Fred) 30 Mar '20

30 Mar '20

Please join the weekly meeting and discuss how to improve the community governance. - Time 10:00-11:00 am, Tuesday, Beijing Time; 2:00-3:00 am, Tuesday, UTC. - Meeting link: https://welink-meeting.zoom.us/j/175956455 [1] https://gitee.com/openeuler/community/blob/master/meeting_records/README.md [2] https://gitee.com/openeuler/community/wikis/All%20the%20open%20tasks%20abou…

2 1

help
by gopanic 29 Mar '20

29 Mar '20

Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

help
by Bruce 28 Mar '20

28 Mar '20

发自我的iPhone

2 1

jackbrucezw@163.com
by Bruce 28 Mar '20

28 Mar '20

发自我的iPhone

1 0

撤回: [community governance]Nonimate @blueskycs2c as committer
by Haolijuan 28 Mar '20

28 Mar '20

Haolijuan 将撤回邮件“[Community] [community governance]Nonimate @blueskycs2c as committer”。

1 0

Re: [Tc] SIG组工作审视
by Fred Li 27 Mar '20

27 Mar '20

Happy to see technical committee members will mentor us. Many thanks in advance. On Fri, Mar 27, 2020 at 7:54 PM myeuler <myeuler(a)163.com> wrote: > > Hi, All tc members, Please do the SIG work review according to this list: > 1. xinwei hu : Virt, system-tool, storage, sig-kernel, sig-community > 2. hong xie : sig-bounds_checking_function, sig-ai-bigdata, security-committee, Runtime, Programming-language > 3. hanjun guo : Private, Packaging, oVirt, Others, Networking, > 4. xiuqi Xie : Kernel, kae, iSulad, Infrastructure, doc > 5. hailiang Zhang : Desktop, DB, Container, Computing > 6. Xun Wang : Compiler, Base-service, A-Tune, atune > 7 Wei Xiong : dev-util, Application, sig-template, sig-mate-desktop > > 请各位委员按照上述的分组对SIG组进行审视，审视的内容包含： > 1. SIG组是否正常运作。是否有明确的负责人。 > 2. 相关的项目是否已经有输出，相关软件是否已经进入gitee仓。 > 3. 相关SIG的主页面是否有明确的介绍信息和完善的说明。 > > 下次TC meeting我们审视一下这些SIG的运作，一些SIG是否需要保留或者合并请各位委员给出建议和意见。 > > 谢谢。 > > > > > _______________________________________________ > Tc mailing list -- tc(a)openeuler.org > To unsubscribe send an email to tc-leave(a)openeuler.org -- Regards Fred Li (李永乐)

1 0

Re: [Tc] [RFC] crystal-ci test as service
by Yang Li 25 Mar '20

25 Mar '20

6 9

[tc][package]About how to manage and maintain packages/dependencies
by Fred Li 25 Mar '20

25 Mar '20

Hi TC members, Infrastructure team and community members, Recently there are many issues about adding dependencies or new packages [1][2][3]. As a linux operating system, it is extremely critical to manage the dependencies. As we know, Technical committee is managing the packages management policy, however who maintain the new packages is not clear. I have draft idea on this. Please give your advice, opinions on how to maintain the dependencies. - policy. Dependencies are still packages, thus they follow the flow on how to introduce the packages into openEuler community. - Who to maintain: if the packages are new and only dependencies, probably one specific team is an option to do this. - How to automate: Infrastructure should provide a function on getting update from upstream automatically - Dependencies management: an expert should maintain the detailed work on how to choose for ISO and yum for each specific version of release. [1] https://gitee.com/openeuler/community-issue/issues/I1CBYV?from=project-issue [2] https://gitee.com/openeuler/community-issue/issues/I1BHND?from=project-issue [3] https://gitee.com/openeuler/community-issue/issues/I1CBW5?from=project-issue -- Regards Fred Li (李永乐)

2 1

[新SIG提案]申请成立UKUI SIG
by Joey Ma 25 Mar '20

25 Mar '20

Hi Dear TC, We are so pleased to propose to apply a new SIG UKUI, please check it out at PR https://gitee.com/openeuler/community/pulls/291 . Please let me have a brief introduction on UKUI for you. UKUI is designed by KylinSoft Co., Ltd. UKUI is a lightweight desktop environment based on pluggable framework for Linux and other Unix-like Distributions. It provides a simpler and more enjoyable experience for browsing, searching, and managing your computer.It is developed using GTK and Qt. It's comprised of ukui-panel, ukui-sidecar and many other components. Please see the official site http://ukui.org/ for more information. The UKUI SIG will work on making UKUI available to all of openEuler users. Looking forward to hearing from you. Thanks and take care. Regards, Joey

4 6

openEuler Community Governance Weekly meeting
by Liyongle (Fred) 22 Mar '20

22 Mar '20

Please join the weekly meeting and discuss how to improve the community governance. - Time 10:00-11:00 am, Tuesday, Beijing Time; 2:00-3:00 am, Tuesday, UTC. - Meeting link: https://welink-meeting.zoom.us/j/152428852 [1] https://gitee.com/openeuler/community/blob/master/meeting_records/README.md [2] https://gitee.com/openeuler/community/wikis/All%20the%20open%20tasks%20abou…

1 0

Introduction to the new commentable and rename_from features supported in ci-bot
by joey 20 Mar '20

20 Mar '20

Hi all: I’m Joey and from infrastructure team of openEuler. So glad to see you guys and hope everybody is doing well. I’m writing here to have a brief introduction to the new features provided by ci-bot. We believe they would be helpful for your repository management. As it’s known to us, ci-bot is an automation system to handle lots of infrastructure stuff, such as gitee web hook events, repository management, owner management and etc. For more details about our lovely ci-bot, please refer to https://gitee.com/openeuler/ci-bot <https://gitee.com/openeuler/ci-bot>. For now, please let me elaborate how you can make use of the two features to ease the repository management. 1. Add commentable property for repository definition in openeuler.yaml or src-openeuler.yaml under openeuler/community. PR is: https://gitee.com/openeuler/ci-bot/pulls/26 <https://gitee.com/openeuler/ci-bot/pulls/26> . > Previously users could leave a comment at the index page of the project, which is a great feature provided by Gitee. While as we all know, the more conventional way is posting an issue request for questions/bugs/features. So after discussion, we finally consider to disable the comment-to-repository feature for all repositories. So here comes to this functionality, which adds an extra commentable property. If it’s not specified, the default value is false of boolean type. > Actually, you DO NOT need to pay any attention to this new property since non-commentable repository is strongly recommended. Just think it never exists. The example is shown as below, ```yaml community: openeuler repositories: - name: A-Tune description: "" type: public commentable: false # User CAN NOT see or leave comment to repository - name: ci-bot description: "" type: public commentable: true # Users CAN see and leave comment to repository - name: community description: "" type: public # User CAN NOT see or leave comment to repository ``` 2. Add rename_from property for repository definition in openeuler.yaml or src-openeuler.yaml under openeuler/community. PR is: https://gitee.com/openeuler/ci-bot/pulls/27 <https://gitee.com/openeuler/ci-bot/pulls/27> . > Please let me take a real case for example. In PR https://gitee.com/openeuler/community/pulls/128 <https://gitee.com/openeuler/community/pulls/128>, iSulad team wants to change the names of three repositories: iSulad-kit ===> iSulad-img iSulad-lxcfs-toolkit ===> lxcfs-tools iSulad-tools ===> syscontainer-tools > As the PR is shown to us, the code diff is as below, which leaded ci-bot to completely remove the old repository and create a new empty one with the new name, causing loss of all the existing issues and PRs. ```diff - - name: iSulad-kit + - name: iSulad-img description: "" - - name: iSulad-lxcfs-toolkit + - name: lxcfs-toolkit description: "" - - name: iSulad-tools + - name: syscontainer-tools description: "" ``` > While after the PR has been merged, the diff would be like the following. This could make use of the newly supported renaming-repository Gitee OpenAPI to keep all the issues and PRs unchanged. ```diff - - name: iSulad-kit + - name: iSulad-img description: "" + rename_from: iSulad-kit - - name: iSulad-lxcfs-toolkit + - name: lxcfs-toolkit description: "" + rename_from: iSulad-lxcfs-toolkit - - name: iSulad-tools + - name: syscontainer-tools description: "" + rename_from: iSulad-tools ``` > While it should noted that rename_from is not declarative but imperative cause it will take effect only for once and not stored in DB. So if we remove it from repository definition after renaming operation has been finished, nothing will happen. Hopefully I have explained clear enough. Currently the new functionalities are not in production yet and your feedback is rather important to us. So please reply this email for further discussion as soon as you have any doubt. Looking forward to your feedback. Take care! Best regards, Joey

3 2

Notice to upgrade license from Mulan PSL v1 to v2
by Fred Li 20 Mar '20

20 Mar '20

Hi all, As you know, openEuler community uses Mulan PSL v1 now as the open source license. Because Mulan PSL v2 was just approved by OSI, it is proposed to upgrade the license from v1 to v2 for the projects which use Mulan PSL v1 now. If you have different opinion on this, please send email to community(a)openeuler.org by March 19th, 2020. The license updating will not be valid until March 19th, 2020. Find the details below: [1] http://blog.openeuler.org/post/fred_li/2020-03-03-license-update/ -- Regards Fred Li (李永乐)

1 1

答复: [Infra] [metrics] welcome to join the task to design and implement community operation metrics
by Haolijuan 19 Mar '20

19 Mar '20

Version 1.0 of user role definition [3] has been output, including user role definition, data access definition, key indicators and statistical analysis dimensions. Welcome to confirm if v1.0 content is OK. @infra, Please focus on the attachment in [3], We can start the discussion of implementation design. Thank you. [3] https://gitee.com/openeuler/community/issues/I1BSJ4?from=project-issue -----邮件原件----- 发件人: Haolijuan 发送时间: 星期一, 2020年3月16日 16:20 收件人: 'Fred Li' <yongle.li(a)gmail.com>; community <community(a)openeuler.org>; infra <infra(a)openeuler.org> 主题: Re: [Infra] [metrics] welcome to join the task to design and implement community operation metrics Hi all, First, thanks Fred Li, imjoey, zhongjun and maquanyi for the contribution. For the role definition in the user funnel model, I created a new issue[3] for review. Welcome to provide your review comments before March 19,2020. Thank you in advance. [3] https://gitee.com/openeuler/community/issues/I1BSJ4?from=project-issue -----邮件原件----- 发件人: Fred Li [mailto:yongle.li@gmail.com] 发送时间: 星期四, 2020年3月12日 22:47 收件人: community <community(a)openeuler.org>; infra <infra(a)openeuler.org> 主题: [Infra] [metrics] welcome to join the task to design and implement community operation metrics Hi all, @ivye has opened [1] to start analyze the requirement about community operation metrics. [2] is the shared document to collect your idea. @zhongjun2 is joining this task and will implement the requirements. @imjoey and I (@zerodefect) have drafted some in [2]. It is an interesting topic, and if you would like to try, join us. Sorry for the content is in Chinese so far, and if anyone needs English, please let me know. [1] https://gitee.com/openeuler/community/issues/I1BAO0 [2] https://docs.qq.com/doc/DRmlaYnZSbEViRm5G -- Regards Fred Li (李永乐) _______________________________________________ Infra mailing list -- infra(a)openeuler.org To unsubscribe send an email to infra-leave(a)openeuler.org

2 1

[blog]A blog from @Shinwell_Hu, chair of Technical Committee
by Fred Li 19 Mar '20

19 Mar '20

Hi all, Shinwell_Hu(@Shinwell_Hu), serving the community as the Chair of Technical Committee, just posted a blog to introduce himself at [1[. And, you are more than welcome to post your blog following [2]. [1] http://blog.openeuler.org/post/shinwell_hu/2020-03-16-a-status-update-of-ea… [2] http://blog.openeuler.org/guidance/ -- Regards Fred Li (李永乐)

1 0

The Guide of Contributor V2.0, thank you for your review~~~
by Yang Li 17 Mar '20

17 Mar '20

2 1

Re: [Infra] [metrics] welcome to join the task to design and implement community operation metrics
by Haolijuan 16 Mar '20

16 Mar '20

Hi all, First, thanks Fred Li, imjoey, zhongjun and maquanyi for the contribution. For the role definition in the user funnel model, I created a new issue[3] for review. Welcome to provide your review comments before March 19,2020. Thank you in advance. [3] https://gitee.com/openeuler/community/issues/I1BSJ4?from=project-issue -----邮件原件----- 发件人: Fred Li [mailto:yongle.li@gmail.com] 发送时间: 星期四, 2020年3月12日 22:47 收件人: community <community(a)openeuler.org>; infra <infra(a)openeuler.org> 主题: [Infra] [metrics] welcome to join the task to design and implement community operation metrics Hi all, @ivye has opened [1] to start analyze the requirement about community operation metrics. [2] is the shared document to collect your idea. @zhongjun2 is joining this task and will implement the requirements. @imjoey and I (@zerodefect) have drafted some in [2]. It is an interesting topic, and if you would like to try, join us. Sorry for the content is in Chinese so far, and if anyone needs English, please let me know. [1] https://gitee.com/openeuler/community/issues/I1BAO0 [2] https://docs.qq.com/doc/DRmlaYnZSbEViRm5G -- Regards Fred Li (李永乐) _______________________________________________ Infra mailing list -- infra(a)openeuler.org To unsubscribe send an email to infra-leave(a)openeuler.org

1 0

openEuler Community Governance Weekly meeting
by Liyongle (Fred) 16 Mar '20

16 Mar '20

Please join the weekly meeting and discuss how to improve the community governance. - Time 10:00-11:00 am, Tuesday, Beijing Time; 2:00-3:00 am, Tuesday, UTC. - Meeting link: https://welink-meeting.zoom.us/j/830090060 [1] https://gitee.com/openeuler/community/blob/master/meeting_records/README.md [2] https://gitee.com/openeuler/community/wikis/All%20the%20open%20tasks%20abou…

2 1

[package][license][question] Is the OSS accepted by openEuler if it depends on hardware with license?
by Fred Li 13 Mar '20

13 Mar '20

Hi TC members, Could you please take a look at [1]? > 目前了解到有些项目开发了KAE加速库，软件本身是开源的，软件本身全部开源，但是需要依赖硬件license的特性才能开启的软件，是否可以引入到openEuler社区，进而纳入到openEuler发行光盘 [1] https://gitee.com/openeuler/community/issues/I1AQUY -- Regards Fred Li (李永乐)

1 0

This is a test email from @huawei
by Liyongle (Fred) 13 Mar '20

13 Mar '20

Sorry for this. Fred 李永乐

1 0

[metrics] welcome to join the task to design and implement community operation metrics
by Fred Li 12 Mar '20

12 Mar '20

Hi all, @ivye has opened [1] to start analyze the requirement about community operation metrics. [2] is the shared document to collect your idea. @zhongjun2 is joining this task and will implement the requirements. @imjoey and I (@zerodefect) have drafted some in [2]. It is an interesting topic, and if you would like to try, join us. Sorry for the content is in Chinese so far, and if anyone needs English, please let me know. [1] https://gitee.com/openeuler/community/issues/I1BAO0 [2] https://docs.qq.com/doc/DRmlaYnZSbEViRm5G -- Regards Fred Li (李永乐)

1 0

Re: [Discusion] How can I become a member of Technical Committee in openEuler
by Liyongle (Fred) 12 Mar '20

12 Mar '20

Hi all, First I apologize that the email title should not include [isulad]. Some friends have left their comments here and hope you have to read or comment. https://gitee.com/openeuler/community/issues/I1B0B4 Your opinion matters. Fred 李永乐 -----Original Message----- From: Fred Li [mailto:yongle.li@gmail.com] Sent: Saturday, March 7, 2020 13:03 To: community <community(a)openeuler.org>; tc <tc(a)openeuler.org>; infra <infra(a)openeuler.org>; dev(a)openeuler.org; isulad(a)openeuler.org; a-tune(a)openeuler.org Subject: [Isulad] [Discusion] How can I become a member of Technical Committee in openEuler Hi openEuler community members, First of all, I will write Chinese in this email as all the information below are written in English in [1]. The purpose of this email is to ask you to leave your opinions in [1]. 各位openEuler社区的朋友们，我陆续会收到一些关于成为openEuler技术委员会成员的请求。比如如下： 1）我们公司做OS的，很大很有经验，公司可以派几名员工成为TC成员 2）某某是我们的架构师，很有经验，能否安排他成为TC成员 3）如果我给openEuler社区捐款，能否安排我成为TC成员？听到这类说法，一方面我很开心，因为说明有人关心openEuler社区并且有意进行技术贡献；一方面也有些困惑，因为可能因为我们没有解释清楚某些席位（比如TC成员、Committer）在开源社区的权利责任和义务是什么。于是我想请大家（无论是否有开源社区工作经验，还是没有）在[1]发表您的观点和看法。 1. 请在[1]的Issue区留言 2. 中文和英语都行 3. 记得遵守开源社区文化，简单一句话就是“be nice to others，对人友善” 将来，大家的观点可以汇总成一篇博客；其中一些大多数人支持的观点也可以作为社区治理的一部分。谢谢 [1] https://gitee.com/openeuler/community/issues/I1B0B4 -- Regards Fred Li (李永乐) _______________________________________________ Isulad mailing list -- isulad(a)openeuler.org To unsubscribe send an email to isulad-leave(a)openeuler.org

2 1