The conversation

Business & incomeExperience excerpt · English

I came across this a few months ago when I was evaluating open source installer options for my own …

I came across this a few months ago when I was evaluating open source installer options for my own open source project. I have no issue with charging for binaries while the source is available under an OSI license, but this from the README rubbed me the wrong way: "To ensure the long-term sustainability of this project, use of the WiX Toolset requires an Open Source Maintenance Fee. While the source code is freely available under the terms of the LICENSE, all other aspects of the project--including opening or commenting on issues, participating in discussions and downloading releases--require adherence to the Maintenance Fee. In short, if you use this project to generate revenue, the Open Source Maintenance Fee is required." I'll give the benefit of the doubt and assume this is just a difficult concept to succinctly explain in a short paragraph. But that summary - that revenue-generating use requires payment - feels misleading to me. …

Original discussionOpen Source Maintenance Fee250 source comments · at import
5

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 5

Direct replies available in this import. Original-language excerpts.

MA

Isn't it just a clear statement that they aren't going to give commercial users support for free? I know you are saying it isn't clear, but your quote literally includes the statement "While the source code is freely available under the terms of the LICENSE".

Full original
TR

Start-ups and smaller companies that are extremely cash strapped are willing to take an opensource project, compile it themselves, turn it into deployment artifacts and manage that whole lifecycle. There is a threshold where paying someone to manage and certify the lifecycle of tools is more valuable than keeping it in house. This is pushing those enterprise customers that are just using and updating binary releases because they don't want to take on the compliance risks of first-party support to pay for official versions.

Full original
YS

I think they're trying to say that if you are talking to them on behalf or a revenue generating entity, then you better pay them to talk to them about the project. feels like a pay to interect iff one of the parties interacting is a profit making entity

Full original
RO

> I'll give the benefit of the doubt and assume this is just a difficult concept to succinctly explain in a short paragraph. It is challenging to describe the concept succinctly, especially as there are lots of varied expectations people have about how Open Source projects work. I'm definitely open to suggestions on how to improve the text.

Full original
CS

If you read the comments on the GitHub issue, the guys seems more than reasonable. My understanding is that they want you pay if you are making money. My guess if you are just a one-person show with a just-started product, they probably won't care much. Here is their sponsorship page: https://github.com/sponsors/wixtoolset

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.