lumi argues that the community around a software project shapes its values. A strong copyleft license can signal a commitment to software freedom, but it doesn’t tell you who controls the project or how contributors are treated.
The essay offers questions to ask alongside checking the license:
- Who makes decisions, and is the project controlled by a corporation?
- What do the code of conduct and contributor agreements require?
- Does the project depend on centralized platforms for its community?
- What values do its maintainers demonstrate in practice?
lumi points to an AGPL project with commercial dual licensing and a mandatory contributor license agreement as an example of why a license badge alone can miss how power is distributed. That is the author’s judgment about a particular arrangement, not a verdict on every commercially backed project.
The invitation is to participate in projects you rely on. Documentation, triage, artwork, outreach and community management all shape a project’s future alongside code.