<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Good overview.  Thank you!</p>
    <p>One additional goal I want to mention on the list, for awareness,
      is the fact that we would like to eventually get some consistency
      to the pages that the 'Contributor Guide' lands on for each of the
      projects.  Needs to be a page that is friendly to new
      contributors, makes it easy to learn about the project and is not
      overwhelming.</p>
    <p>What exactly that looks like isn't defined yet but I have talked
      to Manila about this.  They were interested in working together on
      this.  Cinder and Manila will work together to get something
      consistent put together and then we can work on spreading that to
      other projects once we have agreement from the SIG that the
      approach is agreeable.</p>
    <p>Jay</p>
    <p>(jungleboyj)<br>
    </p>
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 3/5/2018 2:00 PM, Kendall Nelson
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJ6yrQjaCsCLo3XbemXonovLH7p1GKFbw68726HwsNT_7FATcA@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>Hello Everyone :) <br>
                <br>
              </div>
              It was wonderful to see and talk with so many of you last
              week! For those that couldn't attend our whole day of
              chats or those that couldn't attend at all, I thought I
              would put forth a summary of our discussions which were
              mostly noted in the etherpad[1]<br>
              <br>
            </div>
            <div>#Contributor Guide#<br>
            </div>
            <div><br>
              - Walkthrough: We walked through every section of what
              exists and came up with a variety of improvements on what
              is there. Most of these items have been added to our
              StoryBoard project[2]. This came up again Tuesday in docs
              sessions and I have added those items to StoryBoard as
              well. <br>
              <br>
            </div>
            <div>- Google Analytics: It was discussed we should do
              something about getting the contributor portal[3] to
              appear higher in Google searches about onboarding. Not
              sure what all this entails. NEEDS AN OWNER IF ANYONE WANTS
              TO VOLUNTEER.<br>
            </div>
            <div><br>
            </div>
            <div>#Mission Statement#<br>
              <br>
            </div>
            <div>We updated our mission statement[4]! It now states: <br>
              <br>
              To provide a place for new contributors to come for
              information and advice. This group will also analyze and
              document successful contribution models while seeking out
              and providing information to new members of the community.<br>
            </div>
            <div><br>
            </div>
            <div>#Weekly Meeting#<br>
            </div>
            <div><br>
            </div>
            <div>We discussed beginning a weekly meeting- optimized for
              APAC/Europe and settled on 800 UTC in #openstack-meeting
              on Wednesdays. Proposed here[5]. For now I added a section
              to our wiki for agenda organization[6]. The two main items
              we want to cover on a weekly basis are new contributor
              patches in gerrit and if anything has come up on <a
                href="http://ask.openstack.org" moz-do-not-send="true">ask.openstack.org</a>
              about contributors so those will be standing agenda items.<br>
            </div>
            <div><br>
              #Forum Session#<br>
              <br>
            </div>
            <div>We discussed proposing some forum sessions in order to
              get more involvement from operators. Currently, our
              activities focus on development activities and we would
              like to diversify. When this SIG was first proposed we
              wanted to have two chairs- one to represent developers and
              one to represent operators. We will propose a session or
              two when the call for forum proposals go out (should be
              today).<br>
            </div>
            <div><br>
            </div>
            <div>#IRC Channels#<br>
            </div>
            <div>We want to get rid of #openstack-101 and begin using
              #openstack-dev instead. The 101 channel isn't watched
              closely enough anymore and it makes more sense to move
              onboarding activities (like in OpenStack Upstream
              Institute) to a channel where there are people that can
              answer questions rather than asking those to move to a new
              channel. For those concerned about noise, OUI is run the
              weekend before the summit when most people are traveling
              to the Summit anyway. <br>
              <br>
            </div>
            <div>#Ongoing Onboarding Efforts#<br>
            </div>
            <div><br>
              - GSOC: Unfortunately we didn't get accepted this year. We
              will try again next year. <br>
            </div>
            <div><br>
              - Outreachy: Applications for the next round of interns
              are due March 22nd, 2018 [7]. Decisions will be made by
              April and then internships run May to August. <br>
            </div>
            <div><br>
              - WoO Mentoring: The format of mentoring is changing from
              1x1 to cohorts focused on a single goal. If you are
              interested in helping out, please contact me! I NEED HELP
              :) <br>
              <br>
            </div>
            <div>- Contributor guide: Please see the above section. <br>
              <br>
            </div>
            <div>- OpenStack Upstream Institute: It will be run, as
              usual, the weekend before the Summit in Vancouver.
              Depending on how much progress is made on the contributor
              guide, we will make use of it as opposed to slides like
              previous renditions. There have also been a number of
              OpenStack Days requesting we run it there as well. More
              details of those to come. <br>
              <br>
            </div>
            <div>#Project Liaisons#<br>
              <br>
            </div>
            <div>The list is filling out nicely, but we still need more
              coverage. If you know someone from a project not listed
              that might be willing to help, please reach out to them
              and get them added to our list [8].<br>
            </div>
            <div><br>
              I thiiiiiink that is just about everything. Hopefully I at
              least covered everything important :) <br>
              <br>
              Thanks Everyone!<br>
            </div>
            <div><br>
            </div>
            - Kendall Nelson (diablo_rojo)<br>
            <br>
            [1] PTG Etherpad <a
              href="https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG"
              moz-do-not-send="true">https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG</a>
            <br>
          </div>
          [2] StoryBoard Tracker <a
            href="https://storyboard.openstack.org/#%21/project/913"
            moz-do-not-send="true">https://storyboard.openstack.org/#!/project/913</a>
          <br>
        </div>
        <div>[3] Contributor Portal <a
            href="https://www.openstack.org/community/"
            moz-do-not-send="true">https://www.openstack.org/community/</a>
          <br>
        </div>
        [4] Mission Statement Update <a
          href="https://review.openstack.org/#/c/548054/"
          moz-do-not-send="true">https://review.openstack.org/#/c/548054/</a>
        <br>
        <div>
          <div>
            <div>[5] Meeting Slot Proposal <a
                href="https://review.openstack.org/#/c/549849/"
                moz-do-not-send="true">https://review.openstack.org/#/c/549849/</a>
              <br>
            </div>
            <div>[6] Meeting Agenda <a
                href="https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda"
                moz-do-not-send="true">https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda</a>
              <br>
            </div>
            <div>[7] Outreachy <a
                href="https://www.outreachy.org/apply/"
                moz-do-not-send="true">https://www.outreachy.org/apply/</a>
              <br>
            </div>
            <div>[8] Project Liaisons <a
href="https://wiki.openstack.org/wiki/First_Contact_SIG#Project_Liaisons"
                moz-do-not-send="true">https://wiki.openstack.org/wiki/First_Contact_SIG#Project_Liaisons</a>
              <br>
            </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>