March 2020 - Dev - mailweb.openeuler.org

Re: Welcome to the "Dev" mailing list
by axj 29 Mar '20

29 Mar '20

At 2020-03-29 16:42:01, dev-request(a)openeuler.org wrote: >Welcome to the "Dev" mailing list! > >To post to this list, send your email to: > > dev(a)openeuler.org > >You can unsubscribe or make adjustments to your options via email by >sending a message to: > > dev-request(a)openeuler.org > >with the word 'help' in the subject or body (don't include the >quotes), and you will get back a message with instructions. You will >need your password to change your options, but for security purposes, >this password is not included here. If you have forgotten your >password you will need to reset it via the web UI.

1 0

add to the list
by hxp 29 Mar '20

29 Mar '20

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

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

17 Mar '20

2 1

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

[Discusion] How can I become a member of Technical Committee in openEuler
by Fred Li 07 Mar '20

07 Mar '20

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 (李永乐)

1 0