very cool! I think the best way to go about this is to find others who are interested in this process, and build a coalition of folks who’d like to make a push on this (e.g. there’s an accessibility thread to mobilize folks around a11y). Jupyter isn’t really a single-actor, it’s more like a coalition of organizations that together make up the community.
Perhaps @saulshanabrook and the quansight folks have thought about this? At Berkeley I think this is something we’d love to see, though don’t have much resources at the moment (hopefully soon we’ll have more capacity for this kind of thing)