License & Governance
License
GNU Affero General Public License v3.0 with Additional Terms
Full license text: LICENSE
Quick Summary
✅ You Can
Use Free Association
Individuals, cooperatives, non-profits, governments, corporations
No restrictions on who can use it
No usage fees
Modify and Deploy
Fork it, adapt it, run your own instance
Create derivative works
Deploy at any scale
Run as Network Service
Must share your source code (AGPL requirement)
Must make modifications available
Ensures improvements benefit everyone
✅ You Must
Give Attribution
Credit the Free Association project
Prevents invisible use
Maintains project visibility
Share Modifications
If running as network service
Source code must be available
Modifications must use compatible license
Mark Modified Versions
Clearly indicate changes
Prevents protocol fragmentation
Maintains trust in canonical implementation
Why AGPL-3.0?
We want universal access without universal capture.
Core Principle
Anyone can use Free Association. No entity can capture it for proprietary advantage.
AGPL Ensures
Anyone Can Use It:
No restrictions on who
No restrictions on purpose
No restrictions on scale
Network Services Must Share:
Prevents proprietary capture
Ensures improvements benefit commons
Maintains open ecosystem
Modifications Remain Open:
Derivative works must share source
Keeps the commons healthy
Prevents enclosure
Why Additional Terms?
The additional terms (permitted by AGPL Section 7) add important protections:
Attribution Requirement
Purpose: Prevents invisible cooptation
Requirement: Modified versions must credit Free Association project
Protects: Project visibility and contributor recognition
Protocol Fidelity Marking
Purpose: Prevents trust-breaking fragmentation
Requirement: Modified versions that change protocol must be clearly marked
Protects: User trust in canonical protocol
Interoperability Commitment
Purpose: Prevents vendor lock-in
Requirement: Implementations should work toward interoperability standards
Protects: Network effects and user choice
Together: Open for All, Captured by None
The combination of AGPL-3.0 and additional terms ensures:
✅ Universal access and usage rights
✅ No proprietary capture of improvements
✅ Clear attribution and recognition
✅ Protocol integrity and trust
✅ Interoperability and user freedom
Reference Implementation
This repository is the canonical reference implementation of the Free Association protocol, maintained by the core development team.
Purpose
Demonstrates protocol conformance
Provides working example
Establishes implementation patterns
Serves as conformance benchmark
Other Implementations
Other implementations are encouraged, but:
Protocol conformance measured against reference implementation
Must follow protocol specification: PROTOCOL.md
Should clearly mark deviations from protocol
Must comply with license terms
Governance
Project governance ensures:
Technical decisions based on mathematical correctness
Community input through RFC process
Transparent decision-making
Consensus-seeking approach
Full Governance Documentation: GOVERNANCE.md
Key Points
Protocol Changes:
RFC process for proposals
Community discussion (2-4 weeks minimum)
Mathematical verification required
Documented rationale for decisions
Maintainership:
Current core maintainer: Tom Guimberteau
Responsibilities: Review contributions, facilitate RFCs, maintain reference implementation
Community Participation:
Everyone welcome to submit issues and RFCs
Participate in discussions
Contribute code improvements
Share implementation experiences
Trademark
Status: Application in process
Current Policy:
"Free Association" name should be used accurately
Modified versions should be clearly marked as such
Prevents confusion and maintains trust
Future: Formal trademark policy once application complete
FAQ
Can I use Free Association in my commercial product?
Yes. AGPL permits commercial use. If you run it as a network service, you must share your source code.
Can I create a proprietary version?
No. AGPL requires derivative works to use compatible license. Network service deployments must share source.
What if I just want to use it internally?
Internal use doesn't trigger source sharing requirement. Only network services (where users interact over network) require sharing source.
Do I need permission to deploy?
No. License grants deployment rights. Follow license terms (attribution, source sharing if network service, marking modifications).
Can I charge for Free Association services?
Yes. AGPL permits commercial services. Must share source code if running as network service.
What about the additional terms?
Additional terms permitted by AGPL Section 7. Compatible with AGPL, add attribution and protocol fidelity requirements.
How do I comply with the license?
Include license and attribution in your deployment
If network service: Make source code available
If modified: Clearly mark modifications
If protocol changes: Mark as non-conformant or follow RFC process
Where do I get help with compliance?
Email: [email protected]
Subject: License compliance question
We're happy to help you comply with license requirements.
Questions?
Licensing Questions: [email protected]
Protocol Questions: See PROTOCOL.md or open an issue
Governance Questions: See GOVERNANCE.md
Technical Questions: GitHub Issues
Summary: Free Association is open source (AGPL-3.0) with additional terms ensuring attribution, protocol integrity, and interoperability. Universal access. No proprietary capture. Clear rules. Community governance.
Last updated