<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 4, 2015 at 3:35 PM, Stefano Maffulli <span dir="ltr"><<a href="mailto:stefano@openstack.org" target="_blank">stefano@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Thanks Joe for bringing this up. I have always tried to find topics<br>
worth being covered in the weekly newsletter. I assemble that newsletter<br>
thinking of developers and operators as the main targets, I'd like both<br>
audiences to have one place to look at weekly and skim rapidly to see if<br>
they missed something interesting.<br>
<br>
Over the years I have tried to change it based on feedback I received so<br>
this conversation is great to have<br>
<br>
On 05/04/2015 12:03 PM, Joe Gordon wrote:<br>
> The  big questions I would like to see answered are:<br>
<span class="">><br>
> * What are the big challenges each project is currently working on?<br>
> * What can we learn from each other?<br>
> * Where are individual projects trying to solve the same problem<br>
> independently?<br>
<br>
</span>These are all important and interesting questions. When there were fewer<br>
projects it wasn't too hard to keep things together. Nowadays there is a<br>
lot more going on and in gerrit, which requires a bit more upfront<br>
investment to be useful.<br>
<span class=""><br>
> To answer these questions one needs to look at a lot of sources, including:<br>
><br>
> * Weekly meeting logs, or hopefully just the notes assuming we get<br>
> better at taking detailed notes<br>
<br>
</span>I counted over 80 meetings each week: if they all took excellent notes,<br>
with clear #info lines for the relevant stuff, one person would be able<br>
probably to parse them all in a couple hours every week to identify<br>
items worth reporting.<br>
<br>
My experience is that IRC meeting logs don't convey anything useful to<br>
outsiders. Pick any project log from<br>
<a href="http://eavesdrop.openstack.org/meetings/" target="_blank">http://eavesdrop.openstack.org/meetings/</a> and you'll see what I mean.<br>
Even the best ones don't really mean much to those not into the project<br>
itself.<br>
<br>
I am very skeptical that we can educate all meeting participants to take<br>
notes that can be meaningful to outsiders. I am also not sure that the<br>
IRC meeting notes are the right place for this.<br>
<br>
Maybe it would make more sense to educate PTLs and liasons to nudge me<br>
with a brief email or log in some sort of notification bucket a quick<br>
snippet of text to share with the rest of the contributors.<br>
<br></blockquote><div><br></div><div>Makes sense to me.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
> * approved specs<br>
<br>
More than the approved ones, which are easy to spot on<br>
<a href="http://specs.openstack.org" target="_blank">specs.openstack.org</a>, I think the new ones proposed are more interesting.<br>
<br>
Ideally I would find a way to publish draft specs on<br>
<a href="http://specs.openstack.org/drafts/" target="_blank">specs.openstack.org/drafts/</a> or somehow provide a way for uneducated (to<br>
gerrit) readers to more easily discover what's coming.<br>
<br>
Until a better technical solution exists, I can pull regularly from all<br>
status:open changesets from *-specs repositories and put them in a<br>
section of the weekly newsletter.<br></blockquote><div><br></div><div>You can search for the list of merged specs by age (last updated) to get a decent view of what merged since last week.</div><div> </div><div><a href="https://review.openstack.org/#/q/is:merged+age:1week+project:%255Eopenstack/.*-specs,n,z">https://review.openstack.org/#/q/is:merged+age:1week+project:%255Eopenstack/.*-specs,n,z</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span class=""><br>
> * periodically talk to the PTL of each project to see if any big<br>
> discussions were discussed else where<br>
<br>
</span>I think this already happen in the xproject meeting, doesn't it?<br></blockquote><div><br></div><div>Things come up in the xproject meeting that we already know to be cross project. If two projects independently are tackling the same issue they may not realize there is room for collaboration.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span class=""><br>
> * Topics selected for discussion at summits<br>
<br>
</span>I'm confused about this: aren't these visible already as part of the<br>
schedule?<br>
<span class=""><br></span></blockquote><div><br></div><div>Yes they are, but going through the list of all the topics and making a list of the big ticket items/highlights is still a lot of work.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">
> Off the top of my head here are a few topics that would make good<br>
> candidates for this newsletter:<br>
><br>
> * What are different projects doing with microversioned APIs, I know<br>
> that at least two projects are tackling this<br>
> * How has the specs process evolved in each project, we all started out<br>
> from a common point but seem to have all gone in slightly different<br>
> directions<br>
> * What will each projects priorities be in Liberty? Do any of them overlap?<br>
> * Any process changes that projects have tried that worked or didn't work<br>
> * How is functional testing evolving in each project<br>
<br>
</span>Great to have precise examples to work with. It's useful exercise to<br>
start from the end and trace back to where the answer will be. How would<br>
the answer to these question look like?<br>
<span class=""><br>
> Would this help with cross project communication? Is this feasible?<br>
> Other thoughts?<br>
<br>
</span>I think it would help, it is feasible. Let's keep the ideas rolling :)<br>
<br>
/stef<br>
<div class=""><div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>