#sovereignopencore — Public Fediverse posts

meaning with #SovereignOpenCore you have no vendor lock-in in terms of being able to scale-up and not related to the ability to access data. you can choose to no longer license if you think you can support the code and deploy yourself (or via someone else). you can then of course also develop your own replacement plugins for UX convenience.

#SovereignOpenCore vendors can therefore make money in the following ways:

1) hosting the code
2) support
3) UX convenience plugins
4) funded development

has anyone coined a term for #OpenCore #OSS licenses code, where the fundamental principle is that only UX convenience features are allowed to be proprietary? all data must be accessible through open souce means, nothing related to scaling shall be proprietary and the plugin system must also be documented and open?

if not I shall label it #SovereignOpenCore.

in this model companies would finance themselves through support and plugins that enable more efficient interaction with the data.