<div dir="ltr">Hi OSA peeps.<div><br></div><div>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 contributors.</div><div><br></div><div>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.</div><div><br></div><div>Before you answer, imagine that I now work for a moderately large, potential consumer of OSA.</div><div><br></div><div>Is OSA the future, or have other deployment projects made it less relevant?</div><div><br></div><div>-- </div><div>MC</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 3, 2018 at 6:13 PM, Andy McCrae <span dir="ltr"><<a href="mailto:andy.mccrae@gmail.com" target="_blank">andy.mccrae@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Now that we are all part-time, I'd like to toy with a new idea,<br>
proposed in the past by Jesse, to rotate the duties with people who<br>
are involved in OSA, or want to get involved more (it's not restricted<br>
to core developers!).<br>
<br>
One of the first duties to be handled this way could be the weekly meeting.<br>
<br>
Handling the meeting is not that hard, it just takes time to prepare,<br>
and to facilitate.<br>
<br>
I think everyone should step into this, not only core developers, but<br>
core developers are now expected to run the meetings when their turn<br>
comes.<br>
<br>
<br>
What are the actions to take:<br>
- Prepare the triage. Generate the list of the bugs for the week.<br>
- Ping people with the triage links around 1h before the weekly<br>
meeting. It would give them time to get prepared for meeting,<br>
eventually updating the agenda, and read the current bugs<br>
- Ping people at the beginning of the meeting<br>
- Chair the meeting: The structure of the meeting is now always<br>
the same, a recap of the week, and handling the bug triage.<br>
- After the meeting we would ask who is volunteer to run next<br>
meeting, and if none, a meeting char will be selected amongst core<br>
contributors at random.<br>
<br>
Thank you for your understanding.<br>
<br>
Jean-Philippe Evrard (evrardjp)<br></blockquote></div></div><div class="gmail_extra"><br></div></span><div class="gmail_extra">I will gladly pick up my well-used meeting chair hat.</div><div class="gmail_extra">It's a great idea, I think it would help make our meetings more productive.</div><div class="gmail_extra">Once you've been chair you have a different view of how the meetings work.</div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra">Andy</div></font></span></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>