[openstack-dev] [openstack-ansible] Implement rotations for meetings handling

Mike Carden mike.carden at gmail.com
Thu May 3 08:39:18 UTC 2018

Hi OSA peeps.

I apologise in advance for what may seem like an impertinent question. And
for those playing along at home, I was just getting the hang of
contributing to OSA when last year my employer decided that some of us were
no longer needed, and OpenStack lost quite a few full time employed

So my question is... what is the health status of OSA? Is there still a
core of committed contributors? I only check in on OSA code reviews rarely
now, but activity seems a lot less than it was.

Before you answer, imagine that I now work for a moderately large,
potential consumer of OSA.

Is OSA the future, or have other deployment projects made it less relevant?


On Thu, May 3, 2018 at 6:13 PM, Andy McCrae <andy.mccrae at gmail.com> wrote:

>> Now that we are all part-time, I'd like to toy with a new idea,
>> proposed in the past by Jesse, to rotate the duties with people who
>> are involved in OSA, or want to get involved more (it's not restricted
>> to core developers!).
>> One of the first duties to be handled this way could be the weekly
>> meeting.
>> Handling the meeting is not that hard, it just takes time to prepare,
>> and to facilitate.
>> I think everyone should step into this, not only core developers, but
>> core developers are now expected to run the meetings when their turn
>> comes.
>> What are the actions to take:
>>     - Prepare the triage. Generate the list of the bugs for the week.
>>     - Ping people with the triage links around 1h before the weekly
>> meeting. It would give them time to get prepared for meeting,
>> eventually updating the agenda, and read the current bugs
>>     - Ping people at the beginning of the meeting
>>     - Chair the meeting: The structure of the meeting is now always
>> the same, a recap of the week, and handling the bug triage.
>>     - After the meeting we would ask who is volunteer to run next
>> meeting, and if none, a meeting char will be selected amongst core
>> contributors at random.
>> Thank you for your understanding.
>> Jean-Philippe Evrard (evrardjp)
> I will gladly pick up my well-used meeting chair hat.
> It's a great idea, I think it would help make our meetings more productive.
> Once you've been chair you have a different view of how the meetings work.
> Andy
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20180503/2c513a56/attachment.html>

More information about the OpenStack-dev mailing list