main
Greenfield (AGPL) vs MIT-Licensed Custom Compositor — Comparison
This repo holds the head-to-head decision matrix comparing:
- Option A — Use Greenfield as-is (AGPL-3.0): faster time-to-market, but AGPL contamination forces the entire Odoo fork to be open-sourced.
- Option B — Build a fully MIT-licensed custom compositor (this bundle's recommended path).
Final recommendation: Option B. See Greenfield-vs-MIT-Comparison.md for the full analysis with person-week estimates per phase.
Related repos
one-os-dev-wayland-html5-compositor-greenfield-analysis— deep analysis of Greenfield (the reference implementation)one-os-dev-wayland-html5-compositor-mit-compositor-analysis— architecture & build plan for our MIT-licensed alternative
Description
Head-to-head comparison: Greenfield (AGPL) vs MIT-licensed custom compositor. Strong recommendation + person-week estimates.
35 KiB
0 Stars
1 Watchers
0 Forks
Languages
Markdown
100%