On Tue, Apr 11, 2023 at 9:51 AM Hans Verkuil <hverkuil@xxxxxxxxx> wrote: > > One of my main concerns here is time: as subsystem maintainers we can barely > keep up with all the incoming patches. Introducing support for a new language > would add only more pressure. Even though these are mainly bindings (as I > understand it), this would still require that every change to a C kAPI is > duplicated in rust, requiring someone to do that work, and have maintainers > with enough rust knowledge to verify it. Indeed, that is one of the main costs. One potential solution is to have somebody step up as the maintainer of the Rust side (e.g. the author of the abstractions). Of course, that will not make the work go to zero, since there still needs to be some degree of communication even if the new maintainer does all the Rust side work, but it may make it feasible, especially if the abstracted parts of the C API do not change too frequently. It is also an opportunity for existing maintainers to see how the Rust side would work meanwhile the work gets done, and potentially a chance to get a new maintainer involved with the whole subsystem in the future. Some subsystems may want to give that maintainer a different `MAINTAINERS` entry, e.g. as a child subsystem that sends PRs to the main one and may be marked as "experimental". This is also a way to see how the new abstractions work or not, giving maintainers more time to decide whether to commit to a Rust side or not. I don't mean to say it would be doable for the media subsystem, but please consider it. Cheers, Miguel
