QA in the Open
Tuesday 10:40 a.m.–11:25 a.m.
Target audience: Developer
One common misconception about a lot of Open Source projects is that the quality is variable and/or is of a secondary concern. This is supported to a certain degree by a lot of projects which do minimal testing upstream and rely on downstream consumers to do more thorough testing. But, there is no reason that an open project can not also do QA in the open as part of the community. While the term QA will likely evoke a plethora of negative emotions from anyone who has worked in a corporate development environment, there can be real benefits to having a dedicated QA effort on an open source project. It enables transparency in how testing is done, lets anyone contribute and collaborate, and can signal to users the stability of a project. This talk will use OpenStack as an case study to explore how an open source project can do QA in an open manner and the potential benefits it can provide.
Matthew is currently a member of the OpenStack TC (Technical Committee) and was previously the PTL (project technical lead) of the OpenStack community's QA program from OpenStack's Juno development cycle in 2014 through the Mitaka development cycle in 2016. He is a core contributor on several Openstack projects and a core member of the OpenStack stable maintenance team. He has been working on and contributing to Open Source software for most of his career and has been primarily contributing to OpenStack since 2012. Matthew currently works for IBM on Upstream OpenStack development, working to make OpenStack better for everyone. Matthew has previously been a speaker at OpenStack summits, LinuxCons Japan and North America, FOSSASIA, PyConAU's OpenStack miniconf, and linux.conf.au's CI and Testing miniconf.