- Community - mailweb.openeuler.org

Re: [Tc] [Infrastructure] Regarding open OBS, what does infrastructure need prepare
by Liyongle (Fred) 04 Feb '20

04 Feb '20

Hi Tommylike, First of all, I found infra(a)openeuler.org and community(a)openeuler.org are missed in your previous email. I am wondering if it is a maillist issue. Please find my comments inline. Fred 李永乐 -----Original Message----- From: TommyLike Hu [mailto:tommylikehu@gmail.com] Sent: Monday, February 3, 2020 10:31 To: Liyongle (Fred) <liyongle(a)huawei.com> Cc: tc(a)openeuler.org Subject: Re: [Tc] [Infrastructure] Regarding open OBS, what does infrastructure need prepare 补充以下: 0. 明确我们暴露OBS给用户，最主要的目的是啥？查看构建日志，调试单个package, 获取构建的rpm？ [Fred] debug the package and build RPM. 1. 文档，包括OBS系统的介绍，当前我们的开发流程，是怎么使用OBS系统的，如果需要调试单个package怎么操作等。 [Fred] agree. 2. 域名，确实需要。 [Fred] agree, and what is the progress of getting back openeuler.cn? 3. 关于OBS集群本身支持规模的规格，官方并没有明确说明，不过我们在部署的时候是参考build.opensuse.org网站的部署规格来的，具体说明[1]。按照opensuse的机器规格和包的总量来看。我们现有集群的规格短期内是够用的，同时我们现在新增了普罗米修斯的监控系统，在资源使用超过阈值的情况下会有告警。 4. OBS系统的组件都是通过脚本部署在虚拟机上的，本身不支持自动伸缩，需要在资源不足的情况下，手动扩展(扩容等) [Fred] 3&4, currently the solution is fine. How long will it take to add a new server? 5. 关于账户管理，OBS本身有类似于maintainer，reviewer bugowner的角色分类，可以在项目的meta中定义，不过我们目前的开发流程，所有的角色定义都在gitee中，obs本身没有开放这块角色分类，所以开放后，任何人可以在obs注册用户，fork 项目，然后只能在个人主页project下面进行调试。 [Fred] how to link the 2 users between OBS and gitee? Or is it necessary? [1]: https://openbuildservice.org/help/manuals/obs-admin-guide/obs.cha.installat… On Mon, Feb 3, 2020 at 9:13 AM Liyongle (Fred) via Tc <tc(a)openeuler.org> wrote: > > Hi Infrastructure team, > > From last weekly meeting[1] I took one action “fred_li get the schedule of open OBS”. > > The following needs to be analyzed and assessed: > 1. Volume. About how many engineers does it support? > 2. Elastic resource support or not: if access exceeds the criteria, will it restrict, or trigger elastic resource? > 3. account management: > 4. domain name or IP we will use. > 5. anything else we have got from uses(like OVS)? > > If infrastructure team can provide feedback by Feb 7th, that will be fantastic. > > [1] http://meetings.openeuler.org/openeuler-meeting/2020/infrastructure/2020-01… > > > Fred 李永乐 > > _______________________________________________ > Tc mailing list -- tc(a)openeuler.org > To unsubscribe send an email to tc-leave(a)openeuler.org

1 0

答复: 关于驱动开源到OpenEuler事宜
by Wangqindong 03 Feb '20

03 Feb '20

您好，当前我们有款驱动程序，想开源到OpenEuler系统，还请问下具体的流程和规范是什么？多谢。 ________________________________ [智能计算email签名图档] 王钦东华为IT硬件平台部-BMC软件开发部 E-mail: wangqindong(a)huawei.com<mailto:wangqindong@huawei.com> Tel: +86 18923898549 中国(China)-东莞(Dongguan)-松山湖高新技术产业开发区环湖路9号华为溪流背坡村 [B4-94-2-A119S] [Company_logo] ________________________________ 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

1 0

Re: openEuler Community Governance Weekly meeting
by Liyongle (Fred) 03 Feb '20

03 Feb '20

Hi all, Due to Chinese New Year holiday, the weekly meeting last week was skipped. This email is to remind you that this week’s meeting will be resumed. Please find actions from last meeting [1]. Talk to you tomorrow. Action items 1. Fred to ask TC to give an conclusion on when to stop adding new private repos. 2. Fred to send email to TC for help, either reply issues in time, or join IRC meeting. 3. Fred_Li and HelloWord to prepare a governance documents for SIG changes 4. Fred_Li to raise the issue of I18620 and I18LZM to highlight package management strategy is important to our community. 5. Fred_Li and HelloWord to ask release team to prepare releasing guidance. [1] http://meetings.openeuler.org/openeuler-meeting/2020/community/2020-01-21-0… Fred 李永乐 -----Original Appointment----- From: Liyongle (Fred) Sent: Monday, January 6, 2020 19:30 To: Liyongle (Fred); community(a)openeuler.org Cc: guodong.xu(a)linaro.org; Ganesh Raju Subject: openEuler Community Governance Weekly meeting When: Tuesday, February 4, 2020 10:00-11:00(UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi。 Where: IRC https://webchat.freenode.net/#openeuler-meeting 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. - Channels IRC will be used to have the weekly meeting. If you consider other meetings like zoom, please propose to mail list in advance. Channel https://webchat.freenode.net/#openeuler-meeting [1] https://gitee.com/openeuler/community/blob/master/meeting_records/README.md

1 0

[metrics][infrastructure] what are contributors in openEuler
by Fred Li 27 Jan '20

27 Jan '20

Hi all, We are preparing metrics and later statistics for the community operation. One of the topic is to identify what contributors are. If you would like, please leave your commens in [1]. [1] https://gitee.com/openeuler/community-issue/issues/I18PQL -- Regards Fred Li (李永乐)

1 0

Re: [discu] openEuler软件包接纳策略讨论
by Liyongle (Fred) 22 Jan '20

22 Jan '20

Thank you for your proposal, Xinwei. I cc’d community and infra groups in case they may be interested in this topic. Please find my comments inline. One cent. Fred 李永乐 From: Xiehong (Cynthia) via Tc [mailto:tc@openeuler.org] Sent: Saturday, January 11, 2020 17:27 To: Huxinwei <huxinwei(a)huawei.com> Cc: tc(a)openeuler.org Subject: [Tc] 答复: [discu] openEuler软件包接纳策略讨论 /approve ☺ 发件人: Huxinwei via Tc [mailto:tc@openeuler.org] 发送时间: 2020年1月11日 15:00 收件人: tc(a)openeuler.org<mailto:tc@openeuler.org> 主题: [Tc] [discu] openEuler软件包接纳策略讨论 Hi all: 起草了openEuler软件包策略，请大家在大纲和具体内容上发表意见。 openEuler软件包策略手册版本 · 2020-01-11 Initial Draft by Xinwei Hu 关于本文档范围本文档定义了openEuler软件包所需要遵从的策略要求。所以提交到openEuler的软件包需要满足本手册中定义的技术要求。作者与改进流程本文档由openEuler技术委员会（Technical Committee）起草和维护。本文档的最新版本总可以在 XXXXXX [URL] 上找到。所有对本文档的修改意见可以通过邮件列表 XXXXX 反馈和讨论。 [Fred] /s/XXXXX/tc(a)openeuler.org [Fred] 是否需要分两类，ISO内的，以及extra的软件包，分别有不同的要求，比如质量要求不完全一样。目标 openEuler是一个致力于创建开放操作系统的合作组织。我们希望openEuler l 尽可能集成多的软件组件 l 鼓励所有人使用openEuler，并可以在openEuler上开发软件 l 使能任何人，在不违反license，进出口管制或其他相关法律的前提下，可以容易的制作安装介质 openEuler遵从 Open Source Definition<https://opensource.org/docs/osd> ，满足这一定义的软件，被openEuler社区认同为开源软件。 [Fred] 感觉这里是想说，openEuler只接纳开源软件的意思，开源软件需要符合OSD。如果是这个意思，可以直接说明。 openEuler接纳要求版权要求每一个软件包需要license，这个license需要是openEuler社区已知并认同的开源或者商用license。如果是全新的license，需要由openEuler的法务人员审视并接纳成为社区认同的 license。 [Fred] 是否需要列出已经认可的License清单？商用License是否不应该包含？软件包管理要求所有被openEuler接纳的软件包，需要满足openEuler的包管理系统技术要求。基础软件要求基础软件是构成openEuler的核心开源软件，也被认为是 openEuler的一部分。基础软件是自包含的。 openEuler社区中的任何人都可以共享、修改或者再分发基础软件。为此，技术上要求： · 基础软件的构建与运行不允许依赖非基础软件 · 必须满足openEuler社区的质量要求。因为质量问题而无法被支持的软件不允许成为基础软件。 [Fred] 建议质量要求也需要有个说明。共享软件要求共享软件也必须是开源软件。但共享软件的构建或者运行可以依赖openEuler基础软件之外的软件组件。为此，技术上要求： · 必须满足openEuler社区的质量要求。因为质量问题而无法被支持的软件不允许成为基础软件。受限软件要求所有非开源软件，或者有其他法律合规性限制的软件，被看做受限软件。技术上要求： · 必须满足openEuler社区的质量要求。因为质量问题而无法被支持的软件不允许成为基础软件。 [Fred] 不推荐非开源软件被openEuler社区直接接纳。这类软件可以在自己的供应商处或者第三方平台提供可适配openEuler的软件包。参考 ISO openEuler社区会定期发布参考ISO，来验证安装介质的制作流程。原则上，openEuler ISO会包含所有基础软件包。共享软件与受限软件，在openEuler获得重分发授权，并且和XXX不冲突的前提下，也会作为独立的参考ISO。

5 6

openEuler 1.0 Beta is released today
by Fred Li 22 Jan '20

22 Jan '20

Hi all, It is glad to inform you that openEuler 1.0 Beta is released. You can find new iso [1]. The home page is also updated by removing the first banner of that openEuler is open. [2] The mail list page [3] is also updated and the links will open a new window which is more user friendly. Sorry for that the document [4] is only in Chinese and the English version will be ready after Chinese New Year. [1] https://openeuler.org/zh/download.html [2] https://openeuler.org/ [3] https://openeuler.org/zh/community/mails.html [4] https://openeuler.org/zh/docs/Releasenotes/release_notes.html -- Regards Fred Li (李永乐)

1 0

【意见收集】关于sig变更流程的意见收集
by Yang Li 21 Jan '20

21 Jan '20

1 0

Canceled: openEuler Community Governance Weekly meeting
by Liyongle (Fred) 21 Jan '20

21 Jan '20

Due to Chinese New Year, this week meeting is skipped. See you on Feb 4th. 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. - Channels IRC will be used to have the weekly meeting. If you consider other meetings like zoom, please propose to mail list in advance. Channel https://webchat.freenode.net/#openeuler-meeting [1] https://gitee.com/openeuler/community/blob/master/meeting_records/README.md

2 1

Please find minutes of meeting on Jan 21
by Liyongle (Fred) 21 Jan '20

21 Jan '20

Hi all, Thanks for your contribution to Community team. Please find the minutes of meeting [1]. Action items Fred to ask TC to give an conclusion on when to stop adding new private repos. Fred to send email to TC for help, either reply issues in time, or join IRC meeting. Fred_Li and HelloWord to prepare a governance documents for SIG changes Fred_Li to raise the issue of I18620 and I18LZM to highlight package management strategy is important to our community. Fred_Li and HelloWord to ask release team to prepare releasing guidance. Due to Chinese New Year, the next week meeting (Jan 28th) will be skipped. [1] http://meetings.openeuler.org/openeuler-meeting/2020/community/2020-01-21-0… Fred 李永乐

1 0

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

20 Jan '20

Sorry for late notice, can we have this meeting one hour earlier for this week only? 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. - Channels IRC will be used to have the weekly meeting. If you consider other meetings like zoom, please propose to mail list in advance. Channel https://webchat.freenode.net/#openeuler-meeting [1] https://gitee.com/openeuler/community/blob/master/meeting_records/README.md

1 0