01 / PROPOSE
Describe the need.
Start with the production problem, a reproducible bug or a design proposal. Explain who it helps and include a small example.
Explore ↗DEVELOPMENT / OPEN PROCESS / SHARED DIRECTION
Bring a production need, discuss an improvement and help test the result. Our direction is fully free and open-source software, with clear decisions and dependable releases.
SHOWAVE · Powered by Afro Unity Group
01 / PROPOSE
Start with the production problem, a reproducible bug or a design proposal. Explain who it helps and include a small example.
Explore ↗02 / DISCUSS
Use the issue discussion to compare approaches and scope the work. Maintainers should record the decision and its rationale.
Explore ↗03 / DEVELOP
Work in a branch, follow the project guidance and include relevant tests. Share progress in a pull request that reviewers can understand.
Explore ↗04 / REVIEW
Maintainers review the change, contributors respond and affected users test the workflow. Funding does not determine review outcomes.
Explore ↗05 / VALIDATE
Test real media and hardware, check for regressions, update the manual and make limits explicit before release.
Explore ↗06 / RELEASE
Prepare versioned packages, release notes and matching source and license information. Unfinished work moves forward without a promised date.
Explore ↗Live, Broadcast, Encode, Forge, Map, Chaser, Timeline and Grid Tool, with the linked GSL5 Lighting Library. A visible workspace does not mean every native integration is finished.
Read the details ↗Windows x64 preview.4, Linux x64 preview.2 and an Android offline interface/player review. Existing installers are snapshots and differ in capability.
Read the details ↗Continue performance, audio, presentation and output work; compare actual media, decks, fixtures and devices. Stable packaging needs hardware validation and documented limits.
Read the details ↗Reliability and regression checks, supported hardware rehearsals, release documentation, platform packaging and a clear upgrade path. No stable release date is announced.
Read the details ↗File export in Encode, native plug-in compilation in Forge, a stable extension SDK, a marketplace and an MCP server. Current local status APIs are documented separately.
Read the details ↗Grow from the 56 vendor-neutral sample archetypes toward a 1,000+ fixture-profile target, with proper profiles and tests for real equipment. This is not 1,000 supported brands.
Read the details ↗Academy activities, survey responses, recent guides and store requests can be drafted locally. They are not public posts, shared results or placed orders.
Read the details ↗Connect identity, moderated video storage, public activity feeds, survey collection, confirmed commerce and payment reconciliation. The current localhost build does not provide those services.
Read the details ↗A dedicated SHOWAVE payment destination, confirmed sponsorship arrangements and verified funding reports. Current optional donations identify Novus Foundation Uganda as recipient.
Read the details ↗Make source publicly accessible, publish the selected software license and document how to build each release. The current repository remains the development home; no license has been announced here.
Read the details ↗PREVIEW / BETA
Try a small rehearsal and prepare reproducible feedback. Read the platform notes before installing.
Review the preview ↗STABLE / PLANNED
A stable release needs dependable workflows, hardware evidence and documented upgrade behavior. There is no stable installer to download today.
Current release notes ↗COMMUNITY / STEWARDSHIP
Maintainers and contributors shape the roadmap around shared needs. Sponsors help sustain the work without buying control of project decisions.
How decisions work ↗This workflow draws on Blender’s approach to focused contributions, maintainer review and release quality. SHOWAVE is an independent project.
Blender’s contribution handbook ↗