Fork This Site
To "fork" a project is a term stemming from open source development. It has a slightly negative tone, because it's usually something you do as a last resort. If you're unhappy with how an open source project is going you can make your own fork, and maybe, it becomes more popular than the original. In this model of "forking" you now have two competing versions.
However, if you decide to fork this website, there is no downside. The reason is that the data isn't actually stored here. You are mostly copying this list of calendars and publishing it under your name, maybe with a different selection. You are making this project richer by showing your own version of it.
Then, Where is The Data Stored?
The calendar data resides wherever the creator of the calendar has decided it should be. That could mean Google Calendar, Nextcloud or perhaps it's generated from a website. That means, if the creator want something change or deleted, it's up to them. If they want to delete their data, it's also up to them.
How Do I Fork This Site?
To copy this website you need two things. A list of links to the calendars and a way to show them. The list of calendars you can get by pressing "Data" on the overview. A way to show this list you can get here: https://github.com/joelgalvez/calendarlist
You can also use this to show a bunch of calendars together for your own purposes. Perhaps something semi-public, like this example https://calendar.sandberg.nl
Why Would I Fork This Site?
Maybe you don't like waiting for approval of your calendar?
Maybe you have a better way to display calendars alltogether?
Maybe you want to make a selection of calendars with a different focus than what's displayed here?
Or maybe, you have a better, more decentralized model on how to distribute the list of calendars?