[tripleo] rework of triple squads and the tripleo mtg.

Marios Andreou marios at redhat.com
Tue Feb 4 16:48:19 UTC 2020

On Tue, Feb 4, 2020 at 6:12 PM Wesley Hayutin <whayutin at redhat.com> wrote:

> Greetings,
> As mentioned at the previous tripleo meeting [1], we're going to revisit
> the current tripleo squads and the expectations for those squads at the
> tripleo meeting.
> Currently we have the following squads..
> 1. upgrades
> 2. edge
> 3. integration
> 4. validations
> 5. networking
> 6. transformation
> 7. ci
> A reasonable update could include the following..
> 1. validations
> 2. transformation
> 3. mistral-to-ansible
> 4. CI
> 5. Ceph / Integration?? maybe just Ceph?
> 6. others??
> The squads should reflect major current efforts by the TripleO team IMHO.

so I agree with the notion that current efforts are discussed/reported
on/summarized etc during the tripleo weekly but I'd be careful about saying
'these are the only squads'. Something like upgrades for example is still
very much ongoing (though as far as I understand this is now splintered
into 3 subgroups, updates, upgrades and migrations) even if they aren't
reporting during the meeting as a habit.

Instead of just accepting this absence and saying there is no upgrades
squad, instead lets try and get them to check in to the meeting more often.

I think upgrades is a special case, perhaps the above also applies to the
networking squad too. Otherwise agree with your new list, but as above I'd
be careful not to exclude folks that *are* working on $tripleo_stuff but
for _reasons_ (likely workload/pressure) aren't coming to the tripleo

just my 2c thanks

> For the meetings, I would propose we use this time and space to give
> context to current reviews in progress and solicit feedback.  It's also a
> good time and space to discuss any upstream blockers for those reviews.
> Let's give this one week for comments etc..  Next week we'll update the
> etherpad list and squads.  The etherpad list will be a decent way to
> communicate which reviews need attention.
> Thanks all!!!
> [1]
> http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.00.log.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200204/be7e3d9a/attachment.html>

More information about the openstack-discuss mailing list