You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide your feedback for this topic, this is a very important question
Given that we are rewriting Vesta from scratch, we have the rare opportunity to change the project licensing. I am a defender of GPLv3, however I am open to other licenses with the following goals:
Keep VestaCP core product Open Source and free
Prevent competing forks from diluting resources (creating incentives for more people to contribute to Vesta)
Ensure that we get enough contributors OR we can fund paid developers
Maybe limit competition for a few years until the code becomes open again (like the BSL license allows, I think its a bad idea)
There are a few options for licensing, some licenses we looked at were:
Keeping GPLv3
AGPL 3.0 (my preferred option)
BSL 1.1
Functional Source License (FSL)
Something else?
I personally believe that AGPLv3 may be the best option as we keep the same level of permissions, but we plug the hole of network distribution in GPLv3 among other things. AGPL license is recommended by Free Software Foundation (FSF) if the software is commonly run on the cloud (which Vesta is).
Given that our monetization/funding strategy is via paid plugins, the core product should stay as open as possible. We will be able to sell plugins for managing paid hosting (similar to WHMCS) that will come with commercial licenses that allow you to make money from VestaCP as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Please provide your feedback for this topic, this is a very important question
Given that we are rewriting Vesta from scratch, we have the rare opportunity to change the project licensing. I am a defender of GPLv3, however I am open to other licenses with the following goals:
There are a few options for licensing, some licenses we looked at were:
I personally believe that AGPLv3 may be the best option as we keep the same level of permissions, but we plug the hole of network distribution in GPLv3 among other things. AGPL license is recommended by Free Software Foundation (FSF) if the software is commonly run on the cloud (which Vesta is).
Given that our monetization/funding strategy is via paid plugins, the core product should stay as open as possible. We will be able to sell plugins for managing paid hosting (similar to WHMCS) that will come with commercial licenses that allow you to make money from VestaCP as well.
What do you think about AGPL 3.0?
Beta Was this translation helpful? Give feedback.
All reactions