<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 4, 2014 at 3:35 PM, Jay Dobies <span dir="ltr"><<a href="mailto:jason.dobies@redhat.com" target="_blank">jason.dobies@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As an example of something that I think doesn't add much value in the<br>
meeting - DerekH has already been giving semi-regular CI/CD status<br>
reports via email. I'd like to make these weekly update emails<br>
regular, and take the update off the meeting agenda. I'm offering to<br>
share the load with him to make this easier to achieve.<br>
</blockquote></blockquote>
<br></span>
The Tuskar item is the same way. Not sure how that was added as an explicit agenda item, but I don't see why we'd call out to one particular project within TripleO. Anything we'd need eyes on should be covered when we chime in about specs or reviews needing eyes.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are there other things on our regular agenda that you feel aren't<br>
offering much value?<br>
</blockquote>
<br>
I'd propose we axe the regular agenda entirely and let people promote<br>
things in open discussion if they need to. In fact the regular agenda<br>
often seems like a bunch of motions we go through... to the extent that<br>
while the TripleO meeting was going on we've actually discussed what was<br>
in my opinion the most important things in the normal #tripleo IRC<br>
channel. Is getting through our review stats really that important!?<br>
</blockquote>
<br></span>
I think the review stats would be better handled in e-mail format like Derek's CI status e-mails. We don't want the reviews to get out of hand, but the time spent pasting in the links and everyone looking at the stats during the meeting itself are wasteful. I could see bringing it up if it's becoming a problem, but the number crunching doesn't need to be part of the meeting.</blockquote><div><br></div><div>I agree; I think it's useful to make sure we keep on top of the stats, but I don't think it needs to be done in the meeting.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are there things you'd like to see moved onto, or off, the agenda?<br>
</blockquote>
<br>
Perhaps a streamlined agenda like this would work better:<br>
<br>
* Bugs<br>
</blockquote>
<br></span>
This one is valuable and I like the idea of keeping it.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* Projects needing releases<br>
</blockquote>
<br>
Is this even needed as well? It feels like for months now the answer is always "Yes, release the world".<br></blockquote><div><br></div><div>But the next question is: "Who is going to release the world?" and that is usually a volunteer from the meeting.</div><div><br></div><div>Perhaps if we had a regular release team this could be arranged outside of the meeting.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I think our cadence on those release can be slowed down as well (the last few releases I've done have had minimal churn at best), but I'm not trying to thread jack into that discussion. I bring it up because we could remove that from the meeting and do an entirely new model where we get the release volunteer through other means on a (potentially) less frequent release basis.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* Open Discussion (including important SPECs, CI, or anything needing<br>
attention). ** Leader might have to drive this **<br>
</blockquote>
<br></span>
I like the idea of a specific Specs/Reviews section. It should be quick, but a specific point in time where people can #info a review they need eyes on. I think it appeals to my OCD to have this more structured than interspersed with other topics in open discussion.</blockquote><div><br></div><div>One issue I have with these is that I don't know if they get seen by people who aren't at the meeting. Perhaps a weekly email pointing to the minutes and hilighing these would help?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>