<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Folks, <br>
    </p>
    <p>if this is an issue, let's handle it like this:</p>
    <p>- the bidding teams *can* send their proposal to me & someone
      else from CC (Guido? Michael?), if they want to get rid of it
      before the official deadline and if they fear publishing their
      proposal to the public earlier than other teams<br>
    </p>
    <p>  - in that case the bidder posts only a submission-note on the
      ML</p>
    <p>  - if not, they are open to publish their proposal via the
      mailing list, just like it was the years before</p>
    This does not apply for LoI's.<br>
    <br>
    Is that okay (I feel that we don't need a motion here)?<br>
    <br>
    Till<br>
    <p><br>
    </p>
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">Am 17.09.2018 um 11:30 schrieb michael
      terner:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAFk2e0KLeT4_qc8qXP6LTOgYKGX0atEc_dMfGr-UMdyfi_2iZA@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_default" style="font-family:tahoma,sans-serif">+1 <br>
        </div>
        <div class="gmail_default" style="font-family:tahoma,sans-serif"><br>
        </div>
        <div class="gmail_default" style="font-family:tahoma,sans-serif">I
          like the notion of an "email announcement" to the list stating
          "we have submitted and are ready for the next phase of
          Q&A".</div>
        <div class="gmail_default" style="font-family:tahoma,sans-serif"><br>
        </div>
        <div class="gmail_default" style="font-family:tahoma,sans-serif">mt</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Sun, Sep 16, 2018 at 2:41 PM Guido Stein <<a
            href="mailto:guido@guidostein.com" moz-do-not-send="true">guido@guidostein.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Good points,
          <div><br>
          </div>
          <div>I think announcement that the proposal has been submitted
            makes sense.</div>
          <div><br>
          </div>
          <div>Guido<br>
            <br>
            <div class="gmail_quote">
              <div dir="ltr">On Sat, Sep 15, 2018, 3:46 PM Eli Adam <<a
                  href="mailto:eadam@co.lincoln.or.us" target="_blank"
                  moz-do-not-send="true">eadam@co.lincoln.or.us</a>>
                wrote:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">On
                Wed, Sep 12, 2018 at 11:49 PM, Till Adams <<a
                  href="mailto:till.adams@fossgis.de" target="_blank"
                  moz-do-not-send="true">till.adams@fossgis.de</a>>
                wrote:<br>
                > Guido,<br>
                ><br>
                > Most importantly to me and perhaps should be
                discussed here is that I think<br>
                > that we should make the collection of the full
                proposals private until we<br>
                > are ready to release them all on the wiki. This
                would make it possible for<br>
                > people who turned their proposals early to feel
                secure that their<br>
                > competitors are not using the information from
                their publicly shared<br>
                > proposal in the competitive bid.<br>
                ><br>
                <br>
                Sounds reasonable.  I think that the old method was a
                combination of<br>
                waiting until close to the deadline and thinking that if
                other LOCs<br>
                need to look at yours, they've got no chance anyway.<br>
                <br>
                ><br>
                > the 2 times I was involved, we had once only 1
                proposal, for 2019 the<br>
                > proposals came in within the last 2 hours of the
                period. So this was no<br>
                > issue, but I see your point.<br>
                ><br>
                > In order to keep this fair also, we might have two
                people out of CC who<br>
                > receive the proposals and these 2 have the duty to
                release them on the list<br>
                > when the proposal period ends. As chair, I can be
                one of these two.<br>
                <br>
                I would still like to require that the LOCs email the
                list before the<br>
                deadline that they have turned in their proposals.  This
                ensures that<br>
                they are subscribed to the mailing list, who speaks for
                the LOC,<br>
                directs response questions and comments at them, etc. 
                It also lets<br>
                them set the subject line and otherwise establish the
                groundwork for<br>
                their bid.  It also publicly announces it before the
                deadline.  Then<br>
                you or any designated third party can reply with the
                attachment after<br>
                the deadline.<br>
                <br>
                <br>
                Best regards, Eli<br>
                <br>
                ><br>
                > Till<br>
                ><br>
                ><br>
                ><br>
                > Does anyone have an objection to this?<br>
                ><br>
                > Guido<br>
                ><br>
                > On Wed, Sep 12, 2018 at 9:28 AM Till Adams <<a
                  href="mailto:till.adams@fossgis.de" target="_blank"
                  moz-do-not-send="true">till.adams@fossgis.de</a>>
                wrote:<br>
                >><br>
                >> Dear CC!<br>
                >><br>
                >> We have a draft of the RfP document for the
                2020 call now:<br>
                >><br>
                >> The draft RfP is<br>
                >> at<br>
                >> <a
href="https://docs.google.com/document/d/14ltOnAoiFSTl7ERdlFKUvx-Jh9eDpVQgEn4AoCIp4SE/edit?usp=sharing"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://docs.google.com/document/d/14ltOnAoiFSTl7ERdlFKUvx-Jh9eDpVQgEn4AoCIp4SE/edit?usp=sharing</a><br>
                >><br>
                >> Due to Steven, this is an open document, anyone
                with the link can view<br>
                >> and comment.<br>
                >><br>
                >> I know we are little late, but the document is
                based on the RfP of the<br>
                >> past years. Feel free to comment on this
                document until *this* friday<br>
                >> (14.09.2018) 12h CET, after that I will kick
                out the call for 2020 and<br>
                >> we have to finalize the document and resolute
                all comments.<br>
                >><br>
                >> Special thanks to Steven and Michael, who did
                the main work and<br>
                >> improvements on this document!<br>
                >><br>
                >> Till<br>
                >> _______________________________________________<br>
                >> Conference_dev mailing list<br>
                >> <a
                  href="mailto:Conference_dev@lists.osgeo.org"
                  target="_blank" moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
                >> <a
                  href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
                ><br>
                > _______________________________________________<br>
                > Conference_dev mailing list<br>
                > <a href="mailto:Conference_dev@lists.osgeo.org"
                  target="_blank" moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
                > <a
                  href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
                ><br>
                ><br>
                ><br>
                ><br>
                > _______________________________________________<br>
                > Conference_dev mailing list<br>
                > <a href="mailto:Conference_dev@lists.osgeo.org"
                  target="_blank" moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
                > <a
                  href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a><br>
                _______________________________________________<br>
                Conference_dev mailing list<br>
                <a href="mailto:Conference_dev@lists.osgeo.org"
                  target="_blank" moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
                <a
                  href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a></blockquote>
            </div>
          </div>
          _______________________________________________<br>
          Conference_dev mailing list<br>
          <a href="mailto:Conference_dev@lists.osgeo.org"
            target="_blank" moz-do-not-send="true">Conference_dev@lists.osgeo.org</a><br>
          <a
            href="https://lists.osgeo.org/mailman/listinfo/conference_dev"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/conference_dev</a></blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"
        data-smartmail="gmail_signature">
        <div dir="ltr">
          <div>
            <div dir="ltr">
              <div>
                <div dir="ltr">
                  <div><font face="tahoma, sans-serif">Michael Terner</font></div>
                  <div><a href="mailto:ternergeo@gmail.com"
                      target="_blank" moz-do-not-send="true"><font
                        face="tahoma, sans-serif">ternergeo@gmail.com</font></a></div>
                  <div><font face="tahoma, sans-serif">(M) 978-631-6602</font></div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <!--'"--><br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Conference_dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Conference_dev@lists.osgeo.org">Conference_dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/conference_dev">https://lists.osgeo.org/mailman/listinfo/conference_dev</a></pre>
    </blockquote>
    <br>
  </body>
</html>