Meeting Notes

Lemonade Community Maintainers Meeting Notes

June 5, 2026

Attendees: (super)Mario, anditherobot, Anthony Mikinka (AMD), Bone, Daniel Holanda (AMD), fl0rianr, gavinbarnard, geramyl (mod), Jeremy Fowers (AMD), Kalin Ovtcharov (AMD), kenvandine, Krishna (AMD), mikkoph, Occam, Phoenix, primaL- (mod), sawan, TG95, Victoria (AMD)

Milestone for v10.7

• LMX omni models exposed to external OpenAI-compatible apps (Open WebUI, etc.), not just the Lemonade app
• Benchmarking tool ships with 10.7; early testers already finding non-optimal params on their machines
• Action: Finalize external app exposure for LMX models before tag

CI Testing / Health

• Hundreds of tests run on every PR; head of main is generally release-ready
• AMD-sponsored hardware covers Strix Halo on Windows and Linux
• Gap: no equivalent CI for Arm, Intel, CUDA
• Robust CI is the gating factor for faster release cadence
• Action: Ken to explore vendor donations of CI hardware via industry contacts

Release Cadence

• Strong consensus to move faster with more predictability
• Direction: weekly or bi-weekly stable tags on a fixed weekday (Wednesday preferred, avoid Friday)
• Cherry-picked point releases for urgent fixes
• Add a continuously refreshed "tip" channel (Ghostty-style) for developers wanting main builds
• Snap already does this via edge channel; Debian PPAs similar
• Windows signing capped daily, so signed Windows builds stay on stable cadence
• Unsigned Windows, Docker, Fedora could update daily
• Action: Continue discussion in Discord thread; Jeremy to share Ghostty link

Lemonade Working Groups

• New structure: six working groups, each led by a maintainer with autonomy to merge PRs and drive roadmap within scope
• Designed to unblock the ~80 open PR backlog and concentrate reviewer enthusiasm
• Some groups have a discrete end state (cross vendor), others are open-ended (omni)
• Separate maintainer table handles areas outside working groups (security, quality, distros, ROCm, etc.)
• Open question: possible new working group for backend / plugin system; Geramyl volunteered to lead
• Action: Leads to draft charters with scope and, where possible, completion criteria

Lemonade Omni Models

• Led by Jeremy
• Virtual omni via LMX router behind an OpenAI-style interface
• Already shipped: LMX representation, image-gen perf improvements, GUI import/export
• Next: expose to any OpenAI-compatible client (in 10.7)
• Halo Tales reference RPG app is coded, pending release
• Occam noted naming overlap with true omni research models; current design is intentional and gives per-model customization that single omni models lack
• Action: Jeremy to release Halo Tales after 10.7 ships

Lemonade Auto Tune

• Led by Michele
• Splits machine-specific args (global to server) from model-specific args
• Benchmarking tool layered on top to find optimized params
• Goal: community-shared profiles for common archetypes (Strix Halo, dGPU configs)
• Ships in 10.7, CLI only for now
• Not using llama-bench (needs to work with FLM, vLLM and other backends; uses normal inference endpoint instead)
• Custom scenarios supported: short, multiturn, long-context (32K, 64K), coding vs non-coding (relevant for MTP)
• Action: Community help wanted on more benchmark scenarios; UI button for benchmarking to come later

Cross Vendor Support

• Led by Ken Van Dine
• Goal: Lemonade runs on all mass-market hardware so app developers can target Lemonade regardless of backend (AMD, NVIDIA RTX/Spark, Intel, Qualcomm, Arm64)
• Discrete checkbox-style scope; dissolves when complete
• Ken to leverage vendor relationships through day job, including potentially sourcing CI hardware
• IoT and embedded (Canonical core devices) in scope; mobile may need Geramy
• Action: Ken to draft the hardware matrix and pursue vendor partnerships

Cloud Local Hybrid

• Led by Krishna
• Open PR adds cloud backend: bring your own OpenAI-compatible API key, provider models appear in Lemonade, chat works seamlessly
• Not about upselling to cloud
• Intermediate step toward intelligent routing between cloud and local based on user-defined policy
• Lemonade owns the platform and interface, not the policy
• Policy format TBD (markdown file, separate HTTP service, etc.)
• AMD research teams looking at this, plus alignment with vLLM Semantic Router
• Geramyl and Sawan asked for an API to retrieve, manage, and secure policies; Krishna agreed
• Action: Land scaffolding PR, then add basic router, then policy API

Lemonade UI

• Led by Kyle
• Stack stays React plus Tauri to avoid framework-change debate
• New capabilities:
  • Self-configuration (LLM loads model and builds recipe)
  • Pulls recommended settings from HuggingFace
  • Multiple-choice question tool for agent interactions
  • Markdown rendering
• Roughly a month from release-ready
• Florian helping; more contributors needed
• Time to market is the differentiator now, not the features themselves
• Action: Kyle to bring a roadmap to next Friday's meeting; testers and UI contributors wanted

Networking

• Led by Geramy, with Nathan (kg95) on attestation
• Mesh network vision: install Lemonade and reach your nodes from anywhere; add servers and mobile devices to a private mesh
• Tier 1 nodes require TPM 2.0 hardware attestation
• VMs require TEE; otherwise capped at Tier 2 or lower
• Security model includes ban plus master key rotation on detected abuse (self-healing)
• Router demoed: token-based API, delegates by occupancy and TPS across two Strix Halos plus two Thunderbolt 5 R9700s (over 110 TPS)
• Pulls existing Lemonade collections; supports new ones
• Open proposal: subscription or credits model so mobile users without high-end hardware can use community-donated inference, with a percentage flowing back to Lemonade
• Raises broader question about commercial ventures built on Lemonade and how close they sit to the project itself
• Action: Dedicated discussion next week or later; Geramy to organize separate call for interested parties