<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 7/1/20 2:12 PM, Chris Lattner wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7859A175-E17D-4529-A124-907950F2DFFE@nondot.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Jul 1, 2020, at 10:11 AM, Philip Reames <<a
href="mailto:listmail@philipreames.com" class=""
moz-do-not-send="true">listmail@philipreames.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
<div class="">
<p class="">This looks to be a reasonable starting point.</p>
<p class="">A couple of nit picks, none are blockers.</p>
<ol class="">
<li class="">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 <a
href="http://incubator.llvm.org" class=""
moz-do-not-send="true">incubator.llvm.org</a> page
which links to the docs defining the process and lists
all active incubators with links to docs in their own
repo?</li>
</ol>
</div>
</div>
</blockquote>
<div>Sounds great, I’m happy to take this out - this avoids
“promising” it, but we can still discuss it on a case-by-case
basis. I changed this to "Other infrastructure integration
can be discussed on a case-by-case basis.”, because there are
bug tracker and other things as well.</div>
<blockquote type="cite" class="">
<div class="">
<div class="">
<ol class="" start="2">
<li class="">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>
</ol>
</div>
</div>
</blockquote>
<div>I’m not sure what you mean here. Do you have a recommended
approach?</div>
</div>
</blockquote>
Land yours, and if I still care, I'll send a patch. :)<br>
<blockquote type="cite"
cite="mid:7859A175-E17D-4529-A124-907950F2DFFE@nondot.org">
<div>
<blockquote type="cite" class="">
<div class="">
<div class="">
<ol class="" start="3">
<li class="">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>
</ol>
</div>
</div>
</blockquote>
<div>I hear what you’re saying, but I think we can handle this
as part of the approval process. We can bounce of things that
qualitatively don’t feel credible and give guidance there, but
can still be receptive if something seems like a promising
direction.</div>
<blockquote type="cite" class="">
<div class="">
<div class="">
<ol class="" start="4">
<li class="">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>
</div>
</div>
</blockquote>
<div>Yes, this is a good idea. The problem here is “how do we
decide who qualifies as a sponsor?”. I don’t know a good way
to say that - someone with N years of LLVM experience, M
patches, …? How does this get explained?</div>
</div>
</blockquote>
<p>You said elsewhere that we could let this evolve with
experience. I would take that sentiment, and apply it here. I'm
really more concerned about the expectations of the role (i.e.
some human familiar with LLVM norms willing to invest non-trivial
time), than I am the details of who is eligible.</p>
<p>Since I don't want this to be blocking item, why don't we land
what you have and I can draft something as a patch? It seems like
there's some general agreement about a potential issue and we just
need to find a way to address it. <br>
</p>
<blockquote type="cite"
cite="mid:7859A175-E17D-4529-A124-907950F2DFFE@nondot.org">
<div>
<div><br class="">
</div>
<div>-Chris</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<ol class="" start="4">
</ol>
<p class="">Philip<br class="">
</p>
<div class="moz-cite-prefix">On 6/30/20 8:29 PM, Mehdi
AMINI via llvm-dev wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:CANF-O=ZZRUM0bRbhjV5E-QQMfsJmANHfG8pNbK5Wx5F9i4Mn0A@mail.gmail.com"
class="">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8" class="">
<div dir="ltr" class="">Looks like a good proposal to me
as-is! Thanks for putting this together to both of you
:)
<div class=""><br class="">
</div>
<div class="">-- </div>
<div class="">Mehdi</div>
<div class=""><br class="">
</div>
</div>
<br class="">
<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" class="">llvm-dev@lists.llvm.org</a>>
wrote:<br class="">
</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"
class="">Hah, whoops, sorry about that. This is
the correct link:
<div class=""><a
href="https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit"
target="_blank" moz-do-not-send="true"
class="">https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit</a></div>
<div class=""><br class="">
</div>
<div class="">-Chris<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Jun 30, 2020, at 1:41 PM,
Thomas Lively <<a
href="mailto:tlively@google.com"
target="_blank" moz-do-not-send="true"
class="">tlively@google.com</a>>
wrote:</div>
<br class="">
<div class="">
<div dir="ltr" class="">Hi Chris,
<div class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">Thomas</div>
</div>
<br class="">
<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" class="">llvm-dev@lists.llvm.org</a>>
wrote:<br class="">
</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 class=""><br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Jun 30, 2020,
at 11:52 AM, Roman Lebedev
<<a
href="mailto:lebedev.ri@gmail.com"
target="_blank"
moz-do-not-send="true"
class="">lebedev.ri@gmail.com</a>>
wrote:</div>
<br class="">
<div class="">
<div class="">On Tue, Jun 30,
2020 at 9:44 PM Chris
Lattner via llvm-dev<br
class="">
<<a
href="mailto:llvm-dev@lists.llvm.org"
target="_blank"
moz-do-not-send="true"
class="">llvm-dev@lists.llvm.org</a>>
wrote:<br class="">
<blockquote type="cite"
class=""><br class="">
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 class="">
<br class="">
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
class="">
<a
href="https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit"
target="_blank"
moz-do-not-send="true"
class="">https://docs.google.com/document/d/1ss4jGHywL0Y2KW_l4LqTo5CgJxx3i0_4-FkbXiPQMus/edit</a><br
class="">
</blockquote>
Currently it doesn't open,
"You need access", sanity
check: is viewing<br
class="">
allowed for everybody?<br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">It says that “anyone
on the internet is allowed to
comment”, maybe this link will
work better?:</div>
<div class=""><a
href="https://docs.google.com/document/d/1lC7cOJ2Iiqdx62o81J5YP7RzFHi8k2Rkt0zla-Kh6no/edit?usp=sharing"
target="_blank"
moz-do-not-send="true" class="">https://docs.google.com/document/d/1lC7cOJ2Iiqdx62o81J5YP7RzFHi8k2Rkt0zla-Kh6no/edit?usp=sharing</a></div>
<div class=""><br class="">
</div>
<div class="">In any case, if google
docs isn’t cooperating, then you
can check it out when it gets to
Phabricator.</div>
<div class=""><br class="">
</div>
<div class="">-Chris</div>
<div class=""><br class="">
</div>
</div>
_______________________________________________<br class="">
LLVM Developers mailing list<br
class="">
<a
href="mailto:llvm-dev@lists.llvm.org"
target="_blank"
moz-do-not-send="true" class="">llvm-dev@lists.llvm.org</a><br
class="">
<a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br
class="">
</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br
class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org"
target="_blank" moz-do-not-send="true" class="">llvm-dev@lists.llvm.org</a><br
class="">
<a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br
class="">
</blockquote>
</div>
<br class="">
<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" moz-do-not-send="true">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</blockquote>
</body>
</html>