From e873349c768bb8bce1dd628affae2e46e2c6fa88 Mon Sep 17 00:00:00 2001 From: Quick104 <31828688+Quick104@users.noreply.github.com> Date: Sun, 6 Sep 2026 12:28:40 -0400 Subject: [PATCH] docs: add naming and branding guidance for plugin authors Follows Silo-Server/siloserver.org#16, which makes the policy in that repository canonical and adds naming, writing, and colour guidance. Co-Authored-By: Claude Fable 5.1 --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index 7ef173b..864d133 100644 --- a/README.md +++ b/README.md @@ -248,6 +248,17 @@ Read [CONTRIBUTING.md](CONTRIBUTING.md) and Public Go, protobuf, runtime, and manifest changes should start as an issue and identify affected downstream repositories. +## Naming and branding + +Give your plugin its own name and mention Silo in the summary, for example +"Trakt sync plugin for Silo". Repository and package names such as +`silo-plugin-trakt` are fine, since "silo" only describes what the code plugs +into. Avoid "Silo[word]" product names such as SiloTrakt, which read as +official, and do not use the Silo logo as your plugin's icon. Set +`publisher_name` to yourself, not "Silo", unless the plugin is published by the +project. The full guidance, including what needs no permission, is at +. + ## License Apache-2.0. See [LICENSE](LICENSE).