Relicensing

[3Shain]

I don't want to tell a story but MIT was a mistake.

The alternative I'm seeking is a dual-licensing model:

• LGPL-2.1-or-later : to be compatible with Wine and other OSS projects
• DXMT Game Porting License, some sketchy rules:
  • No modification other than compile-time/runtime configurations
  • No redistribution other than being along with a Game
  • No sub-licensing
  • Attribution and copyright notice

DXMT Game Porting License is basically a workaround for distributing LGPL code on Apple platforms. One technical challenge is the term Game: how is an application recognized as a game? Apparently any translation layers including Wine should be excluded from that.

Check list

• Add LGPL and distribute all new patches under LGPL, while keeping the old MIT license.
  • This step does not relicense, and we don't need to because previous code will stay MIT forever
• Figure out the detail of DXMT Game Porting License
• Introduce a Contributor License Agreement that grants project owner the right to relicense
• Ask relevant former contributors to sign on CLA

[Gcenx]

Probably also a good idea to not push any more code changes until the license change is complete.

[3Shain]

Now I have added a LGPL license but it's not really effective until new changes are made. I will gradually relicense my own work by adding a copyright header to changed source files.