<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I have proposed <a href="https://review.opendev.org/#/c/744005/">https://review.opendev.org/#/c/744005/</a>
      to expand the scope of the Operations Docs SIG to include tooling
      like this.</p>
    <p>Sean<br>
    </p>
    <div class="moz-cite-prefix">On 7/30/20 7:52 AM, Chris Morgan wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CA+NmNoNZ1xxynDXCSN+mnKCk0F0SW5ARXY4MjTR+PAaT64_8mw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">+1 to put these in the Operations Docs SIG<br>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Wed, Jul 29, 2020 at 12:25
          AM Fabian Zimmermann <<a href="mailto:dev.faz@gmail.com"
            moz-do-not-send="true">dev.faz@gmail.com</a>> wrote:<br>
        </div>
        <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">
          <div dir="auto">+1</div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">Laurent Dumont <<a
                href="mailto:laurentfdumont@gmail.com" target="_blank"
                moz-do-not-send="true">laurentfdumont@gmail.com</a>>
              schrieb am Mi., 29. Juli 2020, 04:00:<br>
            </div>
            <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">
              <div dir="ltr">Interested in this as well. We use
                Openstack a $Dayjob :)</div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Mon, Jul 27, 2020
                  at 2:52 PM Amy Marrich <<a
                    href="mailto:amy@demarco.com" rel="noreferrer"
                    target="_blank" moz-do-not-send="true">amy@demarco.com</a>>
                  wrote:<br>
                </div>
                <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">
                  <div dir="ltr">
                    <div>+1 on combining this in with the existing SiG
                      and efforts.</div>
                    <div><br>
                    </div>
                    <div>Amy (spotz)<br>
                    </div>
                  </div>
                  <br>
                  <div class="gmail_quote">
                    <div dir="ltr" class="gmail_attr">On Mon, Jul 27,
                      2020 at 1:02 PM Sean McGinnis <<a
                        href="mailto:sean.mcginnis@gmx.com"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">sean.mcginnis@gmx.com</a>>
                      wrote:<br>
                    </div>
                    <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"><br>
                      >> If Osops should be considered distinct
                      from OpenStack<br>
                      ><br>
                      > That feels like the wrong statement to make,
                      even if only implicitly<br>
                      > by repo organization. Is there a compelling
                      reason not to have osops<br>
                      > under the openstack namespace?<br>
                      ><br>
                      I think it makes the most sense to be under the
                      openstack namespace.<br>
                      <br>
                      We have the Operations Docs SIG right now that
                      took on some of the<br>
                      operator-specific documentation that no longer had
                      a home. This was a<br>
                      consistent issue brought up in the Ops Meetup
                      events. While not "wildly<br>
                      successful" in getting a bunch of new and updated
                      docs, it at least has<br>
                      accomplished the main goal of getting these docs
                      published to<br>
                      <a href="http://docs.openstack.org"
                        rel="noreferrer noreferrer" target="_blank"
                        moz-do-not-send="true">docs.openstack.org</a>
                      again, and providing a place where more
                      collaboration<br>
                      can (and occasionally does) happen to improve
                      those docs.<br>
                      <br>
                      I think we could probably expand the scope of this
                      SIG. Especially<br>
                      considering it is a pretty low-volume SIG anyway.
                      I would be good with<br>
                      changing this to something like the "Operator Docs
                      and Tooling SIG" and<br>
                      getting any of these useful tooling repos under
                      governance through that.<br>
                      I personally wouldn't be able to spend a lot of
                      time working on anything<br>
                      under the SIG, but I'd be happy to keep an eye out
                      for any new reviews<br>
                      and help get those through.<br>
                      <br>
                      Sean<br>
                      <br>
                      <br>
                    </blockquote>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature">Chris Morgan <<a
          href="mailto:mihalis68@gmail.com" target="_blank"
          moz-do-not-send="true">mihalis68@gmail.com</a>></div>
    </blockquote>
  </body>
</html>