Hacker News new | ask | show | jobs
by josephcsible 755 days ago
This is not open source, because this is in the license:

> Additional Information:

> If there is any conflict, the rules in this section are more important than the usual rules of the Apache License.

> - Without a special written agreement, you can't modify the paid features of SwiftWave.

> - Without a special written agreement, you can't share or sell another paid version of SwiftWave.

> - Also, if you change the free features of SwiftWave and want to redistribute, you have to share those changes for free and need to keep the changes open source.

1 comments

Moved to Apache 2.0 from the modified Apache 2.0 and removed the point of conflicts. Check the discussion for more details - https://github.com/orgs/swiftwave-org/discussions/680

The license was initially written after checking various existing solutions like this (you can check caprover's license)

We are changing it because,

- I just came to know, Apache doesn't allow the modification in the license. Although there are many popular projects which is using that. So, I thought initially, It may be allowed.

- I don't want to move to GPL/AGPL for a small restriction which is only on the paid features of Swiftwave (which even doesn't exist, I don't know if someday any paid features will come or not).

- If there will be any paid feature in future, that can be in a different variant than the open source one. (Same way like docker or HAProxy) So we can keep Swiftwave as Open Source in Apache 2.0 and keep all the features available for free.

That's perfect now. Thank you!
Thanks !