[tajen]

No, don't do that:

- supportedsource.org requires you to put your code under proprietary license, which is bad because it's not open-source (If someone wants to fix a bug in your software, they can't do it).

- It is absolutely possible to sell open-source software: https://www.gnu.org/philosophy/selling.html

- The drawback is, people can put your software for free on BitTorrent.

- But companies will pay you because they want the original, genuine copy. They don't want to risk getting an unofficial fork where someone might have introduced a keylogger, and a lot of engineers actually prefer to retribute authors for their software. They actually pay the service that someone has code-reviewed what was merged into the software they get.

- If that's not enough for you, you can put a lock in your code and distribute the binary packages for a price. Yes people can remove the lock, but most companies aren't willing to recompile or even look at the code, and they'll pay. Plus, those that are willing to recompile already have their hands dirty, so they're twice closer to submitting improvements to your code ;) which is the meaning of "open-source".

In conclusion, don't use supportedsource.org, and just sell the packaged copies of your software.

[JoshTriplett]

This is especially true with "app stores"; it's sufficiently difficult to get apps into the Apple and Android stores, and sufficiently common to have adware-laden variants, that people will pay for an official version linked from the main project site.

Also true on other platforms where people don't commonly have access to a compiler, such as Windows.