-
If someone has contributed to UNA in the past but can no longer do so, I don’t see how that would negatively impact UNA. Since UNA is open source, anyone is welcome to contribute. Writing a line of code today whether it's 10 or 100, whether for free or for payment does not create an obligation to continue contributing in the future. Open source contributions are voluntary.
I believe that if you are not satisfied with a product, you should be entitled to a refund within a reasonable period. In Europe, consumer protection laws typically allow for a 15-day return window, but the specific terms depend on the conditions under which the product was purchased. Every product comes with its own set of terms and conditions that outline the rights and obligations of both the seller and the buyer.
When it comes to ongoing support and updates, I firmly believe that such services should be provided for a fee. No one can be expected to work for free indefinitely. If a product has no future development, there will be no updates, and consequently, there will be no ongoing support. In such cases, if no updates have been sold or promised as part of the initial purchase, customers cannot demand free support or improvements.
A product that was designed to function with a specific version of an operating system, software, or platform will remain functional only under those specific conditions. As technology evolves, compatibility issues may arise, and unless there is a commitment from the developer to maintain and update the product, it cannot be expected to work seamlessly in perpetuity.
However, if the product is open-source, users have the flexibility to update it themselves. They can modify the code, contribute improvements, or hire another developer if the original creator is no longer available or unwilling to continue maintaining it. This is one of the key advantages of open-source software it allows for long-term adaptability and community-driven development.
If someone worked for you today, you can't force them to work tomorrow. Everyone has the option to quit. And you can hire someone else tomorrow.
REGARDING Old code that is no longer compatible with new versions still holds value and should remain available for sale, provided it is clearly marked as such. Since these codes are open source, they can always be updated, maintaining their relevance. As long as the data is available for purchase and properly labeled, I see no reason why it should no longer be sold.
-
Not true for modules bought
for payment does not create an obligation to continue contributing in the future. Open source contributions are voluntary.
-
If I sell you code that is compatible with the current version of UNA, I don't see why I should be obligated to provide a free update for a new version tomorrow. If I choose to sell an update, I will; if not, I won’t. If you agree to these terms, you are welcome to purchase it; if not, you are not obligated to. I provide you with open-source code today, and if you need an update in the future, you are free to hire someone else to make the necessary changes. Unless there is a contractual agreement to provide updates, you cannot demand them for free. As an example, all the products I've seen from UNA INC with updates typically require an annual subscription. If you don’t buy a subscription, you can’t expect to receive updates. If you receive a free update, that doesn't mean it's mandatory, it's just voluntary.
-
All software products sold with a subscription for updates are eligible to receive updates anywhere on the internet. If you do not purchase a subscription for updates, I see no reason why you should receive them. Therefore, a product sold without updates will, by definition, only receive voluntary updates. However I believe that any software developer should be honest and clearly outline in the sales contract whether the product will receive future updates, ensuring transparency and avoiding any confusion. Otherwise, some customers might consider it a scam.
-