January 2020 - Tc - mailweb.openeuler.org

28 Jan '20

Финансы для руководителей и нефинансовых менеджеров Пройдет: 31 января. Программа посвящена вопросам: - какие показатели измерять, почему они важны, о чем говорят, где их искать; - какие отчеты требовать от финансовых служб; - как создать управленческий учет в компании; - как организовать бюджетное управление в компании; - как рассчитать бюджеты компании, какова должна быть структура бюджетов; - как распределить зоны финансовой ответственности за бюджетные показатели. Повестка дня: Модуль 1. Главные вопросы управления финансами - Как измеряется финансовый успех компании - Какие 3 стратегии позволят увеличить Прибыль - Как рассчитать стоимость бизнеса - Стандарты операционной эффективности Модуль 2. Прогнозирование результатов деятельности компании за 10 минут - Как прогнозировать продажи. Какова будет потребность в финансировании объема продаж - Как прогнозировать расходы - Какой оборотный капитал потребуется - Как спланировать денежный поток, потребность во внешнем финансировании Модуль 3. О чем рассказывают финансовые отчеты: какие показатели нельзя упускать из виду - Почему важны все 3 отчета. Какие проблемы могут быть, если нет Баланса? - Отчет о прибылях и убытках: структура отчета, основные показатели - Операционные затраты, затраты на персонал - Отчет о движении денежных средств: структура отчета, основные показатели Модуль 4. Управленческий учет для руководителя - Какова основная цель управленческого учета - Как совместить бухгалтерский и управленческий учет - Какая информация должна быть в управленческом учете - Учетная политика: что должна содержать. Модуль 5. Организация бюджетного управления. Как управлять с помощью бюджетов - Как быстро привести дела в порядок в финансах - Что нам хочет сказать прибыль? - Что делают выдающиеся финансисты иначе: Практика лучших финансистов - KPI и нормативы подразделений - Что выбрать статичный бюджет или скользящее планирование? Модуль 6. Техники формирования бюджетов компании подразделений - Бюджет доходов и расходов (прибылей и убытков) по статьям и по элементам - Бюджет движения денежных средств, Прогнозный баланс, Как они формируются Узнать подробнее >>> http://ukrmoney.in.ua/training/150/finansi-dlya-rukovoditeley-i-nefinansovi… Отказ от подписки. List-Unsubscribe или пожаловаться на Spam

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

Buy Instagram Followers
by Real.Followers.IG＠gmail.com 27 Jan '20

27 Jan '20

Driven Social Marketing Real and permanent Followers http://www.myinstabuzz.co/buy-instagram-followers/ http://www.myinstabuzz.co/unsubscribe/ Västerlånggatan 56, 111 29 Sweden

1 0

Re: my keywords went down
by Lida Goers 26 Jan '20

26 Jan '20

Hi again here is the service I was telling you about http://www.str8-creative.io/product/ranks-recovery-seo-plan/ thanks and regards Lida Goers 2018-03-12, tr, 19:37 tc <tc(a)openeuler.org> ra�e: Ok,# send me the link, I need the ranks to be# fixed urgantly.

1 0

Increase your website DA on next Moz update
by Improve.DA.of.your.website＠gmail.com 25 Jan '20

25 Jan '20

Here is how http://www.str8-creative.io/product/moz-da-seo-plan/ Get: 2000 high TF links 2500 EDU and Gov links 10000 high Moz DA diversified links Your Domain Authority will get a boost on the next Moz update Regards Str8 Creative Unsubscribe option is available on the footer of our website

1 0

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

[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

Project Community team weekly meeting topics collection
by Liyongle (Fred) 10 Jan '20

10 Jan '20

Hi members, The project community team next weekly meeting will be held on Tuesday next week. As we are early stage, I would send email to remind you of providing requirements to governance. Don’t hesitate to reply emails to provide any requirements or proposals to community(a)openeuler.org<mailto:community@openeuler.org>. Ref: https://gitee.com/openeuler/community/tree/master/meeting_records Fred 李永乐

1 0

openEuler的代码仓是否要参考fedora的方式在git上放sha512、tar包放在其他地方
by Zhuyanpeng 09 Jan '20

09 Jan '20

1 0

A draft community governance
by Liyongle (Fred) 09 Jan '20

09 Jan '20

Hi all, I found some SIGs are adding committers recently. And some new SIGs with new projects(repos) are being created. Even it is in very early stage of the community, I think we'd better to have a governance to make such changes serious. If you have comments, please leave it at[1]. Your opinion matters. [1] https://gitee.com/open_euler/dashboard/issues?id=I1838P Fred 李永乐

2 1

2024

2023

2022

2021

2020

2019

Tc January 2020