[stdexec] Long-Term Ownership and Maintenance of stdexec Dependency

Hi OpenBMC Community,

I would like to start a discussion around the long-term ownership and maintenance model for the stdexec dependency that is currently part of the OpenBMC dependency chain. As I understand it today:

  *
bmcweb references sdbusplus through subprojects/sdbusplus.wrap:
     *
https://github.com/openbmc/bmcweb
  *
sdbusplus is maintained under the OpenBMC organization:
     *
https://github.com/openbmc/sdbusplus
     *
https://github.com/openbmc/sdbusplus/blob/master/subprojects/stdexec.wrap
  *
sdbusplus in turn references stdexec through subprojects/stdexec.wrap :
     *
https://github.com/NVIDIA/stdexec

First, I would like to acknowledge and appreciate the work that has gone into this implementation. The intent of this note is not to question the quality of the code or the contributions made by NVIDIA, but rather to discuss whether there may be an opportunity to align this dependency more closely with OpenBMC’s long-term governance and maintenance model. Since stdexec is now part of a commonly consumed dependency path within OpenBMC, it may be worth considering whether a community-maintained approach could provide additional benefits, such as:

  *
Reduced risk from repository access, policy, or ownership changes outside the OpenBMC project
  *
Broader review and maintainer participation and long-term support
  *
Improved community ownership , transparency and reduce dependency risk

If there have already been discussions on this topic, or if there is a preferred roadmap for the dependency, I would greatly appreciate any references or guidance. My goal is simply to explore whether we can further strengthen the sustainability, transparency, and long-term maintainability of the OpenBMC dependency ecosystem as it continues to grow.

Thank you for your time and consideration. I look forward to hearing the community’s thoughts.

Best regards,

Chinmoy Dey