Now, As you can see, whatever issue is bug or requirement, the tempalte is the same.This is not inaccruacies.
if issue is a requirement, the requirement scenario and value is very important.
if issue is a bug, this template is incomplete. the complete template is below, this template is provided by a member of sig-qa :
【标题描述】:能够简要描述问题发生的场景、做了什么操作,以及出现了什么问题。
【环境信息】:
**硬件信息**:
- 逻辑场景提供出问题的硬件信息
- 虚拟机场景提供虚拟机的XML文件或配置信息
**软件信息**
- OS版本及分支 (e.g. from /etc/os-release)
- 内核信息(e.g. `uname -a`)
- 发现问题的组件…
[View More]版本信息
*如果有特殊组网,请提供网络拓扑*
【问题复现步骤】
具体操作步骤
【预期结果】
描述预期结果,可以通过对比新老版本获取
【实际结果】
妙处出问题的结果
【附件信息】
比如系统的Message日志、组件日志、dump信息、图片等。
btw,the template is also switch when the issue is switched in drop-down list box. if the switchover cannot be performed due to the restriction of gitee, we can integrate two templates into one ,for example:
-----
以下是需求的模板,如果您的Issue是一个需求,请按照以下模板提供相关信息,**并把问题模板的内容删除**,谢谢
-----
【需求场景】:请简要需求的使用场景和相关规格
【需求价值】:请简要描述该需求的竞争力和实现价值
-----
以下是问题的模板,如果您的Issue是一个问题,请按照以下模板提供相关信息,**并把需求模板的内容删除**,谢谢
-----
【标题描述】:能够简要描述问题发生的场景、做了什么操作,以及出现了什么问题。
【环境信息】:
**硬件信息**:
- 逻辑场景提供出问题的硬件信息
- 虚拟机场景提供虚拟机的XML文件或配置信息
**软件信息**
- OS版本及分支 (e.g. from /etc/os-release)
- 内核信息(e.g. `uname -a`)
- 发现问题的组件版本信息
*如果有特殊组网,请提供网络拓扑*
【问题复现步骤】
具体操作步骤
【预期结果】
描述预期结果,可以通过对比新老版本获取
【实际结果】
妙处出问题的结果
【附件信息】
比如系统的Message日志、组件日志、dump信息、图片等。
rainbow1981(a)163.com
[View Less]
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 李永乐
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 李永乐
Hi there
Have you lost your ranks during the Recent google updates?
We can recover them back!
We will perform
- onpage seo work
- toxic links clean up
- ethical offpage seo work to boost your ranks up
- Monthly reports with guaranteed results
More info here
http://www.cheapseoagency.com/cheap-seo-packages/
If you have more than 1 website, we can give big bundle deals
Start gaining your spots back TODAY!
Regards
Mike
http://www.cheapseoagency.com/unsubscribe/
001 (516) 926-…
[View More]1772, 18 Richmond St, Albany, New York
[View Less]
Hi all,
If you are interested in managing new projects, or you are willing to create new projects in our community, you may be interested in the discussion [1]. Join to show your opinion.
You opinion matters.
[1] https://gitee.com/openeuler/community/issues/I17WWY?from=project-issue
Fred 李永乐
Hi TC members and Infrastructure team,
I posted a news to call for developers [1]. Please help to review it.
To clarify comments you may ask, there are 2 competitions related with openEuler in HDC.Cloud. One is [2] which focuses on openEuler itself, and the one I posted is focused on integration with other open source projects.
[1] https://gitee.com/openeuler/website/pulls/42
[2] https://openeuler.org/zh/events/2020hdc.html
Regards
Fred 李永乐
Hi all,
At this early stage, many developers are coming to see the projects. To make visitors easier to understand the project, it is proposed to improve the following:
- README
It is better to provide both English[1] and Chinese[2].
- Meeting schedule
Please provide meeting schedule and add the information to your readme. The example is [3].
- Contact
Mail and IRC.
- Team members
Please be sure to including Maintainers, committers and contributors. This is a way to respect every …
[View More]contributor, and let new contributors to understand who to talk.
- How to contribute
Different projects have their own way to contribute. Some projects (like community) are mainly documents, some are codes and some are buildings. Please provide the contribution guidance for your own projects.
- Other useful information
Your advice and good practice are valuable.
[1] https://gitee.com/openeuler/community/blob/master/README.md
[2] https://gitee.com/openeuler/community/blob/master/README_cn.md
[3] https://gitee.com/openeuler/community/blob/master/README.md#meeting
Fred 李永乐
[View Less]
Hi members of openEuler community team,
Firstly I would clarify that this email is supposed for the project community [1], not the whole openEuler community.
This email is to propose the time for weekly meeting with the contributors for the project, and anyone who are interested in the project.
Which one would you select below?
1. 10:00-11:00 am, Tuesday, Beijing Time; 2:00-3:00 am, Tuesday, UTC.
2. 17:00-18:00 am, Thursday, Beijing Time; 09:00-10:00 am, Tuesday, UTC.
The topics on this …
[View More]meeting will be:
1. community governance. As we are still in preparation phase, the maturity of the governance is far from completion.
2. proposed helps to the rest of teams, including but not limited to the management procedure between technical committee, SIGs and others.
3. actions for next week.
Where to store the meeting documents?
I would propose to create a new folder meeting_records under [1], and for each meeting I will create a new folder like [yyyy-mm-dd-weekly-meeting].
Any comments or suggestions are welcome.
[1] https://gitee.com/openeuler/community
Fred 李永乐
[View Less]