Open Stack

Hi

It will be happy to participate and help in driving this effort

Thanks

Ofer

On Sun, Nov 19, 2017 at 3:57 PM, Ofer Blaut <oblaut at redhat.com> wrote:

> Hi
>
> On Fri, Nov 17, 2017 at 11:25 PM, Rochelle Grober <
> rochelle.grober at huawei.com> wrote:
>
>> First off, let me say I think this is a tremendous idea.  And, it's
>> perfect for the SIG concept.
>>
>> Next, see inline:
>>
>> Thierry Carrez wrote:
>> > Andrea Frittoli wrote:
>> > > [...]
>> > > 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.
>> > > [...]
>> >
>> > I think this goes with the current trends of re-centering upstream
>> "project
>> > teams" on the production of software, while using SIGs as communities of
>> > practice (beyond the governance boundaries), even if they happen to
>> > produce (some) software as the result of their work.
>> >
>> > One question I have is whether we'd need to keep the "QA" project team
>> at
>> > all. Personally I think it would create confusion to keep it around,
>> for no gain.
>> > SIGs code contributors get voting rights for the TC anyway, and SIGs
>> are free
>> > to ask for space at the PTG... so there is really no reason (imho) to
>> keep a
>> > "QA" project team in parallel to the SIG ?
>>
>> Well, you can get rid of the "QA Project Team" but you would then need to
>> replace it with something like the Tempest Project, or perhaps the Test
>> Project.  You still need a PTL and cores to write, review and merge tempest
>> fixes and upgrades, along with some of the tests.  The Interop Guideline
>> tests are part of Tempest because being there provides oversight on the
>> style and quality of the code of those tests.  We still need that.
>>
>> --Rocky
>>
>> > In the same vein we are looking into turning the Security project team
>> into a
>> > SIG, and could consider turning other non-purely-upstream teams (like
>> I18n)
>> > in the future.
>> >
>> > --
>> > Thierry Carrez (ttx)
>> >
>> > _______________________________________________
>> > openstack-sigs mailing list
>> > openstack-sigs at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171119/0457052a/attachment.html>