search

OpenTermsArchive / docs

User documentation website for Open Terms Archive
https://docs.opentermsarchive.org
Creative Commons Attribution Share Alike 4.0 International
1 stars 3 forks source link

Explain how to handle terminated services and how to rename services #96

Closed clementbiron closed 10 months ago

netlify[bot] commented 10 months ago

Deploy Preview for open-terms-archive-docs ready!

Name Link
Latest commit 5f3f1b8ea8eb8d8fd0d0ed4a01fcb7fb40704a0f
Latest deploy log https://app.netlify.com/sites/open-terms-archive-docs/deploys/655b59d114525000087387f1
Deploy Preview https://deploy-preview-96--open-terms-archive-docs.netlify.app/contributing-terms
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

MattiSG commented 10 months ago

Please notify https://github.com/OpenTermsArchive/contrib-declarations/pull/906 once merged!

MattiSG commented 9 months ago

Through discussion, we reached a conclusion that it was more relevant to leave it to the analysts / consumers to decide how to join data. It is rather trivial, at analysis stage, to fuse Twitter and X from the dataset: just merge the folders. However, if we use only one name, we make it hard to discover the data: will users expect X to contain historical 2011 data of Twitter? If we keep the original name, will it still make sense in 5 years when nobody remembers anymore that Make used to be called Integromat?

Now, there might be a case for adding metadata on renames. At this stage, we recommend doing in at commit level, by having a single commit with message “Rename Twitter to X” that contains both the termination of Twitter and the tracking of X.

This example is especially interesting since we observe that the transition of terms is very gradual: while one can pinpoint the official renaming date announcement, or the incorporated name change, it is impossible to pinpoint that transition in the terms as the renaming is applied apparently opportunistically, with terms still being rewritten in the last weeks, several months after the official name change.

The policy we described here is the current best practice, that does not mean it is final 🙂 We would happily consider improvements or complete changes if there are clear use cases and applicable proposals!