We’re pretty short on manpower too, as the CuArrays.jl issue backlog shows… But well-isolated/documented issues are always appreciated, i.e. don’t hesitate to file issues on CUDAdrv for those specific API additions.
I’ll try and get back to some of your issues in this post when I have the time, but don’t hold your breath. The problem is that adding functionality to CUDAdrv isn’t much effort, but tying it into a usable API at the CuArrays level is much harder…