3 ms·

For us, FOSS is the start of the funnel for our SaaS. Somewhat in-between the "hosted version" and the "premium features" buckets, but in separate projects. We

For us, FOSS is the start of the funnel for our SaaS. Somewhat in-between the "hosted version" and the "premium features" buckets, but in separate projects. We employ the two core maintainers of Storybook (one of the most popular FOSS JavaScript projects) who work on it full-time. The rest of us build Chromatic, a SaaS that offers features on top of Storybook, and we occasionally work on Storybook too. Storybook is a tool for local development, so if a feature makes sense there, we add it to Storybook. If it needs some cloud connection/storage (e.g. for team collaboration), it becomes a Chromatic feature. We have a shared roadmap that doesn't prioritize one over the other, and Storybook has it's own steering committee.

Legogris 6y ago
Without having any knowledge of or experience with Storybook, that sounds like an optimal approach for such a project. I thin Hashicorp does something similar on top of slect core features (which tend to eventually end up on the free and open version eventually, which is funny because the enterprise customers end up being beta testers due to HC's habit of releasing features in a half-working state).