<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Jun 22, 2020, at 11:07 PM, Stella Laurenzo via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""><div><blockquote type="cite" class="">Per the recent (seeming) consensus regarding incubating new projects under the LLVM organization, I would like to trial the process by requesting to incubate <a href="https://github.com/google/mlir-npcomp" class="">mlir-npcomp</a>. The project is still quite young and has been primarily developed part time by myself and Sean Silva over the last ~2 months. We set it up following discussion of a <a href="https://llvm.discourse.group/t/numpy-scipy-op-set/768" class="">Numpy/Scipy op set</a> and also in conjunction with a proving ground for high level dialects/transforms for lowering from "numpy-aligned" frontends (e.g. sometimes labeled TCF/TCP).<br class=""></blockquote><div><br class=""></div>Awesome.</div><div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="">So, as the first one walking through the door, what is the process we would like to follow? I'm happy to provide more information/discussion, but I'd also be happy if with just an LGTM and someone creating an "mlir-npcomp" repository under the LLVM GitHub organization and working the rest out as we go.</div></div></blockquote><br class=""></div><div>I feel like we have general consensus that something like an incubator process is a good idea, but I think we should converge on adding a new section to the LLVM Developer Policy that describe what an incubator project is, and outline the requirements (following the policy etc).</div><div><br class=""></div><div>Could you help put together a draft of a patch? If not, I can take a look at this this weekend.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>