- Tc - mailweb.openeuler.org

Re: Related backlinks please
by World.Wide.Traffic＠gmail.com 24 Jan '20

24 Jan '20

hello Here it is http://str8-creative.io/product/related-backlinks/ http://www.str8-creative.io/unsubscribe/

1 0

Re: How to remove a site from top 10 for important keywords
by NegativeSEOthatWorks＠gmail.com 22 Jan '20

22 Jan '20

Negative SEO with Satisfaction Guaranteed http://www.blackhat.to

1 0

[discu] openEuler软件包接纳策略讨论
by Huxinwei 22 Jan '20

22 Jan '20

Hi all: 起草了openEuler软件包策略，请大家在大纲和具体内容上发表意见。 openEuler软件包策略手册版本 · 2020-01-11 Initial Draft by Xinwei Hu 关于本文档范围本文档定义了openEuler软件包所需要遵从的策略要求。所以提交到openEuler的软件包需要满足本手册中定义的技术要求。作者与改进流程本文档由openEuler技术委员会（Technical Committee）起草和维护。本文档的最新版本总可以在 XXXXXX [URL] 上找到。所有对本文档的修改意见可以通过邮件列表 XXXXX 反馈和讨论。目标 openEuler是一个致力于创建开放操作系统的合作组织。我们希望openEuler l 尽可能集成多的软件组件 l 鼓励所有人使用openEuler，并可以在openEuler上开发软件 l 使能任何人，在不违反license，进出口管制或其他相关法律的前提下，可以容易的制作安装介质 openEuler遵从 Open Source Definition<https://opensource.org/docs/osd> ，满足这一定义的软件，被openEuler社区认同为开源软件。 openEuler接纳要求版权要求每一个软件包需要license，这个license需要是openEuler社区已知并认同的开源或者商用license。如果是全新的license，需要由openEuler的法务人员审视并接纳成为社区认同的 license。软件包管理要求所有被openEuler接纳的软件包，需要满足openEuler的包管理系统技术要求。基础软件要求基础软件是构成openEuler的核心开源软件，也被认为是 openEuler的一部分。基础软件是自包含的。 openEuler社区中的任何人都可以共享、修改或者再分发基础软件。为此，技术上要求： · 基础软件的构建与运行不允许依赖非基础软件 · 必须满足openEuler社区的质量要求。因为质量问题而无法被支持的软件不允许成为基础软件。共享软件要求共享软件也必须是开源软件。但共享软件的构建或者运行可以依赖openEuler基础软件之外的软件组件。为此，技术上要求： · 必须满足openEuler社区的质量要求。因为质量问题而无法被支持的软件不允许成为基础软件。受限软件要求所有非开源软件，或者有其他法律合规性限制的软件，被看做受限软件。技术上要求： · 必须满足openEuler社区的质量要求。因为质量问题而无法被支持的软件不允许成为基础软件。参考 ISO openEuler社区会定期发布参考ISO，来验证安装介质的制作流程。原则上，openEuler ISO会包含所有基础软件包。共享软件与受限软件，在openEuler获得重分发授权，并且和XXX不冲突的前提下，也会作为独立的参考ISO。

6 7

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

[all]It is urgent to prepare software packages selection strategy
by Liyongle (Fred) 21 Jan '20

21 Jan '20

Hi TC member, QA, Infrastructure team, Docs team, I sent this email because of issue[2]. We container team still provide docker as a choice~ Maybe we need a disscuss.Should we put it into our base iso or some enhancement repo. And considering the discussion in [1], I think it is urgent to open the selection strategy of software packages. 1. it is the criteria for the software to be allowed to openEuler 2. it the criteria for the software packages to be inside the base Then the infrastructure team need implement it. The QA team need separate the test cases according to this. The docs team need prepare documentation according to the same. Please leave your comments in [1], and contributors are needed. [1] https://gitee.com/openeuler/community/issues/I18620?from=project-issue [2] https://gitee.com/openeuler/community-issue/issues/I18LZM?from=project-issue Fred 李永乐

1 0

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

21 Jan '20

1 0

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

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