<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    As would I...<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 26/08/2014 21:48, Adam Lawson wrote:<br>
    </div>
    <blockquote
cite="mid:CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com"
      type="cite">
      <p dir="ltr">I'd be happy to participate as needed Anne.</p>
      <div class="gmail_quote">On Aug 26, 2014 11:10 AM, "Anne Gentle"
        <<a moz-do-not-send="true" href="mailto:anne@openstack.org">anne@openstack.org</a>>

        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div dir="ltr">Hi all, 
            <div>Cross-posting to -docs and -operators. </div>
            <div><br>
            </div>
            <div>At the Ops mid-cycle meetup this week, Matt Griffin,
              David Medberry, and Sriram Subramanian offered to start a
              review team for the High Availability Guide. It needs some
              updates and it's best if the review team works similar to
              the Security Guide -- subject matter experts working with
              core docs team members for reviews. So I'm proposing we
              pull it into its own repo just like the Security Guide.
              Any reasons not to? I think the next steps are:</div>
            <div><br>
            </div>
            <div>1. Propose a patch to openstack/governance to show the
              repo is governed by the Docs program.</div>
            <div>2. Propose a patch that sets up a separate review team
              starting with Matt, David, and Sriram. We think Emilien
              would be interested too, sound good? Any others? We can
              have members of openstack-docs-core as well, similar to
              the Security Guide.</div>
            <div>3. Propose a patch that gets that guide building
              separately in a different repo.</div>
            <div>4.  Start working on the four bugs already logged [1]
              and logged more as needed.</div>
            <div><br>
            </div>
            <div>Any other subtasks? Any interested parties? </div>
            <div><br>
            </div>
            <div>Thanks,</div>
            <div>Anne</div>
            <div><br>
            </div>
            <div>1. <a moz-do-not-send="true"
href="https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide"
                target="_blank">https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide</a></div>
          </div>
          <br>
          _______________________________________________<br>
          OpenStack-operators mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
          <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
            target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
          <br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-operators mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Maish Saidel-Keesing
</pre>
  </body>
</html>