Migrate or remove code samples under /samples/ dir
Categories
(developer.mozilla.org Graveyard :: General, defect)
Tracking
(Not tracked)
People
(Reporter: fs, Unassigned)
References
Details
(Whiteboard: [specification][type:bug])
Attachments
(1 file)
35.44 KB,
text/plain
|
Details |
Reporter | ||
Comment 2•11 years ago
|
||
Comment 3•11 years ago
|
||
Reporter | ||
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
Reporter | ||
Comment 6•10 years ago
|
||
Comment 7•10 years ago
|
||
Comment 8•6 years ago
|
||
I think the slow-and-steady approach of the last five years has not been very successful, and it is time for a quicker solution.
My preference is to:
-
Publish a Github repo with these samples. I've started this as a private repo https://github.com/mozilla/mdn-legacy-files, when I thought we would bring the files under configuration management and might make changes. I think the large files should be added to the repo, and then it should be made public and moved to the https://github.com/mdn org, then archived to prevent further changes.
-
Stop serving files from /samples, /diagrams and /presentations (404)
-
Shut down the backing storage for these files, removing one more quirk of the MDN architecture.
This came up because I was asked if we could migrate mdn-legacy-files to a public repo. I'm against it because it would create a searchable index of the /samples folder, which may contain code that is dangerous to MDN or its users as long as they are being served from developer.mozilla.org. However, if MDN was no longer serving the files, I think an archived repo would be interesting for historical purposes, as well as a reference for migrating any broken samples to the live sample system or other current samples implementations.
Comment 9•5 years ago
|
||
Updated•5 years ago
|
Description
•