<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Aug 13, 2014, at 4:05 PM, Dean Troyer <<a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 13, 2014 at 2:24 PM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">What “cross-project efforts” are we talking about? The liaison program in Oslo has been a qualified success so far. Would it make sense to extend that to other programs and say that each project needs at least one designated QA, Infra, Doc, etc. contact?<br>
</div>
</blockquote></div><div class="gmail_extra"><br></div>++1</div><div class="gmail_extra"><br></div><div class="gmail_extra">I've done this informally with DevStack and it has worked well enough that Ian is introducing a MAINTAINERS file where we'll record these 'delegations'. For those areas that don't have obvious representation or volunteers I'll pick someone based on the commits for that feature. That specific bit might not scale to other projects, but I think documenting some informal connectivity like this would be helpful.<br clear="all">
<div><br></div><div>dt</div></div></div></blockquote><div><br></div><div>That matches what we do in the Oslo incubator for code contributions. For the liaisons, we’re just using a wiki page [1] because I wanted people to be able to sign up without any sense of “approval” being needed (and without any delay having a LIAISONS commit approved). It’s quite likely that we’ll have a lot of turnover in Kilo, too, since I will ask everyone to volunteer again in case the projects (or current volunteers) want to rotate duties.</div><div><br></div><div>Those are are just implementation details, though. The key factor is asking for a specific name to be written down somewhere indicating that there is a volunteer, and then engaging with that person regularly (we reserve part of our weekly meeting for liaisons to raise issues they’re having in their project that need attention, for example).</div><div><br></div><div>Doug</div><div><br></div><div>[1] <a href="https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons">https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons</a></div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div><br></div>-- <br><br>Dean Troyer<br><a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a><br>
</div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>