Relicensing consent for pre-FSL contributions

Following up on #3089 with the full picture and the one action item that came out of it.

The numbers up front: 95.5% of the current codebase was written from scratch during the v2 rewrite. Of the ~4.5% that carried over from v1, ~98% was written by Spacedrive's employees and contractors under IP-assignment agreements. What remains — code in today's tree owned by community contributors — is about 1% of the codebase, held by the nine people tagged below. This issue exists to clear that last 1%.

Background. Spacedrive v2 is a ground-up rewrite I started in June 2025 (53b21a3fa). The license changed from AGPL-3.0 to FSL-1.1-ALv2 on March 24, 2026 (53b030c49). Every commit and release before that date remains AGPL-3.0 permanently — anyone can fork and continue from there under AGPL.

To verify we have the rights to distribute everything in the current tree under FSL, I ran a provenance analysis: blob-hash and path intersection between the last v1 commit (2fa63bb8c) and current main, plus a full-tree git blame with per-line author timestamps against the rewrite date (2025-06-18) and the license-change date (2026-03-24).

Ownership of the current tree (~326k lines of source, excluding assets/docs/lockfiles):

Category	Lines	Status
Written during the v2 rewrite by me	~308k	Spacedrive Technology Inc.
Carried from v1, written by Spacedrive employees & contractors	~14.3k	Company-owned — employment/contractor agreements with IP assignment
Community PRs merged during v2 before the license change	~3.1k	Owned by their authors, contributed under AGPL — consent requested below
v1 community code in the shipped product	~31	Same — consent requested below
v1 community lines in non-product files (CI workflows, setup scripts, issue templates, Code of Conduct)	~260	De minimis config edits; the CoC is the Contributor Covenant (CC BY 4.0)
Community PRs merged after the license change	—	Submitted under the repo's FSL license (inbound = outbound)

The ask. The following contributors have code merged while the repo was AGPL that survives in main today. Since we never had a CLA, that code's copyright is yours, and I'd like your permission to keep distributing it under the new license:

Contributor	Surviving lines	Main areas
@slvnlrt	~1,540	volume fs / ReFS, file transfer & delete protocols, device domain, Windows fixes
@gedeondoescode	~1,220	mobile pairing panel & client, job executor/manager, xtask
@StarbirdTech	~160	build config, asset types, whitepaper formatting
@SinanGncgl	~100	Dropbox OAuth configuration
@Yukeey07	~34	volume fs (NTFS/ReFS), CLI update
@julianbraha	~31	EXIF flash decoding (v1, carried into crates/media-metadata)
@okunamayanad, @Nebhay, @nicofishman	≤13 each	setup/config fixes

If you agree, please reply to this issue with:

I agree to relicense all of my past contributions to spacedriveapp/spacedrive under the FSL-1.1-ALv2 license, and grant Spacedrive Technology Inc. the right to distribute them under it.

A plain reply from your GitHub account is exactly the record needed — no forms, no paperwork. No pressure either way: if you'd rather not, say so (or say nothing) and I'll rewrite the relevant code instead. Either outcome is completely fine and changes nothing about how much I appreciate what you've built with us.

• @slvnlrt
• @gedeondoescode
• @StarbirdTech
• @SinanGncgl
• @Yukeey07
• @julianbraha
• @okunamayanad
• @Nebhay
• @nicofishman

Once everyone has responded (or their code has been rewritten), I'll link the outcome from #3089 and lock this issue. We're also adding a DCO to CONTRIBUTING.md so contribution provenance is explicit at PR time going forward.