- Tc - mailweb.openeuler.org

Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00
by Zhanghailiang 23 Mar '20

23 Mar '20

Hi All, This is the topics we collected for 3.25 TC meeting: - Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 -> zhangpan - Add RaspberryPi SIG: https://gitee.com/openeuler/community/pulls/259 -->方亚芬 - 1. introduce some development tools packages in openEuler.->myEuler (熊伟） 2. apply to do some clean job in community. refine the organization of the web page. 3. set program language for each package repo https://gitee.com/openeuler/community/issues/I1C1PU - introduce some big data and ai develop runtime/framework in openEuler -> zhengxian Please let me know if you would like to add a topic. From: Zhanghailiang via Tc [mailto:tc@openeuler.org] Sent: Wednesday, March 11, 2020 2:56 PM To: tc(a)openeuler.org Cc: zhangpan (L) <zhangpan26(a)huawei.com> Subject: [Tc] TC Call for agenda 2020-03-25 RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Hi Please, send any topic that you are interested in covering. We have already one topic for this call already: 1) Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 Thanks, Hailiang From: Meeting Book via Tc [mailto:tc@openeuler.org] Sent: Wednesday, March 11, 2020 2:37 PM To: tc(a)openeuler.org<mailto:tc@openeuler.org> Subject: [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Topic openEuler TC meeting Time 2020-03-25 10:00-12:00((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/627988019> Meeting ID 627 988 019 Convener 张海亮 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载ZOOM客户端入会。 Please click the conference link and download the ZOOM to join the conference. Huawei and all its affiliates respect your privacy and are committed to protecting it. When inviting you to join a video meeting, we will collect and use your personal information, including your name, device type, IP address, network type, microphone, speaker, camera, joining time, and leaving time. For more information about Huawei’s privacy policy, visit https://www.huawei.com/en/privacy-policy

2 2

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

apply one topic : need to set program language for each package repo
by myeuler 18 Mar '20

18 Mar '20

Please check the issue : https://gitee.com/openeuler/community/issues/I1C1PU I think this is a good idea that can help the repo more clear.

1 0

【Apply for topic in TC】A-Tune status and progress
by Shanshishi 17 Mar '20

17 Mar '20

Purpose: introduce A-Tune status and current development progress

2 2

[新SIG提案]，申请添加bounds_checking_function SIG。望批准
by zhaozhijian (A) 17 Mar '20

17 Mar '20

您好， [新SIG提案]，申请添加bounds_checking_function SIG，用于贡献带边界检查函数的源代码。望批准合入。 PR链接：https://gitee.com/openeuler/community/pulls/274 赵志健

1 0

apply 2 topics in 3.25 TC meeting
by myeuler 17 Mar '20

17 Mar '20

1. introduce some development tools packages in openEuler. 2. apply to do some clean job in community. refine the organization of the web page.

3 3

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

17 Mar '20

2 1

TC Call for agenda 2020-03-25 RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00
by Zhanghailiang 16 Mar '20

16 Mar '20

Hi Please, send any topic that you are interested in covering. We have already one topic for this call already: 1) Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 Thanks, Hailiang From: Meeting Book via Tc [mailto:tc@openeuler.org] Sent: Wednesday, March 11, 2020 2:37 PM To: tc(a)openeuler.org Subject: [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Topic openEuler TC meeting Time 2020-03-25 10:00-12:00((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/627988019> Meeting ID 627 988 019 Convener 张海亮 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载ZOOM客户端入会。 Please click the conference link and download the ZOOM to join the conference. Huawei and all its affiliates respect your privacy and are committed to protecting it. When inviting you to join a video meeting, we will collect and use your personal information, including your name, device type, IP address, network type, microphone, speaker, camera, joining time, and leaving time. For more information about Huawei’s privacy policy, visit https://www.huawei.com/en/privacy-policy

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