Cal.com closing source

[robi]

The dev said:

Open source is dead.

That’s not a statement we ever thought we’d make.

@calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up.

AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost.

In that world, transparency becomes exposure. Especially at scale.

After a lot of deliberation, we’ve made the decision to close the core @calcom codebase.

This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible.

We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple:

Protecting our customers and community at all costs.

This may not be the most popular call.

But we believe many companies will come to the same conclusion.

[andreasdueren]

Absolutely lame.

[jdaviescoates]

@robi yeah, it's not entirely dead given:

Starting today, Cal.com will relaunch all free and open-source code as Cal.diy under MIT License, widely considered the most liberal and popular open-source license. This new community edition is only for self-hosting and use at your own risk.

https://www.cal.diy/

That probably still meets my own needs. Perhaps a new package is needed for that?

Or perhaps we'll all migrate to @ekevu123's TymeSlot app?

https://tymeslot.app/
https://forum.cloudron.io/topic/15212/tymeslot-better-meeting-scheduling-than-cal.com

[robi]

@andreasdueren Clearly something happened to them or their customers.

Yet it was taken as defeat, instead of a chalenge to rise to.

[robi]

@jdaviescoates Indeed, seems they're not quite in the right frame of mind to avoid contradicting themselves.

Their emotions are in the open.

Long live Open Source.

[girish]

Have to see where this goes. Maybe they will have a change of mind. We will take a decision in some weeks to see what to do with the existing package.

[Lanhild]

@girish I would be surprised if they were to backtrack that move. The developers were always one step towards that direction, they simply used AI scanners as an excuse to close the code earlier (which was arguably pretty much already closed).

It's only a matter of time before the "new" https://github.com/calcom/cal.diy repo gets archived.

[sparkwise]

I noticed that they haven't issued a new release since March 1, where they were previously cutting releases every few days. Looks like they are still merging PRs into calcom:main, but unclear when that will turn into a new release. Any idea who is managing the release process for the repo?

[Lanhild]

@sparkwise According to their blog post, back in April, the maintainers are "former Cal.com interns".

Anyhow, it's been ~15 days since any commit was pushed, and all the commits since their announcement were almost exclusively changes to remove code from their "now" closed source version.

Not to be pessimistic, but I wouldn't expect a new release any time soon, if ever.

[Mathieu]

So, what's our best move now ?
I'm pretty stuck on the team problem. Can I install a previous version ? And do you know the version prior to the team gate ?
I've searched for good alternatives but I couldn't find anything with team capabilities and round-robin.

[jdaviescoates]

@Mathieu I don't think going to an old version would be wise - very likely to have security flaws (it was AI based attacks which led them to close their code).

I've not tried it at all yet (I'm just using the free hosted version of Cal.com as I don't need teams etc), but perhaps see if @ekevu123 could (or already has) add team functions to Tymeslot?