Opensource

5971 readers

221 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

Credits

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

⠀

founded 2 years ago

MODERATORS

pylapp@programming.dev

Cal.com goes closed source “because of security” (cal.com)

submitted 9 hours ago by pylapp@programming.dev to c/opensource@programming.dev

5 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Kissaki@programming.dev 5 points 8 hours ago* (last edited 8 hours ago)

~~Open core, closed extensions.~~ Not really clear how that significantly improves the situation. I doubt they'll diverge the two code bases(?).

The vault symbolism is pretty bad. A software product is much different to a vault, and a sister-vault-product you publish the blueprint for anyway.

At the same time, we still care deeply about open source. That’s why we are releasing a version of our codebase to the community under the MIT license as Cal.diy.

While our production codebase has significantly diverged, including major rewrites of core systems like authentication and data handling, we want to ensure there is still a truly open version available for developers, hobbyists, and anyone who wants to explore and experiment.

Huh? I don't get it. So the open product is an older, worse/different version/codebase? And they can do that without impacting their product risk because it's different?