[llvm-dev] [Incubation] Request to incubate mlir-npcomp

[Mehdi AMINI via llvm-dev]

On Wed, Jun 24, 2020 at 2:37 AM Chris Lattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On Jun 22, 2020, at 11:07 PM, Stella Laurenzo via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> Per the recent (seeming) consensus regarding incubating new projects under
> the LLVM organization, I would like to trial the process by requesting to
> incubate mlir-npcomp <https://github.com/google/mlir-npcomp>. 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 Numpy/Scipy op set
> <https://llvm.discourse.group/t/numpy-scipy-op-set/768> 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).
>
>
> Awesome.
>
> 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.
>
>
> 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).
>
> Could you help put together a draft of a patch?  If not, I can take a look
> at this this weekend.
>

Now that the proposal landed, we could resume the discussion on this
proposal?

I haven't been involved with mlir-npcomp directly so far, but I'm very
interested in seeing this moving forward: it has a lot of potential as an
incubator project!

-- 
Mehdi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200709/7943a0c9/attachment.html>