- Infra - mailweb.openeuler.org

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

Re: [Tc] 会议纪要 //【Meeting Notice】Unscheduled openEuler TC meeting Time: 2020-03-11 10:00-12:00
by Fred Li 11 Mar '20

11 Mar '20

cc infra(a)openeuler.org Welcome Mate-desktop SIG! OBS is being opened and if you have any request or doubts, don't hesitate to contact infra(a)openeuler.org. Thanks On Wed, Mar 11, 2020 at 12:46 PM Hanjun Guo via Tc <tc(a)openeuler.org> wrote: > > 1. Mate-desktop SIG建立（遗留问题责任人 - 普华） > - 在PR中说清楚mate-desktop的作用，使用范围，以及涉及哪些软件包，方便review时从兼容性，作用等技术因素决定是否接受为新的SIG； > - 签署CLA； > - 需要新建立邮件列表； > - OBS系统构建对接，与胡胜（hu.husheng(a)huawei.xn--com);-bd0no1q > > 2. 建立openEuler测试系统（遗留问题责任人 - 吴峰光） > - 建立一个测试能力as service的系统，构建openEuler影响力，提议OK，建议创建新SIG，提PR进行review； > > 3. 会议时间变更，下周会议取消。下次会议3月25号（主持人张海亮），之后保持双周例会不变； > _______________________________________________ > Tc mailing list -- tc(a)openeuler.org > To unsubscribe send an email to tc-leave(a)openeuler.org -- Regards Fred Li (李永乐)

1 0

weekly meeting reminder
by Edward Lee 10 Mar '20

10 Mar '20

hi, all kindly reminder the today's infra meeting schedule(today): next meeting time: Tuesday 17:00-18:00(CST) channel: #openeuler-meeting please feel free to reply this email to add your topic. thanks -- freesky-edward

2 2

Is it possible to add a label for issues to indication that more information is required?
by Fred Li 09 Mar '20

09 Mar '20

Hi Infrastructure team, Sometimes we got some issues whose information is too brief to understand. I am wondering whether it is necessary to add one label to indication that more information is required. If yes, it helps the developers to skip issues whose information is far from enough. If no, it is also reasonable, as if the issue author doesn't care so much, the issue can be handled later. What do you think? And if yes, is it feasible to customize or add new labels for issues? -- Regards Fred Li (李永乐)

1 0

[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

openEuler Blog is launched
by Fred Li 06 Mar '20

06 Mar '20

Hi all, openEuler blog is launched and you all are welcome to post your blogs. From openeuler.org you can find the menu "BLOG", or visit blog.openeuler.org directly. Thanks to the following guys for contribution: @ZhengyuhangHans @freesky-edward @shredstar @blueskycs2c @Fred_Li Best Regards -- Regards Fred Li (李永乐)

1 0

[Blog]Please help to review the final step to launch blog.openeuler.org
by Liyongle (Fred) 05 Mar '20

05 Mar '20

Hi all, As you may have noticed that openEuler blog [1] has been in trial phase for 2 weeks, and now we are thinking of launch it formally. Now there are still several pending tasks to finish, and I would like to ask you to take a final look on this. 1. Guidance to post a blog [2] is pending for reviewing 2. 3 changes [3] are pending for reviewing 3. Legal notice [4] is to be added and @zhengyuhanghans is working on it. 4. To add the link to openEuler portal [5] will be the final step. Please leave your comments on the PR or Issues and we will finish the final steps. Thank you in advance. [1] blog.openeuler.org [2] https://gitee.com/openeuler/blog/pulls/11 [3] https://gitee.com/openeuler/blog/pulls/11 [4] https://gitee.com/openeuler/blog/issues/I1AOFP?from=project-issue [5] https://gitee.com/openeuler/website/pulls/64 Fred 李永乐

1 0

Regarding to improvement to openeuler's wiki and issues handling on gitee
by Huxinwei 28 Feb '20

28 Feb '20

Infra team: On behave of TC, I’m proposing following changes to openEuler infrastructure for your consideration. 1. Regarding to Wiki Background: We think Wiki is a good way to consolidate and present knowledge systematically. openEuler already has its own document site (https://openeuler.org/zh/docs) we think it could be further improved. a) The namespace of pages should be flattened. For example, https://openeuler.org/zh/docs/Administration/简介.html , the name of page implies to be an introduction to system administration. But in fact, it’s an introduction to system only. We propose to add directories for each domain. b) Currently documents are divided into different SIG, we think it’s important to extend it for multiple SIG. For example, if we introduce oVirt into openEuler, the document of oVirt should be part of the https://openeuler.org/zh/docs/Virtualization, not it’s own. c) It’s very different to use cross reference now. We think it is an important feature to have. For example, https://openeuler.org/zh/docs/Administration/设置语言环境.html should refer to systemd. It’ difficult or even impossible to do so now. 2. Regarding to issues handling Background: There’re difficulties during day-to-day work on openEuler community. Especially, when issues are reported. We think it needs to be further improved. a) When an issue is reported, we think it’s very helpful to have it assigned to a default triage. The developers don’t know each other, and even they know each other, they can not match the ID with real people. The best way now is to assigned to a default triage based on the components or sub-module. b) There’re too many messages on the web interface. Developers are easily overwhelmed. We suggest to have a default mail notification for all un-handled or un-closed issue to assigned developers. If there’re existing mechanism we can leverage, please advise too. Looking forward to your feedback and suggestions. Shinwell Technical Committee openEuler Community

2 2

更新通知 infra@openeuler.org
by openeuler.org 27 Feb '20

27 Feb '20

1 0

[Recap] Last weekly meeting
by Edward Lee 24 Feb '20

24 Feb '20

hi, all This is an email for the last week meeting recap: 1. *Add zhongjun2 to maintainer group* get approved after vote 2. *open discussion* no special action left *for more detailed information, please refer to * http://meetings.openeuler.org/openeuler-meeting/2020/infrastructure/2020-02… and now the next weekly meeting is open, please feel free to reply your topic proposal. next meeting time: Tuesday 17:00-18:00(CST) channel: #openeuler-meeting thanks -- freesky-edward

1 0