@allison @pernia @animeirl @mint

> depending on what you're trying to do

What you are trying to do and what ends up happening are not necessarily connected. Ten thousand projects kick off, maybe a hundred of them end up relevant to a niche, maybe one of them ends up relevant to a large number of programmers. Nobody can predict which ones take off, and licensing doesn't seem to affect it much.

If you're the sole author of the work and it starts off as GPL or AGPL, it's easy to say "All right, dual-licensing is now available" or release it into the public domain, but you can't go the other way, from BSD-licensing to dual-licensing under GPL and expect to be able to enforce the GPL: it will get forked. If it turns out not to matter, you can relicense, you can dump it into the public domain, whatever, no need to hang onto anything.

So it's prudent to just license under GPL or AGPL by default. You can always *start* permitting exploitation of something you've created, but you can't *stop* it once there's a release (i.e., a published work) that permits it.