|
Top-level
 @mgorny use REUSE.software and SPDX headers and everything becomes larger than the GPL notice. Though, I went the other direction over time and I'm more likely to use MIT/0BSD than GPL simply because nothing I write make a difference to be copyleft-licensed, but it can make a difference to be permissive-licensed. 9 comments
@amszmidt @mgorny no, really no. There's nothing of anything I've released myself for which I would be annoyed if someone included in a proprietary software. This doesn't apply to everyone or to any projects, but mine are in that camp for sure. Trying to call up to emotions by saying "regret" makes you sound disrespectful.  @flameeyes @mgorny Maybe you will, I don't have a crystal ball .. but you make a similar argument I've heard over many decades where people regret that they picked a permissive license. @flameeyes @mgorny (and before you call someone disrespectful, maybe consider your own words first) @flameeyes @mgorny So much for respect I suppose ... I have plenty of more experience than you have on the topic, so have a *plonk*  Most of my code is GPL or AGPL and always has been. Though sometimes I will put out public domain works. One interesting counter example is templates. When I found out that one of the templates in inkscape was licensed GPL I had that sinking feeling that we'd just invited a few million people to copyright infringement because they sure as hell weren't going to know about the GPL. Had to get the original authors to PD their work since it was never their intent to lock users  @doctormo @flameeyes @mgorny Please use CC0 then. Public domain is a concept that does not work in larger parts of the world. @waldi I don't use Public Domain because I just can't (not in the USA! We don't have a working public domain here!) but for various reasons I don't have CC-0 either. I settled for 0BSD because to the best of my research is the least frowned upon of the options. |
Gregory's Server
@flameeyes @mgorny And when it makes a difference ... you might regret it.