How, with no company or non-profit organization to own an open source project, can I arrange for the project community to hold the ownership of the web site, vs. one person.
Simple in theory, but someone has to pay the server bill (not a lot, cost isn't my concern), someone holds the keys to the domain name, and while one could hand out SSH access to any number of admins, some person or company must be the owner-in-name of the VPS instance or other hosting platform.
Right now, we've got a former project owner that wants to move on, and is happy enough for us to take over the site. But it's been difficult to contact him 'til now, and I'd like to plan for the project to avoid that in future. One guy's absence shouldn't torpedo a project.
It's the "hit by a bus"/"won the lottery" problem: an open source project has a problem when its site owner is no longer interested or available, but perhaps unwilling or unable to cede control to others. Were the owner to suddenly shuffle off the mortal coil, the domain, server, everything could be tied up in probate, and even deleted or domain sold before the community could migrate it.
So is there a generally well-known way to hold the site in community trust without a company or non-profit set up?
I have googled quite a bit, but the results always assume I want to learn to build a site, or start an open source project. The query to find good info is probably difficult to structure.