This is a general view on the topic. I think open-source isn’t enough, we need also governance for the software we use, and create small pockets of freedom.

All feedback is welcome.

  • Shin@piefed.socialOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 hours ago

    I’m not sure if I follow the question, let’s me try to understand.

    If you are talking about a self-hosting. This isn’t the governance, this is the “deployment” of a software. I know that I talk heavily on this point on the essay, but the focus is regarding that self host is a act on the individual level, while governance is about who use the system and have a say on it.

    I’ll grab a example, (I’ll avoid the Uber cliche, but maybe I need to take this one)


    Imagine a N-unit building, cooperative software replaces the landlord with a transparent governance dashboard (I’m assuming that all residents own each of the units in this building). Residents propose maintenance tasks (e.g., roof leaks) and collectively vote on fund allocation using a one-unit-one-vote system. The software automatically tracks each unit’s financial contributions, schedules shared laundry slots via a consensus calendar, and logs inspection reports viewable by all. When a major expense arises, the platform facilitates a binding poll, calculates each owner’s share, and executes payment only when the quorum is met, ensuring every resident has equal say over their shared physical assets.


    This is the example of governance that I was talking about. The people who use and own the building have a say on it. When something arives everyone have a way to discuss and talk, using the software as a tool to support then. Self-host is just the deployment for this system, but the focus is on the helping then to mitigate and ensure that everyone have a say in it.

    I hope I got your point right.