Interesting:
Docs is the result of a joint effort lead by the French 🇫🇷🥖(DINUM) and German 🇩🇪🥨 governments (ZenDiS). We are always looking for new public partners (we are currently onboarding the Netherlands 🇳🇱🧀). Feel free to reach out if you are interested in using or contributing to docs.
https://docs.numerique.gouv.fr/login/
#docs #opensource #eu #europe #france #germany #netherlands #collaboration #fosdem
Right. But you can’t do that in a live system like google docs. You can have a workflow to export copies, but the live doc is the one bigquery and linked docs utilize to function against your app. It’s actually a feature of the same tooling that makes using them like a database possible that causes it to not be versionable. So even if you export copies as you update it, you can’t move the system back to those copies without breaking other parts of the system.
Other systems for modeling data have better version control for running parallel versions of models if you need to recover how data had been constructed in an older state. It’s an incredibly bad idea to do this with Google docs at scale
Right. But you can’t do that in a live system like google docs. You can have a workflow to export copies, but the live doc is the one bigquery and linked docs utilize to function against your app. It’s actually a feature of the same tooling that makes using them like a database possible that causes it to not be versionable. So even if you export copies as you update it, you can’t move the system back to those copies without breaking other parts of the system.
Other systems for modeling data have better version control for running parallel versions of models if you need to recover how data had been constructed in an older state. It’s an incredibly bad idea to do this with Google docs at scale