5 ms·

Addendum: wtf, this change (or a change that happened prior to the final dump from Kuma) appears to have lost almost the entirety of one of the articles I have

by lol768 6y ago

Addendum: wtf, this change (or a change that happened prior to the final dump from Kuma) appears to have lost almost the entirety of one of the articles I have contributed. Compare: https://web.archive.org/web/20200113175409/https://developer.mozilla.org/en-US/docs/Web/Security/Certificate_Transparency https://web.archive.org/web/20200113175409/https://developer... To: https://github.com/mdn/content/blob/main/files/en-us/web/security/certificate_transparency/index.html https://github.com/mdn/content/blob/main/files/en-us/web/sec... Where has all the content gone? And of course there's no history anymore due to how the content has been migrated.

roblabla 6y ago
https://github.com/mdn/content/blame/53ba7ccaf34f639208791a98171d80badfe0ff33/files/en-us/web/security/certificate_transparency/index.html https://github.com/mdn/content/blame/53ba7ccaf34f639208791a9... Isn't your entire article here? The history is there...
- lol768 6y ago
  All of the contributor names, edit descriptions etc have been lost. It's not history, it's just snapshots of content.
  - bawolff 6y ago
    What license is MDN under and who owns the copyright? Is this a license violation?
    - escattone 6y ago
      https://github.com/mdn/content/blob/main/LICENSE.md https://github.com/mdn/content/blob/main/LICENSE.md and the attributions for the English docs are in https://github.com/mdn/content/blob/main/files/en-us/_wikihistory.json https://github.com/mdn/content/blob/main/files/en-us/_wikihi...
  - peterbe 6y ago
    The database dump is coming. Busy week. Also, at the footer of every document is a link to `$0/contributors.txt`. Your attribution is there: https://developer.mozilla.org/en-US/docs/Web/Security/Certificate_Transparency/contributors.txt https://developer.mozilla.org/en-US/docs/Web/Security/Certif... There will be a record of every contributor who submitted a revision to the non-archived content in all locales.
- merb 6y ago
  well... I'm still not sure why the old content was scratched. I mean https://developer.mozilla.org/en-US/docs/Web/Security/Certificate_Transparency https://developer.mozilla.org/en-US/docs/Web/Security/Certif... wtf?! this looks like a placeholder.
oefrha 6y ago
Losing the entire history by starting with a dump is ridiculous. Authorship would be somewhat tricky (I suppose they could use username + email on file, but might run into issues where people don’t intend to make their email addresses public), but it’s not like it would be very hard to migrate the diff + message history to git. I guess they either don’t want to start the repo with a gazillion commits (actually that would be a good stress test for the system, but would make cloning harder for people who don’t know how to use --depth), or just don’t care? Btw: now you need to clone the entire repository and run a dev server just to edit and preview a single page (let’s not get into super involved ways to clone only part of a git repo). You can avoid cloning by editing with GitHub’s web editor, but you can’t preview that way.
- lol768 6y ago
  > I guess they either don’t want to start the repo with a gazillion commits They could've cut it down to e.g. the last n changes to a page if this was a concern. Honestly the whole migration feels like it has happened before things had been properly thought through. There are pages lying around with {{IncludeSubnav{"")}} directives in the text that don't render properly - and they put this into production.

by lol768 6y ago

roblabla 6y ago

https://github.com/mdn/content/blame/53ba7ccaf34f639208791a98171d80badfe0ff33/files/en-us/web/security/certificate_transparency/index.html https://github.com/mdn/content/blame/53ba7ccaf34f639208791a9... Isn't your entire article here? The history is there...

lol768 6y ago
All of the contributor names, edit descriptions etc have been lost. It's not history, it's just snapshots of content.
- bawolff 6y ago
  What license is MDN under and who owns the copyright? Is this a license violation?
  - escattone 6y ago
    https://github.com/mdn/content/blob/main/LICENSE.md https://github.com/mdn/content/blob/main/LICENSE.md and the attributions for the English docs are in https://github.com/mdn/content/blob/main/files/en-us/_wikihistory.json https://github.com/mdn/content/blob/main/files/en-us/_wikihi...
- peterbe 6y ago
  The database dump is coming. Busy week. Also, at the footer of every document is a link to `$0/contributors.txt`. Your attribution is there: https://developer.mozilla.org/en-US/docs/Web/Security/Certificate_Transparency/contributors.txt https://developer.mozilla.org/en-US/docs/Web/Security/Certif... There will be a record of every contributor who submitted a revision to the non-archived content in all locales.
merb 6y ago
well... I'm still not sure why the old content was scratched. I mean https://developer.mozilla.org/en-US/docs/Web/Security/Certificate_Transparency https://developer.mozilla.org/en-US/docs/Web/Security/Certif... wtf?! this looks like a placeholder.

oefrha 6y ago

Losing the entire history by starting with a dump is ridiculous. Authorship would be somewhat tricky (I suppose they could use username + email on file, but might run into issues where people don’t intend to make their email addresses public), but it’s not like it would be very hard to migrate the diff + message history to git. I guess they either don’t want to start the repo with a gazillion commits (actually that would be a good stress test for the system, but would make cloning harder for people who don’t know how to use --depth), or just don’t care? Btw: now you need to clone the entire repository and run a dev server just to edit and preview a single page (let’s not get into super involved ways to clone only part of a git repo). You can avoid cloning by editing with GitHub’s web editor, but you can’t preview that way.

lol768 6y ago
> I guess they either don’t want to start the repo with a gazillion commits They could've cut it down to e.g. the last n changes to a page if this was a concern. Honestly the whole migration feels like it has happened before things had been properly thought through. There are pages lying around with {{IncludeSubnav{"")}} directives in the text that don't render properly - and they put this into production.