2 project(s) screened and waiting. Each row is a recommendation; reply in one comment saying what you want, e.g. "accept all but X and Y -- X because ..., Y because ...". Rows marked on hold are asking something else and are listed under Held back below.
| # |
project |
licence |
duplicate effort |
viable |
recommend |
| 1 |
DynOSAM |
BSD-3-Clause (t1) |
none -- no AMD-Ecosystem/ROCm repo, all 33 upstream forks vanilla, no AMD mention in upstream docs |
yes |
fork |
| 2 |
cuda_voxelizer |
MIT (t1) |
none |
yes |
on hold |
- DynOSAM -- ROS2 dynamic-object SLAM (BSD-3, 327 stars, active): its GPU-critical half is cv::cuda PyrLK/GoodFeatures, already ported and validated by our own opencv_contrib on gfx1100, and its own CUDA is one 327-line .cu; what decides it is whether we accept reimplementing its raw-TensorRT YOLOv8 inference on MIGraphX (no ONNX Runtime layer exists) inside a ROS2 + GTSAM + from-source-OpenCV stack.
- full write-up:
projects/DynOSAM/notes.md
- cuda_voxelizer -- Small, actively-maintained MIT CUDA mesh voxelizer with a real GPU kernel path and no existing AMD/ROCm port; two vendored NVIDIA CUDA-Samples helper headers (helper_cuda.h, helper_string.h) carry old restrictive EULA-style text and should be reviewed/replaced during the port even though the project's own code is clean MIT.
- full write-up:
projects/cuda_voxelizer/notes.md
Held back
Flagged with triage.py verify because something needs settling before fork-or-decline is even the right question. They are in the table above and they do need an answer -- just an answer to what is written here. Clearing the flag (triage.py unskip <owner/repo>) returns one to an ordinary row.
Forceflow/cuda_voxelizer -- vendored NVIDIA CUDA-Samples headers under the old EULA notice; admin deciding whether forking is acceptable
This table is a snapshot. It is regenerated in place only while nobody has answered; once a decision is recorded this issue closes and anything still undecided returns as a new one, so a reply always refers to the table above it.
2 project(s) screened and waiting. Each row is a recommendation; reply in one comment saying what you want, e.g. "accept all but X and Y -- X because ..., Y because ...". Rows marked on hold are asking something else and are listed under Held back below.
projects/DynOSAM/notes.mdprojects/cuda_voxelizer/notes.mdHeld back
Flagged with
triage.py verifybecause something needs settling before fork-or-decline is even the right question. They are in the table above and they do need an answer -- just an answer to what is written here. Clearing the flag (triage.py unskip <owner/repo>) returns one to an ordinary row.Forceflow/cuda_voxelizer-- vendored NVIDIA CUDA-Samples headers under the old EULA notice; admin deciding whether forking is acceptableThis table is a snapshot. It is regenerated in place only while nobody has answered; once a decision is recorded this issue closes and anything still undecided returns as a new one, so a reply always refers to the table above it.