Document GPLv3-to-MIT relicensing consent

[lipkau]

Context

JiraPS was originally distributed under GPL and moved from GPLv2 to GPLv3 in commit e1239bd6 on 20 August 2016.

Commit d4352777 changed the repository license from GPLv3 to MIT on 5 October 2017. The public repository record does not contain a relicensing proposal, contributor consent, a CLA, or a copyright assignment covering that change. A search of the project owner's available email history also found no explicit license consent. The historical Slack archive is unavailable.

This issue collects a durable public record. It does not allege wrongdoing and does not by itself change the repository license.

Consent statement

Each affected contributor may approve the MIT licensing of their own pre-change contributions by posting the following statement as a comment:

I confirm that I authored contributions to JiraPS before 5 October 2017. I agree that those contributions may also be distributed under the MIT License used by the JiraPS project.

A contributor may instead identify exclusions or request clarification about the commits attributed to them.

Contributor inventory and consent status

The current-code audit is recorded in this comment and PR #708. Duplicate commit identities have been consolidated where apparent.

Surviving attribution

• Joshua Taliaferro (replicaJunction)
• Oliver Lipkau
• Josh Knorr (jkknorr)
• Axel Gluth (axxelG)
• Michael Dejulia (Dejulia489)
• Liam Leane (LiamLeane)
• Eugene Bekker (ebekker)
• Neil Padgham (padgers)
• Brian Bunke (brianbunke)
• Joe Beaudry (beaudryj)

No surviving blame attribution

• Tomas Deceuninck
• ThePSAdmin
• kittholland

Required audit and resolution work

• Map each identity to the relevant pre-5-October-2017 commits.
• Determine which attributed code or documentation survives in the current branch.
• Contact contributors whose work still survives.
• Link every public consent comment or document any exclusions.
• Replace code lacking MIT permission, obtain permission, or restore GPL-compatible licensing for that scope.
• Commit the final evidence and conclusion to LICENSING.md.

Completion criteria

This issue can close only when every surviving GPL-era contribution is covered by explicit MIT permission, independently replaced, or distributed under a GPL-compatible scope. Repository ownership, collaborator access, later contributions, and silence after the change are not treated as relicensing consent.

Related: #705

[lipkau]

I confirm that I authored contributions to JiraPS before 5 October 2017. I agree that those contributions may also be distributed under the MIT License used by the JiraPS project.

[lipkau]

Current-code provenance audit completed

The current branch was audited with git blame --line-porcelain -C -C HEAD for every tracked file. Deleted work and lines attributed to later independent rewrites were excluded; copy/move detection was enabled.

The audit found 4,549 current lines in 177 files, attributed to 114 pre-MIT commits and 10 consolidated contributors.

Contributor	Current lines	Files	Commits
Oliver Lipkau	2,632	148	36
Joshua Taliaferro (@replicaJunction )	1,530	115	62
Liam Leane (@LiamLeane )	126	4	1
Josh Knorr (@jkknorr )	72	8	3
Eugene Bekker (@ebekker)	61	5	2
Joe Beaudry (@beaudryj )	56	4	4
Axel Gluth (@axxelG)	42	4	2
Neil Padgham (@padgers )	20	2	1
Michael Dejulia (@Dejulia489)	6	2	2
Brian Bunke (@brianbunke )	4	1	1

No current line was attributed to a pre-MIT commit by Tomas Deceuninck, ThePSAdmin, or kittholland. Joe Beaudry was missing from the preliminary inventory and must be included in consent tracking.

This is a blame-based provenance lower bound, not a legal conclusion: Git may miss heavily modified derivative work, and line counts do not measure copyright significance.

Evidence:

• Audit summary in LICENSING.md
• Exact file/line/author/commit mapping with direct commit links
• PR Document the JiraPS relicensing audit #708

Issue #706 remains the authoritative tracker for outreach, consent, exclusions, and replacement work.

[ebekker]

I confirm that I authored contributions to JiraPS before 5 October 2017. I agree that those contributions may also be distributed under the MIT License used by the JiraPS project.

[aaronsb]

Even though I am not on this list, I believe I authored code before 5 October, 2017, and I agree that any contributions I made may be distributed under the MIT license.