<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 09/15/2015 10:50 AM, Anne Gentle wrote:<br>
<blockquote
cite="mid:CAD0KtVF=8tw6tw7DZ8kef+fB1ECO=JhnV72L=nLhgtSb+rorwQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>What can we do to make the cross-project meeting more
helpful and useful for cross-project communications? I started
with a proposal to move it to a different time, which morphed
into an idea to alternate times. But, knowing that we need to
layer communications I wonder if we should troubleshoot
cross-project communications further? These are the current
ways cross-project communications happen:</div>
<div><br>
</div>
<div>1. The weekly meeting in IRC</div>
<div>2. The cross-project specs and reviewing those</div>
<div>3. Direct connections between team members</div>
<div>
<div>4. Cross-project talks at the Summits</div>
<div><br>
</div>
<div>What are some of the problems with each layer? </div>
<div><br>
</div>
<div>1. weekly meeting: time zones, global reach, size of
cross-project concerns due to multiple projects being
affected, another meeting for PTLs to attend and pay
attention to</div>
</div>
</div>
</blockquote>
<br>
I would actually love to attend the cross-project IRC meeting but it
falls in a perfectly bad time for my time zone so I can never make
it. When daylight savings time end the first week of November I'll
start attending because it will be 1 hour earlier for me.<br>
<br>
<blockquote
cite="mid:CAD0KtVF=8tw6tw7DZ8kef+fB1ECO=JhnV72L=nLhgtSb+rorwQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>2. specs: don't seem to get much attention unless they're
brought up at weekly meeting, finding owners for the work
needing to be done in a spec is difficult since each project
team has its own priorities</div>
<div>3. direct communications: decisions from these comms are
difficult to then communicate more widely, it's difficult to
get time with busy PTLs</div>
<div>4. Summits: only happens twice a year, decisions made
then need to be widely communicated</div>
<div><br>
</div>
<div>I'm sure there are more details and problems I'm missing
-- feel free to fill in as needed. </div>
<div><br>
</div>
<div>Lastly, what suggestions do you have for solving problems
with any of these layers? </div>
<div><br>
</div>
<div>Thanks,</div>
<div>Anne</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>Anne Gentle</div>
<div>Rackspace</div>
<div>Principal Engineer</div>
<div><a moz-do-not-send="true"
href="http://www.justwriteclick.com" target="_blank">www.justwriteclick.com</a></div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>