Open Stack

Just going to keep it short,
I think this is a great idea and would like to participate/chair.

From: Andrea Frittoli [mailto:andrea.frittoli at gmail.com]
Sent: Friday, November 17, 2017 5:54 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; openstack-operators at lists.openstack.org; openstack-sigs at lists.openstack.org
Subject: [openstack-dev] [QA] Proposal for a QA SIG

Dear all,

during the last summit in Sydney we discussed the possibility of creating an
OpenStack quality assurance special interest group (OpenStack QA SIG).
The proposal was discussed during the QA feedback session [0] and it received
positive feedback there; I would like to bring now the proposal to a larger
audience via the SIG, dev and operators mailing lists.

The mission of the existing QA Program in OpenStack is to “develop, maintain,
and initiate tools and plans to ensure the upstream stability and quality of
OpenStack, and its release readiness at any point during the release cycle” [1].
While the mission statement is quite wide, the only QA that we have visibility on
is what happens upstream, which is limited with pre-merge testing, with the only
exception of periodic tests.

There’s a lot of engineering that goes into OpenStack QA downstream, and there
have been several attempts in the past to share this work and let everyone in the
community benefit from it. The QA SIG could be a forum to make this happen:
share use cases, tests, tools, best practises and ideas beyond what we test today
in upstream; enable everyone doing QA in the OpenStack community to benefit
from the QA work that happens today.

Adjacent communities may be interested in participating to a QA SIG as well.
The opnfv community [2] performs QA on OpenStack releases today and they
are actively looking for opportunities to share tools and test cases.

Please reply to this email thread to express interest in participating / chairing a
QA SIG, if I get enough positive feedback I’ll setup the SIG as forming [4], and we
can then continue the conversation on the SIG mailing list and eventually setup
an initial meeting.

Thank you,

Andrea Frittoli (andreaf)


[0] https://etherpad.openstack.org/p/SYD-forum-qa-tools-plugins<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_SYD-2Dforum-2Dqa-2Dtools-2Dplugins&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=afs6hELVfCxZDDqAHhTowQ&m=jUvfpUyzPRLQXEEng0s-su6A6Rs2pkbFP3qw8fKWeSQ&s=ApJs95NnJ4kz6e8bpd4bbFfsLVUvyPxRkYbepKniyw0&e=>
[1] https://wiki.openstack.org/wiki/QA<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_QA&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=afs6hELVfCxZDDqAHhTowQ&m=jUvfpUyzPRLQXEEng0s-su6A6Rs2pkbFP3qw8fKWeSQ&s=P5UsabqPkx-va-YxxMFOgZ1ImwLhThYc_cXC2LtOVlg&e=>
[2] https://www.opnfv.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opnfv.org_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=afs6hELVfCxZDDqAHhTowQ&m=jUvfpUyzPRLQXEEng0s-su6A6Rs2pkbFP3qw8fKWeSQ&s=OERoWwj9HG0G-lDWCp_2fKXedlkOKNJsR_qWfhGRhjw&e=>
[3] https://wiki.openstack.org/wiki/Performance_Team<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Performance-5FTeam&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=afs6hELVfCxZDDqAHhTowQ&m=jUvfpUyzPRLQXEEng0s-su6A6Rs2pkbFP3qw8fKWeSQ&s=zUc0GKlPJdD1QPz3LbIzhOXYaYAmGTvTSRgwNU9y9BA&e=>
[4] https://wiki.openstack.org/wiki/OpenStack_SIGs<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_OpenStack-5FSIGs&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=afs6hELVfCxZDDqAHhTowQ&m=jUvfpUyzPRLQXEEng0s-su6A6Rs2pkbFP3qw8fKWeSQ&s=d3_KjzsMevqDOTyW8BK-fqjXh8Md1whaBlNxeyTQBrI&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171117/cdbd4499/attachment.html>