<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 1, 2016, at 10:57 AM, Russell Bryant <<a href="mailto:rbryant@redhat.com" class="">rbryant@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Jun 1, 2016 at 1:15 PM, Edgar Magana <span dir="ltr" class=""><<a href="mailto:edgar.magana@workday.com" target="_blank" class="">edgar.magana@workday.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri" class="">Russell,<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri" class="">All those references can be fixed. We do not feel like an impediment for this proposal.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri" class="">In terms of alternatives, we believe that this is the best and mostly the correct way to move forward.</span></p></blockquote></div><br class=""><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">We can certainly fix the references we control. Others we do not control.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">One example: <a href="https://twitter.com/search?f=tweets&q=governance.openstack.org" class="">https://twitter.com/search?f=tweets&q=governance.openstack.org</a></div><div class="gmail_extra"><br class=""></div><div class="gmail_extra"><span style="font-family:arial,helvetica,sans-serif" class=""><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;display:inline">To be clear, I understand and support the idea that you want some kind of "equal footing" with the TC's documentation.</div></span></div></div></div></div></blockquote><div><br class=""></div><div>I’m not sure combining these sources into the same repo makes sense from an “ownership” perspective.</div><div><br class=""></div><div>The existing content includes TC resolutions and project rules. Because of the nature of the content, we’ve limited roll call reviewers and merge access to the TC and TC chair respectively. It seems like the UC is going to want similar control over their own content, and doing that would be simpler using a separate repository published to a separate site. We don’t put any board content in the existing repo either, so it’s not like having a separate repo would be unequal or disadvantaging the UC.</div><div><br class=""></div><div>I’d be happy to help with the work of setting up a sphinx repo to publish a separate site for the UC if you want a hand.</div><div><br class=""></div><div>Doug</div></div><br class=""></body></html>