- Tc - mailweb.openeuler.org

Last weekly meeting before Chinese New Year 2020
by Liyongle (Fred) 20 Jan '20

20 Jan '20

Hi all, Just to remind that we will have weekly meeting tomorrow, and will skip the next one due to Chinese New Year holiday. If you have any requirements, please reply the emails to community(a)openeuler.org<mailto:community@openeuler.org>. Please find minutes of meeting at[1] and review your actions. · 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<https://gitee.com/openeuler/community/blob/master/meeting_records/community…> in advance. The channel https://webchat.freenode.net/#openeuler-meeting is used. [1] http://meetings.openeuler.org/openeuler-meeting/2020/community/2020-01-14-0… Fred 李永乐

1 0

[Test] Test whether reply to lists goes well
by TommyLike Hu 16 Jan '20

16 Jan '20

Hey guys: Now, all of our mail lists' dmarc mitigation policy has been upgraded into "only when sender's DMARC equal to p = quarantine or p = reject", that means now we would not change email's content (Sen from Someone via Tc) at most of the cases. and the behaviour of Reply to would work as expected. Sorry for inconvenience.

1 0

[all] We should provider more concrete spec files for projects
by Liyongle (Fred) 16 Jan '20

16 Jan '20

Hi all, Please read [1] to get the request that all the PR should detail the changes so that users/developers can understand the context. [1] https://gitee.com/open_euler/dashboard/issues?sort=updated_at%20desc&id=I18… Fred 李永乐

1 0

[proposal] The open all repositories
by Edward Lee 15 Jan '20

15 Jan '20

hi all and tc members Today we discussed the private repositories management on community weekly-meeting. please refer to the log[1] we already get agreement on this meet that to open all other private repositories AQAP, I open this mail thread to get approval from the tc team. here are several reasons that should open them: 1. The governance encourage to open all, as the initial partner of this community, they should be open. 2. The privilege with public repositories and private repositories is quick different, that will make much efforts on managing them. other more, I would propose to not accept private repository any more. please review it, any comments are welcome. thanks. [1] http://meetings.openeuler.org/openeuler-meeting/2020/community/2020-01-14-0…

3 5

[Community]Reminding for weekly meeting of openEuler Community team
by Liyongle (Fred) 13 Jan '20

13 Jan '20

Hi all, This is a reminder for this week’s meeting. And please find last meeting minutes here http://meetings.openeuler.org/openeuler-meeting/2020/community/2020-01-07-0…. Weekly meeting · 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<https://gitee.com/openeuler/community/blob/master/meeting_records/community…> in advance. The channel https://webchat.freenode.net/#openeuler-meeting is used. · Document for meetings If there are some documents for the meeting, please cp ./meeting_records/template_meetig ./meeting_records/yyyy-mm-dd-meeting and put the documents there so that attendees can find them. Fred 李永乐

2 1

[discu] 定义会议时间？
by Huxinwei 11 Jan '20

11 Jan '20

各位： TC可以用定期电话短会的形式快速讨论闭环些事情。大家看下一般什么时候方便？ Regards Xinwei

3 2

答复: [Infra] Re: 答复: openEuler的代码仓是否要参考fedora的方式在git上放sha512、tar包放在其他地方
by Xiehong (Cynthia) 11 Jan '20

11 Jan '20

TC有刷新，重新发一下本邮件但是为什么这种邮件全部回复是，只能发给邮件发送人，infra(a)openeuler.xn--org?-ib5f81ch4kg7a956gz5lvk2bkj0absczs8akqzusau5g -----邮件原件----- 发件人: TommyLike Hu via Infra [mailto:infra@openeuler.org] 发送时间: 2020年1月10日 18:25 收件人: infra(a)openeuler.org 主题: [Infra] Re: 答复: openEuler的代码仓是否要参考fedora的方式在git上放sha512、tar包放在其他地方从目前接触到的开发流程来看，个人认为如果把tar包从代码仓库剥离，可以预见的好处是: 1. 提升开发的效率(git clone/push/pull) 2. 减少出错的概率(网络问题, gitee限制，脚本问题) 3. 提升OBS集成的速率(tar包部署在OBS内网中)。 PS: 如果能把当前2段同步的流程(gitee=>obs cache, obs cache-> obs source) 压缩成一步就更好了。 On Fri, Jan 10, 2020 at 4:07 PM Edward Lee via Infra <infra(a)openeuler.org> wrote: > > 对于基础设施来讲，两种方案都OK。 > > 如果使用sha512方式存放，对于基础设施来讲负载会更小，但是包管理人员的工作流程会更复杂。他需要先上传包到特定地方，然后再上传sha512 > 文件到gitee。 > 上传包到特定的地方如何来保证包内容的正确性需要考虑，比如是否包含病毒？是否有木马之类。 > > 总之没有详细设计之前，建议先按照现状进行。 > > On Thu, Jan 9, 2020 at 7:50 PM Xiehong (Cynthia) via Infra <infra(a)openeuler.org> wrote: >> >> 我以前用fedora的感觉是要下载个软件包好麻烦，比如用git。现在我们用码云的话，用浏览器很容易下载 >> >> >> >> 如果要把tar包不直接放在gitee上，那对开发者来说，git的命令都不能直接操作源码包，可能要操作两次，或者把git命令再封装一层，那是 >> 不是意味着我们要自己维护一套定制化的git工具，别人不能使用通用的git工具版本？ >> >> >> >> 发件人: Zhuyanpeng via Tc [mailto:tc@openeuler.org] >> 发送时间: 2020年1月9日 16:23 >> 收件人: infra(a)openeuler.org; tc(a)openeuler.org; Hexiaowen (Hex, EulerOS) >> <hexiaowen(a)huawei.com>; Hufeng (Solar, Euler) <solar.hu(a)huawei.com> >> 抄送: Zhangwenfeng (A) <wind.zhangwenfeng(a)huawei.com>; Zhangguiping >> <zhangguiping(a)huawei.com> >> 主题: [Tc] openEuler的代码仓是否要参考fedora的方式在git上放sha512、tar包放在其他地方 >> >> >> >> >> >> _______________________________________________ >> Infra mailing list -- infra(a)openeuler.org To unsubscribe send an >> email to infra-leave(a)openeuler.org > > > > -- > > Edward Lee > ----------------------------------------------------------- > Email: freesky-edward(a)gamil.com > Phone: 0086-18200191386 > Twitter: https://twitter.com/EdwardL0086 > Address: Chengdu City, Sichuan Privince, China > _______________________________________________ > Infra mailing list -- infra(a)openeuler.org To unsubscribe send an email > to infra-leave(a)openeuler.org _______________________________________________ Infra mailing list -- infra(a)openeuler.org To unsubscribe send an email to infra-leave(a)openeuler.org

1 0

新建文档SIG，希望通过审批
by Tanzhipeng 11 Jan '20

11 Jan '20

因用户参与文档建设诉求，需要建立文档SIG小组，构建、丰富现有的文档。已经在community社区提交PR，希望建立类似如下SIG。 [cid:image001.png@01D5C727.51A8DA10]

5 5

test
by Xiehong (Cynthia) 11 Jan '20

11 Jan '20

1 0

答复: 同意~答复: Re: 答复: 答复: 新建文档SIG，希望通过审批
by Xiehong (Cynthia) 10 Jan '20

10 Jan '20

多数人同意 @谭志鹏，麻烦你提交相关PR到https://gitee.com/openeuler/community -----邮件原件----- 发件人: Zhanghailiang 发送时间: 2020年1月10日 14:26 收件人: Guohanjun (Hanjun Guo) <guohanjun(a)huawei.com>; Xiehong (Cynthia) <xiehong(a)huawei.com>; Xiexiuqi <xiexiuqi(a)huawei.com>; Tanzhipeng <tanzhipeng.tan(a)huawei.com> 抄送: Liyongle (Fred) <liyongle(a)huawei.com> 主题: 同意~答复: [Tc] Re: 答复: 答复: 新建文档SIG，希望通过审批 -----邮件原件----- 发件人: Hanjun Guo via Tc [mailto:tc@openeuler.org] 发送时间: 2020年1月10日 14:10 收件人: Xiehong (Cynthia) <xiehong(a)huawei.com>; Xiexiuqi <xiexiuqi(a)huawei.com>; Tanzhipeng <tanzhipeng.tan(a)huawei.com> 抄送: tc(a)openeuler.org; Liyongle (Fred) <liyongle(a)huawei.com> 主题: [Tc] Re: 答复: 答复: 新建文档SIG，希望通过审批同意组建文档组，这个是对外体现的一个门面，有促于开发者参与 On 2020/1/10 13:59, Xiehong (Cynthia) via Tc wrote: > 其他TC委员是什么意见？ > > -----邮件原件----- > 发件人: Xiexiuqi > 发送时间: 2020年1月9日 22:26 > 收件人: Xiehong (Cynthia) <xiehong(a)huawei.com>; Tanzhipeng <tanzhipeng.tan(a)huawei.com> > 抄送: tc(a)openeuler.org > 主题: Re: [Tc] 答复: 新建文档SIG，希望通过审批 > > 我也统一建立专门的文档组。 > > 另外是不是也搞一个 openEuler 的 wiki，类似 openSuse，fedora 等： > > https://en.opensuse.org/Main_Page > https://zh.opensuse.org/%E9%A6%96%E9%A1%B5 > https://fedoraproject.org/wiki/Fedora_Project_Wiki > > 这里也有一些讨论： > https://gitee.com/openeuler/community-issue/issues/I17NN3 > > On 2020/1/9 20:33, Xiehong (Cynthia) via Tc wrote: >> 我个人同意建议组 >> >> >> >> 这个邮件列表建议换一个文档组专用的 >> >> IRC频道也建议换一个 >> >> 首页这里要换成一个专门的doc组吧。 >> >> website仓上也有sig的定义，PR的时候一起修改一下 >> >> >> >> >> >> *发件人:*Tanzhipeng via Tc [mailto:tc@openeuler.org] >> *发送时间:*2020年1月9日20:00 >> *收件人:*tc@openeuler.org >> *主题:*[Tc] 新建文档SIG，希望通过审批 >> >> >> >> 因用户参与文档建设诉求，需要建立文档SIG小组，构建、丰富现有的文档。 >> >> 已经在community社区提交PR，希望建立类似如下SIG。 >> >> >> _______________________________________________ >> Tc mailing list -- tc(a)openeuler.org >> To unsubscribe send an email to tc-leave(a)openeuler.org >> > > _______________________________________________ > Tc mailing list -- tc(a)openeuler.org > To unsubscribe send an email to tc-leave(a)openeuler.org > _______________________________________________ Tc mailing list -- tc(a)openeuler.org To unsubscribe send an email to tc-leave(a)openeuler.org

1 0

2024

2023

2022

2021

2020

2019

Tc