6 ms·
Here’s the catch: when you give away something completely for free, people aren’t that motivated to pay for it. It's worse than that, people don't value it ver
by tonyedgecombe 7y ago
Here’s the catch: when you give away something completely for free, people aren’t that motivated to pay for it.
It's worse than that, people don't value it very highly if it's free.
- miguelrochefort 7y agoHow can we fix that?
- rapsey 7y agoYou want to fix human nature? Good luck.
- tannhaeuser 7y agoBy giving it away for free only for personal rather than commercial use, as lots of software used to be in the last millenium? But of course what's going to happen is a certain F/OSS advocacy org will shout "this isn't F/OSS as it doesn't obey our no-purpose-limitation criterion" and you and your software will be treated as a pariah and avoided like the plague and even more than pure closed-source software.
- pjc50 7y agoDefine "commercial use". It's not a clear bright line.
- tannhaeuser 7y agoWhen you're doing it for money. It's not difficult at all IMHO. Note that the new-fangled, earlier discussed licenses mongodb and others are using are targetting the case where your business is hosting sw for your customers (like cloud providers do); commercial use is ok when you self-host the software.
- jarfil 7y agoThat's why there are "non-free" repos. Not much of a problem, really.
- icebraining 7y agoFine, so you write a bunch of code, and release it under an NC license and a paid commercial license, no problem. Then someone comes along and submits a PR. What now? Will you accept their code and monetize it, despite the fact that you still deny that person the right to monetize your code, or will you refuse all PRs? The problem with these proposals is that it creates an unequal relationship; some developers have more rights just because they started the project, even if others have contributed significantly.
- jarfil 7y agoMore likely it discourages others from contributing significantly. The PRs requiring copyright assignment end up being minor fixes, and anyone willing to develop a bigger functionality will just start their own project.
- dspillett 7y agoI have a few things that I plan to release at some point. Small stuff, commercial use probably isn't a big issue, and I have no real plans for monetisation as this is hobby/interest stuff not the day job. My intent is to go for full-on AGPLv3 and not accept PRs initially. If someone sees a bug they can tell me "if these options are picked there is an infinite loop" or "you've missed input sanitisation here" and I'll put together a fix for it. That way all the code is mine, I have full control, and I don't have to worry about treading on someone else's toes if I relicense later. When/if I later decide upon a more permissive license, or to try monetise through commercial licensing, or if I chose another route entirely, then changing will be frictionless. In the meantime anyone wanting to work on it themselves because I'm too slow, they don't want to work my way, or "just because", are free to fork (assuming they are happy with AGPL), or contact me to negotiate other terms, or write something themselves from scratch to deal with the itch (again: these are not Big Things, I certainly don't expect to be releasing the NextBigThing™).
- ghaff 7y agoLeave aside the ideology of restricted use in open source. What's commercial use? Creative Commons has been messing around with this question for something like decade and has never come to a resolution. So, sure, advocate for changes to the open source definition if you like. But there are reasons that a lot of people are resistant.
- tannhaeuser 7y agoIdk what is so difficult about defining "commercial use". It is a concept even a child can understand. I acknowledge the goals others have for their licensing choices, and hold RMS in high esteem for his principled stance and achievements; I even release software under LGPL and other licenses. But I don't think OSI have an answer for the new software crisis where F/OSS developers are doing all the work, just to line the pockets of the three big cloud providers which obviously isn't sustainable. It also isn't in line with the ethics of eg the FSF to lock customers in to a walled garden built by F/OSS. In this sense, it's not me who brings up ideological arguments, but OSI who insist and hold-up their Open Source definition whenever someones dares to make a living with his/her work.
- ghaff 7y agoIt was, in fact, so difficult to define "commercial use" 10 years ago and nothing has changed, e.g. https://www.socialmediatoday.com/content/defining-non-commercial-and-trouble-creative-commons https://www.socialmediatoday.com/content/defining-non-commer... You can always release your software under the AGPL (which is an OSI-approved license)--which would effectively prohibit its use by cloud providers. Probably very few others will use it either but that's the tradeoff you make.
- tannhaeuser 7y agoCareful with AGPL. It has yet to stand in court, and is actually the license mongodb has left behind in favour of their own SSPL because it turned out not strong enough, and not preventing eg. AWS to sell mongodb as a sevice without releasing any of their provisioning and monitoring sw (though I'm not sure AWS actually uses mongo or, like Azure with CosmosDB, a proprietary API-compatible product instead). The amount of confusion regarding AGPL shows in eg. [1], and I've also heard the opinion it might not be enforcable because it wants to restrict third-party software. IANAL, but I wouldn't rely on AGPL, and not many people would use AGPL software anyway. [1]: https://softwareengineering.stackexchange.com/questions/107883/agpl-what-you-can-do-and-what-you-cant https://softwareengineering.stackexchange.com/questions/1078...
- Paraesthetic 7y agoSo we need to charge a nominal fee so that they other party thinks it has more value
- huffmsa 7y agoI was just thinking the other day, "If Wikipedia became a paid product, would I pay for it?" Really, what would happen if it became a for profit product? Would I pay for access to the greatest single repository of information the world has ever seen? Or would I shrug my shoulder and let Google tell me that I actually meant to query something else, and trust that the top placed link is really the best?
- skohan 7y agoHow would monetizing Wikipedia even work? That raise a lot of questions about fair compensation for the people creating content.
- huffmsa 7y agoIts a different line of discussion, but one which is being wrestled with all over the internet. How do you compensate content creators who are not your direct employees for producing content on your platform. See YouTube.
- tiborsaas 7y agoYou mean monetized for access to the content content like spotify? Most creators get peanuts, some get barely enough and some get a huge chunk. Wikipedia is already monetized, but not like most platforms: https://en.wikipedia.org/wiki/Wikimedia_Foundation#Finances https://en.wikipedia.org/wiki/Wikimedia_Foundation#Finances
- daurnimator 7y agoI (and most people) used to buy encyclopedias. If wikipedia didn't exist, I would again...
- flr03 7y agoI used to buy encyclopedias too, paper first and later on CD. But let's be honest here, there is no coming back from Wikipedia. The amount of informations on every single subject, the details, the fact that's its extremely dynamic (yes this new Usain Bolt world record is updated faster than than the actually record time), this is incomparable.
- shabda 7y agoIt is probably even worse, people assume that they get what they pay for, so some people won't even look at the free options. It is happening with me right now. I am searching for a Jekyll theme, and there are a bunch of free ones, but because time is money I will only try the paid ones.
- pjc50 7y agoBit of a bipolar market: in Android apps, hardly anyone pays upfront, so apps develop all sorts of weird post-hoc monetisation.
- TheRealSteel 7y agoMaybe Apple and Google need to give in and let us have free time-limited trials? Nobody wants to go back to the 90s software "You have 22 of 30 days remaining" popups every time you start an app, but is what we have now any better?
- cameronbrown 7y agoProblem is the long tail user retention story is incredibly bleak on mobile. It's considered an achievement to get them to last a week, never mind a month.
- pjc50 7y agoThat sounds like the "free trial" system working. Someone looking for an app for X purpose installs 10 of them and deletes all but one - giving very low average metrics.
- sidlls 7y agoIt's more like the "one" they keep is also free, and marginally less useful or slightly more irritating to use. Mobile app stores are a cesspool of terrible ideas and naive people who think if only they give away their time developing free software some company will notice and bless them with a job. The few gems to be found are a stark contrast.