Given the positive responses by >=5 institutions that want to invest in this, plus lots of positive comments on the original RFC, I hope this clears the bar set by our developers policy:
- Must be generally aligned with the mission of the LLVM project to advance compilers, languages, tools, runtimes, etc.
(I don’t think anyone would object to this.) - Must conform to all of the policies laid out in this developer policy document, including license, patent, coding standards, and code of conduct. (we already do and we plan to continue to do so.)
- Must have an active community that maintains the code, including established code owners. (I am happy to continue as code owner, but we will revisit this in our early meetings. The responses above show an active community is willing to form.)
- Should have reasonable documentation about how it works, including a high quality README file. (we got a non-trivial amount of information on the openmp.llvm.org webpage and we will spend effort on better documentation as one of the initial goals.)
- Should have CI to catch breakage within the project itself or due to underlying LLVM dependencies. (more CI will be added but we have one staging and one production buildbot)
- Should have code free of issues the community finds contentious, or be on a clear path to resolving them. (the code is upstream and we established the development board, we’ll add the Offload meeting, and the thematic working groups asap.)
- Must be proposed through the LLVM RFC process, and have its addition approved by the LLVM community - this ultimately mediates the resolution of the “should” concerns above. (I think the responses here show broad agreement, including on the way we can resolve existing issues.)
If nobody objects, I would like to start with some of the administrative tasks such that we can hit the ground running in 2024.
I will send out invites for the meeting later this year, I’m still waiting for more people to put their availability into the calendar above.
For now, I want to create the subproject folder, README and docs. Then webpage and GH teams/hooks. I’ll also make sure we test the initial commit on more systems to verify it does not break existing functionality of OpenMP offload.
I don’t recall how the webpage redirect is done but I can start writing content in llvm-project/offload/docs which we would show under offload.llvm.org.
~ J
Tag: @tonic @akorobeynikov @tstellar
(Side note: It hasn’t even been 8 years since something like this was first proposed: RFC: Proposing an LLVM subproject for parallelism runtime and support libraries, LLVM moves fast after all.)