At this time, VCV uses the GNU General Public License v3.0 license for most of our published free/open-source projects. If, however, the Free Software Foundation releases a new GPL version in the future, say GPLv3.1 or GPLv4, software released under this license would be “incompatible” with VCV’s code. For example, a GPLv4 project might not be able to use VCV’s code, and VCV might not be able to use the GPLv4 project’s code, depending on whether the GPLv4 is more restrictive (>), more permissive (<), or neither (≠). The solution to this problem is for VCV to license software under “GPLv3 or later”, which gives the code multiple licenses to choose from, if for example someone needs to consider its code as licensed under GPLv4.
This has been requested by 5-6 Rack users in the past year, and I had a short conversation with Richard Stallman himself about license incompatibilities and the possibility of future GPL versions, so I plan to add the “or later” clause to all future releases of VCV’s GPLv3-licensed projects. I encourage all developers of GPLv3 plugins to consider adding the “or later” clause if you believe in this logic. If you do, see https://www.gnu.org/licenses/gpl-3.0.en.html#howto and remember to change the license identifier in
This is an extremely minor change right now, perhaps not even worth making an announcement about it, but it will be extremely important if a new GPL version is released.