<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 12/9/2019 12:41 PM, Kendall Nelson
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJ6yrQiWLGVZPY=BD2q0d_G9Ee9gx9f5U0U3y_RB8S6NP2fk8g@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr"><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Mon, Dec 9, 2019 at 10:13
            AM Ghanshyam Mann <<a
              href="mailto:gmann@ghanshyammann.com"
              moz-do-not-send="true">gmann@ghanshyammann.com</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex"> ---- On Fri, 06 Dec 2019
            14:02:07 -0600 Jeremy Stanley <<a
              href="mailto:fungi@yuggoth.org" target="_blank"
              moz-do-not-send="true">fungi@yuggoth.org</a>> wrote
            ----<br>
             > On 2019-12-06 12:54:00 -0600 (-0600), Jay Bryant
            wrote:<br>
             > > <snip><br>
             > > > The point I was making in another fork of
            this thread was to tie the<br>
             > > > exact term length to the election timing and
            only state approximate<br>
             > > > lengths here, ie including 'minimum' in the
            above will still set a bound<br>
             > > > that complicates accommodating another
            slightly smaller than usual<br>
             > > > cycle.<br>
             > > > <br>
             > > </snip><br>
             > > <br>
             > > I am in agreement with Dean that the easiest and
            most flexible<br>
             > > solution is to tie the term lengths to the
            elections and not state<br>
             > > a particular minimum or maximum.<br>
             > [...]<br>
             > <br>
             > Does this satisfy what's required by the bylaws
            though?<br>
             > <br>
             >     the term for the members of the Technical
            Committee shall be<br>
             >     approved by a majority of the Technical Committee
            (“Term”) and<br>
             >     shall be published publicly before each Technical
            Committee<br>
             >     election; if no such Term is published the Term
            will be twelve<br>
             >     calendar months.<br>
             > <br>
             >     <a
href="https://www.openstack.org/legal/technical-committee-member-policy/"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.openstack.org/legal/technical-committee-member-policy/</a><br>
             > <br>
             > I guess it doesn't *strictly* require a term duration
            to be<br>
             > specified as an explicit measure of time, so it's
            possible to<br>
             > interpret it as allowing terms to be defined according
            to some other<br>
             > criteria as long as they don't also exceed 16 months.<br>
            <br>
            I agree with mapping the TC term with the election.<br>
            <br>
            bylaws say:<br>
            " the elections for the Technical Committee shall be held in
            two phases: the first<br>
             election being for at least half of the members of the
            Technical Committee and <br>
            the second election being for the remaining members of
            Technical Committee."<br>
            <br>
            Because Elections dates are not explicitly mentioned (as we
            do not know the future events final dates)<br>
            and are divided into two-phase. Current TC charter states
            'The election is held no later than 6 weeks prior to each
            OpenStack Summit'<br>
            which makes the term length etc tricky. If we can define the
            specific week for both phases then it can be<br>
            consistent. <br>
          </blockquote>
          <div><br>
          </div>
          <div class="gmail_default"
            style="font-family:tahoma,sans-serif;font-size:small">Just
            throwing this idea out there (its probably already been
            discussed at some point).. but what if we just tie it to
            releases instead of to events since events are way more
            variable than releases?</div>
          <div class="gmail_default"
            style="font-family:tahoma,sans-serif;font-size:small"><br>
          </div>
          <div class="gmail_default"
            style="font-family:tahoma,sans-serif;font-size:small">-Kendall
            (diablo_rojo)</div>
        </div>
      </div>
    </blockquote>
    <p>Good point.  Given the recent changes and the fact that even
      schedules have become more variable, it may make sense to follow
      the release schedule that is remaining relatively static.</p>
    <p><br>
    </p>
    <p>Jay</p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:CAJ6yrQiWLGVZPY=BD2q0d_G9Ee9gx9f5U0U3y_RB8S6NP2fk8g@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <div class="gmail_default"
            style="font-family:tahoma,sans-serif;font-size:small"><br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <br>
            I feel R-4 can be fixed week: <br>
             - 4th weeks prior to each cycle final release date (R-4) is
            the fixed week to conduct the election. <br>
             - And make PTL and TC election as a combine election always
            at R-4.<br>
            <br>
            TC term can be documented as a "two-cycle term".<br>
            <br>
             [2] <a
              href="https://governance.openstack.org/tc/reference/charter.html"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://governance.openstack.org/tc/reference/charter.html</a><br>
            <br>
            -gmann<br>
            <br>
             > -- <br>
             > Jeremy Stanley<br>
             ><br>
            <br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
  </body>
</html>