当前时区为 UTC + 8 小时



发表新帖 回复这个主题  [ 1 篇帖子 ] 
作者 内容
1 楼 
 文章标题 : QA community structuring and needs - QA社区的构建和需求
帖子发表于 : 2013-05-09 9:56 

注册: 2013-05-09 9:11
帖子: 9
系统: UbuntuKylin 13.04
送出感谢: 0 次
接收感谢: 0 次
*温馨提示:本人英文能力有限,翻译不当之处还望大家跟帖指正,共同学习、进步!*

https://blueprints.launchpad.net/ubuntu ... -community
QA community structuring and needs
QA社区的构建和需求

Discussing communication strategies, interactions with sister communities and team organization, recruitment and recognition
讨论沟通策略,与姊妹社区的互动和团队的组织、招新和识别。

AGENDA:
议程:

Communication 沟通
How can we improve our communication?
如何改善我们的沟通?
How well are the weekly QA meetings working?
每周的QA会议如何运作?
Do we need other avenues (non-realtime?) to communicate?
我们是否需要其他途径(非实时)沟通呢?

Collaboration 协作
Can we collaborate on testcase management?
我们可以在测试用例管理上进行协作吗?
Can we collaborate on common application testing?
我们可以在应用程序测试上进行协作吗?
Can we collaborate on common package testing?
我们可以在常见的包测试上进行协作吗?

installers, x, drivers, etc 安装,x,驱动程序等
Can we co-host the idea of "testing days"?
我们可以共同主持“testing days”吗?

Other ideas 其他想法
Other areas for colloboration 其他地区的协作
App Developers 应用开发者
Server/Dev Ops 服务器/设备驱动程序运维
Upstream developers 上游开发者
Other Platforms 其他平台讨论区
Team Organization 团队组织
Are we sharing resources for recruiting and retaining folks?
我们是否共享招新和留人的资源?
Example, many people use multiple flavors such as ubuntu and lubuntu, xubuntu and kubuntu, etc.
例如,许多人使用多个特色版本,如ubuntu和lubuntu,xubuntu和kubuntu等。
How are we recognizing our contributors?
我们怎样认识我们的贡献者?
Release notes 发行说明/版本注释
SWAG
Early access to new "stuff"; code, packages, hardware
新的“原料”预览:代码,包,硬件
Resources 资源
Clasroom and Instruction Clasroom和指令
Is there a need/desire for more "how-to" sessions?
是否有添加更多“how-to”会话的需求/要求?
Is there a need/desire for mentoring?
是否有指导的需求/要求?
Hardware 硬件
Are we getting good coverage?
我们是否得到了好的覆盖?
Other Needs / Ideas?
其他需求/想法

Notes from the session:
会议记录
* Communication * 沟通
How to improve communication, how well are weekly meetings working, are there other ways to do it?
如何改善沟通,怎样运作周会,有其他方式去做吗?
Currently we have the weekly meeting, which changed time during the past release, working better so far
目前我们有周会,它在过去的版本中改变了时间,目前运作良好。
QA mailing list also available
QA邮件列表也可用
Flavour teams, Localized ISO testing
特色团队,本地化ISO测试

In ISO testing is important to report results even if they are repeated, the more results the better- Is there a way to automatically submit results? Maybe talking to the ubiquity/alternate developers on how to do this would help (to be discussed on iso testing)
在ISO测试中报告测试结果是很重要的即使是重复报告,测试结果越多越好 - 是否有一个自动提交结果的方法?也许会说到ubiquity/alternate开发者关于怎样去做会有帮助(讨论iso测试)

Send a distilled summary of what was discussed/agreed on the weekly meeting to the ubuntu-qa mailing after the meeting itself.
会后自动发送一个在周会上什么被讨论/同意的精华总结到ubuntu-qa。

* Collaboration * 协作
- Having a community based hardware database to be able to compare results based on hardware components (Ubuntu Friendly currently covers entire systems)
- 有一个基于硬件数据库的社区可以基于硬件组件比较结果(Ubuntu友好化目前覆盖整个系统)
http://brainstorm.ubuntu.com/ide ... r-hardware-databasehttps://blueprints.launchpad.net ... ntuhardwaredatabase

- Maybe use the database to do targetted testing so if a fix is hardware related they can work together
- 也许可以使用数据库做合适的测试,所以如果一个修复跟硬件相关,他们可以一起工作。

- Ubuntu Friendly was done a cycle ago, but they didn't have the capacity to build a community around it, the site is there, the results tracker on launchpad. Maybe the community could own the site and the effort to take Ubuntu Friendly forward
- Ubuntu友好化已经完成一个周期,但他们没有能力建立一个关于他们的社区,结果追踪在launchpad上。也许社区可以有自己的网站并努力推动Ubuntu友好化。

- What does collaboration mean? There are QA teams on the flavours, they are doing some QA that we can try to reduce duplication
协作是什么意思?在特色系统有一个QA团队,他们为试着减少重复做一些质量保证。

There are three kinds of testing:1. Call for testing (something new has changed and we want to test it)2. Cadence of testing (make sure that we have people with read hw in the community testing every day)3. ISO testing (testing at milestones)
一共有三类测试:
1.要求测试(新的东西改变了,我们需要测试它)
2.规律测试(确保我们有人每天在社区测试中阅读hw)
3.ISO测试(里程碑的测试)

* Team Organisation * 团队组织

People who do calls for testing - People who do targetted testing (hardware, localisation)
做要求测试
- 做合适的测试(硬件,本地化)

People who use the ISO tracker - People who do targetted testing (hardware, localisation)
使用ISO追踪
- 做追踪测试(硬件,本地化)

People who do cadence testing - People who do targetted testing (hardware, localisation)Test developers(?)
终止测试
- 做追踪测试(硬件,本地化)

Running: ISO testing, checkbox tests
运行:ISO测试,复选框测试
Let's organise in a way that people do not get burnt out
让我们组织一个不会被烧坏的方式
Give feedback to the people doing testing about how much they contributed
反馈人们贡献了多少做测试。

- How do we recognise the contributors? Trophies,
我们如何认识贡献者?有威望的,

Sessions to add:- Calls for testing- QA Team Organisation
添加会话:
- 要求测试
- QA团队组织


页首
 用户资料  
 
显示帖子 :  排序  
发表新帖 回复这个主题  [ 1 篇帖子 ] 

当前时区为 UTC + 8 小时


在线用户

正在浏览此版面的用户:没有注册用户 和 2 位游客


不能 在这个版面发表主题
不能 在这个版面回复主题
不能 在这个版面编辑帖子
不能 在这个版面删除帖子
不能 在这个版面提交附件

前往 :  
本站点为公益性站点,用于推广开源自由软件,由 DiaHosting VPSBudgetVM VPS 提供服务。
我们认为:软件应可免费取得,软件工具在各种语言环境下皆可使用,且不会有任何功能上的差异;
人们应有定制和修改软件的自由,且方式不受限制,只要他们自认为合适。

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
简体中文语系由 王笑宇 翻译