Here we explore the practice of commons of running code - relationships of folks who develop (code), folks who maintain (code, servers) and folks who 'just use', in truly plural ways. This includes the matter of wiki-farm hosting.
Peer-to-peer production of repos and assemblages of code is famously fèted as a commons. This is true enough. But the genres of collaboration, protocolling, curating and stewarding in a code commons - eg around a git codebase, a bunch of (largely individual) projects - are not the same as those that will be called for in a commons of running code. The users here are no longer identical with the producer-curators, this is multistakeholder, and how.
In the `commons.hour` project, meet.coop is at work on this challenge of multistakholder governance and stacked commons, with regard to a platform built around the video conferencing software stack of BBB - Big Blue Button. They broadly are adopting a DisCO frame (C=cooperative) rather than a Dao frame (A='autonomous'). See: meet.coop trial handbook gitbook 
> Add a DisCO link xxx. Meanwhile, try the <Search>
The aspect of most direct relevance to wiki is the question of hosting of wiki farms. The strong programming/free software tradition of wiki has led to an aesthetic of farms self-managed by wiki-authors as sysadmins. But for wiki to become vernacular, non-geeks must be able to cultivate wikis without having to manage servers.
Within the wiki community a number of folks have an interest in this counter-cultural development: Ward Cunningham, Robert Best, David Bovill, Jon Richter. Maybe Paul Riodwell regarding the data ownership and distribution approach (dat)? Watch this space. - Link some other wikis here, by these folks xxx
some first thoughts on a stack of commons, built on a commons of running code, are in Shared learning space aka commons