Community scheme gallery #33

New issue

Open

opened 2026-07-07 17:39:23 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-07 17:39:23 +00:00

Contributor

Goal

A lightweight way to share and discover schemes across Iris installs, keyed by event_key, so a user can pull someone else's great "Diwali" or "Halloween" scheme instead of authoring from scratch.

Why it's valuable

Iris already has scheme export/import (M9). A shared gallery adds content network effects — the hardest part of holiday lighting is good schemes, and sharing amortizes that curation across users.

Why it's a v2 bet

It adds an external surface (hosting/index, discovery, and light moderation/trust concerns) beyond a single self-hosted instance — a product/infra decision, not just a feature.

Sketch

Reuse the existing scheme serialization for a shareable unit keyed by event_key + tags + attribution.
Options to weigh in design: a curated git-backed repo Iris can pull from (simplest, no hosting), vs. a hosted index with submission/browse.
Import path reuses the M9 import + segment-mapping wizard; imported schemes land as candidates for approval.

Acceptance criteria

Browse/pull community schemes by event_key/tag from within Iris
Imported schemes go through the normal candidate → approve flow
Attribution preserved
A decision recorded on the hosting model (git-backed vs. hosted index)

Proposed enhancement (brainstorm follow-up).

## Goal A lightweight way to share and discover schemes across Iris installs, keyed by `event_key`, so a user can pull someone else's great "Diwali" or "Halloween" scheme instead of authoring from scratch. ## Why it's valuable Iris already has scheme export/import (M9). A shared gallery adds content network effects — the hardest part of holiday lighting is good schemes, and sharing amortizes that curation across users. ## Why it's a v2 bet It adds an external surface (hosting/index, discovery, and light moderation/trust concerns) beyond a single self-hosted instance — a product/infra decision, not just a feature. ## Sketch - Reuse the existing scheme serialization for a shareable unit keyed by `event_key` + tags + attribution. - Options to weigh in design: a curated git-backed repo Iris can pull from (simplest, no hosting), vs. a hosted index with submission/browse. - Import path reuses the M9 import + segment-mapping wizard; imported schemes land as candidates for approval. ## Acceptance criteria - [ ] Browse/pull community schemes by `event_key`/tag from within Iris - [ ] Imported schemes go through the normal candidate → approve flow - [ ] Attribution preserved - [ ] A decision recorded on the hosting model (git-backed vs. hosted index) Proposed enhancement (brainstorm follow-up).

claude-bot added the

labels

2026-07-07 17:39:48 +00:00