-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete the Projects/NSS tree #8215
Conversation
Hi @beurdouche This removes the NSS files from MDN, as previously discussed in #2669. I hope this will be done this week. Have you got the documents published elsewhere yet? |
@sideshowbarker @hamishwillee Oh, with my comment here I was only thinking of closing #2669 since it was being tracked in bugzilla. I wasn't thinking of actually removing the NSS document tree yet. I don't think the NSS team is ready for this, in the sense that they've already hosted their docs somewhere else, or did they OK this? My most recent understanding, was that we'd given the NSS and DevTools teams extra time (past the original June 30th deadline) to re-host their docs before we remove them from MDN, so I'm thinking that we might have to revert this PR until then. (cc @Rumyra) |
Hi all, I started to migrate the NSS doc but we only have a very limited set of pages for now. Any time you can give us where we can keep rendering on MDN would be appreciated :) |
@hamishwillee Would you mind if I revert this? We'd like to give the NSS and DevTools teams more time before we remove their docs from MDN. I apologize for not realizing that this PR had already been merged when I made this comment. |
@hamishwillee Let's postpone this until the NSS team is ready. I'm going to revert this for now (so we don't lose the docs in tonight's build), and later, when the NSS team is ready, we can finally resolve this. Sorry for the hassle. |
This reverts commit b2effa6.
@escattone @beurdouche No worries at all. I'm not the "boss of MDN" and it is not my intent to make anyone's life harder. I also didn't expect this to merge quite so quickly. I should have put it in draft - apologies on that aspect to all concerned. That said:
Could you two create a tracking bug that has an owner for co-ordination and a clear roadmap for delivering the next few steps? |
This replaces #4681. The files are archived (and in github anyway, so not truly "lost"). The files are not redirected (there had been talk or redirecting to https://github.com/mdn/archived-content/tree/main/files/en-us/mozilla/developer_guide - but since that couldn't be done globally happy for it to happen as some kind of post process - see mdn/yari#3692
The PR was previously approved and planned for merging in June 30, 2021.
This completes #2669