<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>This looks to be a reasonable starting point.</p>
    <p>A couple of nit picks, none are blockers.</p>
    <ol>
      <li>I'd hold off on handing out the sub-domain for the moment. 
        This feels more official than we probably want for a random
        incubator.  I reserve the right to change my mind here, but
        maybe we should delay this part until we see what actual
        incubators look like?  As an alternative, maybe have a common
        incubator.llvm.org page which links to the docs defining the
        process and lists all active incubators with links to docs in
        their own repo?</li>
      <li>The must/should terminology should probably be factored out
        once and referenced.  As written, it takes a little effort to be
        sure the definitions are the same between the two uses.</li>
      <li>I'm not sure I agree with the no-code standard.  I agree with
        minimal code, but I think an incubator should be established
        enough to be discussed concretely (e.g. "what is" vs "ideals").</li>
      <li>As I mentioned before, I'd advocate for the notion of a
        sponsor (an existing LLVM contributor) for each incubator.  I'd
        have that a must on the incubator list.</li>
    </ol>
    <p>Philip<br>
    </p>
    <div class="moz-cite-prefix">On 6/30/20 8:29 PM, Mehdi AMINI via
      llvm-dev wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANF-O=ZZRUM0bRbhjV5E-QQMfsJmANHfG8pNbK5Wx5F9i4Mn0A@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Looks like a good proposal to me as-is! Thanks for
        putting this together to both of you :)
        <div><br>
        </div>
        <div>-- </div>
        <div>Mehdi</div>
        <div><br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Jun 30, 2020 at 1:49
          PM Chris Lattner via llvm-dev <<a
            href="mailto:llvm-dev@lists.llvm.org" moz-do-not-send="true">llvm-dev@lists.llvm.org</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 style="word-wrap:break-word;line-break:after-white-space">Hah,
            whoops, sorry about that.  This is the correct link:
            <div><a
href="https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit"
                target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit</a></div>
            <div><br>
            </div>
            <div>-Chris<br>
              <div><br>
                <blockquote type="cite">
                  <div>On Jun 30, 2020, at 1:41 PM, Thomas Lively <<a
                      href="mailto:tlively@google.com" target="_blank"
                      moz-do-not-send="true">tlively@google.com</a>>
                    wrote:</div>
                  <br>
                  <div>
                    <div dir="ltr">Hi Chris,
                      <div><br>
                      </div>
                      <div>I'm also seeing an access denied error on the
                        first link you shared, and although I can access
                        the second document, it doesn't look like the
                        document you meant to share. It looks like a one
                        pager on ML in Swift.</div>
                      <div><br>
                      </div>
                      <div>Thomas</div>
                    </div>
                    <br>
                    <div class="gmail_quote">
                      <div dir="ltr" class="gmail_attr">On Tue, Jun 30,
                        2020 at 1:05 PM Chris Lattner via llvm-dev <<a
                          href="mailto:llvm-dev@lists.llvm.org"
                          target="_blank" moz-do-not-send="true">llvm-dev@lists.llvm.org</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><br>
                          <div><br>
                            <blockquote type="cite">
                              <div>On Jun 30, 2020, at 11:52 AM, Roman
                                Lebedev <<a
                                  href="mailto:lebedev.ri@gmail.com"
                                  target="_blank" moz-do-not-send="true">lebedev.ri@gmail.com</a>>
                                wrote:</div>
                              <br>
                              <div>
                                <div>On Tue, Jun 30, 2020 at 9:44 PM
                                  Chris Lattner via llvm-dev<br>
                                  <<a
                                    href="mailto:llvm-dev@lists.llvm.org"
                                    target="_blank"
                                    moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
                                  wrote:<br>
                                  <blockquote type="cite"><br>
                                    The idea of adding an “incubation”
                                    stage to projects in the LLVM world
                                    seems to be positively received.  I
                                    also noticed that we don’t really
                                    document the new project policy in
                                    general in the LLVM Developer
                                    Policy.  To help with both of these
                                    Stella and I worked together to
                                    draft up a new section for the LLVM
                                    developer policy (incorporating the
                                    existing “New Targets” section).<br>
                                    <br>
                                    Ahead of proposing a Phabricator
                                    patch, we put it into this google
                                    doc, I’d love to get feedback on it
                                    from anyone who is interested in
                                    this:<br>
                                    <a
href="https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit"
                                      target="_blank"
                                      moz-do-not-send="true">https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit</a><br>
                                  </blockquote>
                                  Currently it doesn't open, "You need
                                  access", sanity check: is viewing<br>
                                  allowed for everybody?<br>
                                </div>
                              </div>
                            </blockquote>
                          </div>
                          <br>
                          <div>It says that “anyone on the internet is
                            allowed to comment”, maybe this link will
                            work better?:</div>
                          <div><a
href="https://docs.google.com/document/d/1lC7cOJ2Iiqdx62o81J5YP7RzFHi8k2Rkt0zla-Kh6no/edit?usp=sharing"
                              target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/1lC7cOJ2Iiqdx62o81J5YP7RzFHi8k2Rkt0zla-Kh6no/edit?usp=sharing</a></div>
                          <div><br>
                          </div>
                          <div>In any case, if google docs isn’t
                            cooperating, then you can check it out when
                            it gets to Phabricator.</div>
                          <div><br>
                          </div>
                          <div>-Chris</div>
                          <div><br>
                          </div>
                        </div>
                        _______________________________________________<br>
                        LLVM Developers mailing list<br>
                        <a href="mailto:llvm-dev@lists.llvm.org"
                          target="_blank" moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
                        <a
                          href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
          _______________________________________________<br>
          LLVM Developers mailing list<br>
          <a href="mailto:llvm-dev@lists.llvm.org" target="_blank"
            moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
          <a
            href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
    </blockquote>
  </body>
</html>