<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 1, 2020 at 10:22 AM Philip Reames via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</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">
<div>
<p>One other thought, since it came up on the apple branch thread.</p>
<p>I think we need to be very specific about the fact that code in
an incubator has been contributed to LLVM. I think this is
implicit in the statements about license and policy, but having
this be made explicit seems worthwhile. This would, for instance,
make it obvious that code could be moved between repository
without further involvement of the original authors.</p>
<p>Again, I think this is covered by the existing text, but leaving
no room for ambiguity here seems worthwhile. :)</p></div></blockquote><div><br></div><div>+1 - This is actually a significant part of why I originally advocated for this approach. The reality is that many of us have various hurdles and ambiguities around collaborating with each other but are explicitly allowed/encouraged to do so in the context of contributions to LLVM and engaging in public as part of this community. Being explicit that a contribution to an incubator project is a contribution to LLVM is a bright line that is easy to point at (and hopefully understand). I'll leave the opinion of whether it is fine to leave this implicit vs explicit to those more knowledgeable about the vagaries of such things. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>Philip<br>
</p>
<div>On 7/1/20 10:11 AM, Philip Reames
wrote:<br>
</div>
<blockquote type="cite">
<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
<a href="http://incubator.llvm.org" target="_blank">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>
<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>On 6/30/20 8:29 PM, Mehdi AMINI via
llvm-dev wrote:<br>
</div>
<blockquote type="cite">
<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" target="_blank">llvm-dev@lists.llvm.org</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">
<div style="overflow-wrap: break-word;">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">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">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">llvm-dev@lists.llvm.org</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">
<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">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">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">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">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">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">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">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
LLVM Developers mailing list
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
</blockquote>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div></div>