t4we fan
29d8cdcc44
Create docs/plugin-ecosystem(.en).md as the ecosystem manifesto: an open, composable, sustainable vision with composition-first, declare-clearly, and compatibility-first principles, the desktop shell as the first example, living-document community governance, and the marketplace as the trust signal. The root README intro now ends with the co-progress vision and links the manifesto; the docs index and root README tables list it; the plugin-development ecosystem-vision section points to it as the full statement.
2.4 KiB
DSH Plugin Ecosystem Manifesto
中文 | English
The DSH plugin ecosystem is growing quickly. The more plugins there are, the more their ability to work together matters: if every plugin assumes or even overrides another plugin's internals, installing a few plugins starts to conflict and the ecosystem fragments. This is nobody's fault — it is the natural result of missing shared conventions.
Our vision
We want to build an open, composable, and sustainable DSH plugin ecosystem:
- Open: anyone can participate; official, desktop, and third-party plugins compose on the same platform as equals.
- Composable: plugins extend against the same conventions, so they can be installed together and work together without interfering with each other.
- Sustainable: upgrades stay backward compatible, so the ecosystem can evolve long-term without being rebuilt from scratch.
Three principles we advocate
- Composition first: compose capabilities through official slots, services, and patches; do not assume or override other plugins' internals.
- Declare clearly: state the services and slots you depend on; do not rely on runtime coincidences.
- Compatibility first: keep upgrades backward compatible and never break existing compositions.
The desktop shell is the first example
DSH Desktop is the first practitioner of this approach: the desktop shell itself is an ordinary DSH plugin on the same composition path as official and third-party plugins, with no special privileges. We did not fork upstream source into a fixed shell — we made "the desktop" an equal member of the plugin ecosystem.
A living document, built with the community
This manifesto is not a unilateral rulebook. It is a living document: it follows ecosystem practice and accepts community discussion and revision. Any author can propose changes through issues, discussions, or pull requests.
The plugin marketplace: making conventions the beneficial choice
Once the plugin marketplace ships, plugins that follow this manifesto will be easier to discover, install, and trust. We want convention-driven development to be the beneficial choice for every author, not an extra burden.
How to participate
- Learn how plugins are written in plugin development.
- Learn how to install and manage plugins in the user guide.
- Share your thoughts on this manifesto through issues and discussions.