Add license
Marlamin opened this issue · comments
Turns out after all the time we haven't done this. Not sure how relevant it is for files like this (especially as we base stuff on Blizz names) but probably good to have still.
This would be a nice thing since I would like to use your great definitions for parsing db2 files. They are just more eye / user friendly.
What about
.github/workflows/
analytics/
definitions/
schlumpf/
- CC BY-SA 4.0 (-NC would be neat, but wowhead)
code/
exedumper/
- GPL 3.0 (to avoid wowhead being a wowhead, at least in spirit), or
- BSD-3-Clause (to keep it simple and permissive)
?
CC BY-SA 4.0 sounds good for defs, I don't really care to add a NC as SA would cover most worries.
For the code I don't really care, something like BSD-3 or something even more permissive would be fine in my books.
Also, might be worth mentioning that DBCD is MIT and I don't know what it means if we (re)license any of the DBDefsLib code (which would also affect https://github.com/wowdev/DBDefsLib).
I looked and didn’t see any licenses and still don’t, but MIT is also fine I guess. Main difference is that BSD-3/4 forbids them advertising wowhead with our names, something they probably.. won’t.
@Marlamin if you want to relicense DBCD from MIT to BSD you simply can ask your contributors :D
For me, i agree with everything that keeps it opensourcly and useable hehe :D
Would be BSD or any other suggested license compatible with GPLv2 or GPLv3 ?
We currently using DBCD inside WowPacketParser (if you want to relicense it)
https://github.com/TrinityCore/WowPacketParser#provided-third-party-libraries
https://github.com/TrinityCore/WowPacketParser/blob/master/COPYING
@Marlamin if you want to relicense DBCD from MIT to BSD you simply can ask your contributors :D
For me, i agree with everything that keeps it opensourcly and useable hehe :D
I don't want to deal with relicensing DBCD, just wanted to note it uses a library we're talking about possibly giving a license, which might have repercussions.