At the link below is the first draft of the Post-Open License. This is not yet the product of a qualified attorney, and you shouldn’t apply it to your own work yet. There isn’t context for this license yet, so some things won’t make sense: for example the license is administered by an entity called the “POST-OPEN ADMINISTRATION” and I haven’t figured out how to structure that organization so that people can trust it. There are probably also terms I can’t get away with legally, this awaits work with a lawyer.
Because the license attempts to handle very many problems that have arisen with Open Source licensing, it’s big. It’s approaching the size of AGPL3, which I guess is a metric for a relatively modern license, since AGPL3 is now 17 years old.
Send comments privately to bruce at perens dot com.
License Text
I'm intersted in what you can do with this (compared with the current open source licenses).
This interview has been posted before but I'm sharing it again as it gives an insight into Bruce's thoughts.
Nothing yet. It's a draft and the first one at that. It's not meant to be used for anything. It could be some time before anything comes of this, if anything does come of it.