3 ms·
Hashicorp, Gitlab, Bitwarden, Mattermost, Automatic (WordPress), Discourse, Canonical, Red Hat...how many should I name? I’m surprised this discussion even took
by dangus 6y ago
Hashicorp, Gitlab, Bitwarden, Mattermost, Automatic (WordPress), Discourse, Canonical, Red Hat...how many should I name? I’m surprised this discussion even took place.
I reaize that I’m reading into the title, I don’t have time to watch the whole thing. But I think the title is meant to provoke the kind of response I’m dishing out. Consider me provoked I guess.
- burntoutfire 6y agoCloudera as well.
- bdcravens 6y agoObviously your list isn't intended to be all-inclusive (that's kind of the point), but Sidekiq and Sentry are two of my favorites.
- ryukafalz 6y agoSentry isn't FOSS: https://blog.sentry.io/2019/11/06/relicensing-sentry https://blog.sentry.io/2019/11/06/relicensing-sentry
- uberman 6y agoSuccessful examples tend to be revenue models where what you pay for is support. While that does technically generate revenue (and potentially lots of it) it is not generally applicable to many open source projects particularly those not large enough or foundational enough to even raise the interest of paid corporate support. At the moment that would leave donations as the rev stream and I guess that might work for some. The other model that can work is one where you offer a basic open source product but then charge for a closed source "professional version". I guess, I wonder if that type of thing is is really open source in the end.
- ASalazarMX 6y agoZabbix too. As others have said, the proven business model is services (support, SaaS, certification, etc.), not the code per se. That said, it's harder to make services for open source games or office software.