I think product-izing open source projects is a long shot, but: I would go the SAAS route, the way WordPress.com does it. Self-serve DIY hosting and enterprise

I think product-izing open source projects is a long shot, but: I would go the SAAS route, the way WordPress.com does it. Self-serve DIY hosting and enterprise clients (the kind of stuff you'd have account managers for). There also is a recipe for a permissively licensed library, with a commercial front-end: spaCy, the NLP library [1], and prodi.gy, the front-end [2]. The spaCy devs are my favorite success story. A solid library, and using their know-how to create a value-added front-end on top of it. There is a lot in play when this happens. SaltStack is a superb configuration management system. But when I make tickets on GH to pressure them to make things more fluid for non-enterprise deployments, they don't get much traction. I can't help their bottom line, and their incentive to cater to enterprise clients takes them astray from the values that made it great: the masterless, solo quickstart [3] (this is strongly my own observation). By far the biggest usage of open source is going to be intermixing permissively licensed libraries and build tools in larger works. By the time you see a polished service or product, you may not be able to tell what it's built in, even though they stand on the shoulders of giants. PS4 and Switch is built on FreeBSD. [1] https://spacy.io/ https://spacy.io/ [2] https://prodi.gy/ https://prodi.gy/ [3] https://docs.saltstack.com/en/latest/topics/tutorials/quickstart.html https://docs.saltstack.com/en/latest/topics/tutorials/quicks...