-
Notifications
You must be signed in to change notification settings - Fork 144
Archive non-web event reference pages #874
Comments
Some of the Browser API stuff will still be useful, as the browser api is used in devtools/webextensions (see https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Chrome/API/Browser_API). But a bunch of that functionality was recently deleted, so we can probably get rid of some. I can investigate this. I reckon we can get rid of the rest of it. |
I would still argue against outright deletion of most of it. The "legacy" stuff is largely still actually there but is only used internally. That doesn't necessarily mean the content may not have some usefulness left in it, and there are still products on the market based on XULRunner and older versions of the Firefox runtime. And after reading recently about the growth of Firefox OS derived products in certain markets, I'm more uncertain than ever that deleting that content is a good idea. I think instead someone should try to reach out to reps of companies that use B2G in products and try to get them to take over the content and pull it to a new site. Then it will be time to delete it from MDN. If we aren't able to get someone to take the stuff on, I would say we at that point can look at removing it. |
I would encourage you to look at the pages that I've listed above. Many are of so little content and no real value that I doubt the usefulness of them to anyone. |
I would still prefer archiving them over straight up deleting them. |
The thing is that old legacy add-ons were just injected chrome code, so many if not all of the events listed here as "Legacy add-ons" may still be being used by chrome code. For example: https://searchfox.org/mozilla-central/search?q=AlertActive&case=false®exp=false&path=. I would love for MDN to remove the non-Web docs, since we don't properly maintain them, but the fact is that we still have docsets like XUL and XPCOM, and don't have concrete plans to archive or delete them. So it's not clear to me why events should be different. The easiest thing to do, which moves the event reference work forward while punting on all the decisions about non-Web docs, is:
|
I'm sad we're still maintaining non-web docs on MDN and aren't brave enough to finally get them off our site, but I also don't want to block this discussion on the event reference work, so I guess the decision here is to use the archive. Thanks for your feedback everyone. Changing the title accordingly. |
I have now moved all the events in the Misc category under https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Chrome/Events (en‑US locale only, as those events weren’t translated) |
I wonder if we should also get rid of any macros when archiving/moving these. |
I can do this as part of my work on this issue in the next sprint. |
Automatic de-macroification is blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1519582. |
XUL events moved to be subpages of https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/Events, as currently the rest of the XUL stuff is there. Yes, it's not archiving, but it'll make things easier and less confusing when we come to archive or do whatever with the rest of the XUL stuff |
Firefox OS event pages archived at https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Events; macro calls all removed. |
Browser API event pages all moved underneath https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Chrome/API/Browser_API, as these are still of limited use, although now Chrome-only. |
I've deleted all of the add-ons related Chrome code events, as these are related to events that are applicable to old add-ons systems that are no longer available. For the couple that are Chrome-related, but not add-on related, I've moved them to https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Chrome/Events. So that's it for this work. @Elchi3 , fancy giving this a quick review to see if it's OK? |
Thing is, all of those are chrome code related, so I don’t think they should’ve been outright deleted. |
We're lacking policies around deletion and archiving and everything not web related isn't supposed to be on MDN Web docs anyways, so these docs have no owner right now as far as I can tell. So, no policies and no owners make it hard to say what to do with these pages. They won't get any maintenance, so I'm not sure what is worse going forward: no docs or archived and potentially wrong docs. So far we've decided on a case by case basis. I don't know very much about chrome code or its events, so I'm not sure, and I also don't know who would know. I haven't seen interest in the docs at all from anyone. So, hard to review the deletion vs archiving, but generally this LGTM. |
The ones I deleted are definitely no use to anyone anymore. The others that I moved under the Chrome events page I can't be so sure about, so I've left them for now. Exactly, so I think we can delete these. If someone complains, we can always reinstate them. I think future plans need some kind of clear guidelines on deletion versus archiving, but I think this is a reasonable judgement call for these ones. There were no translations. I checked. |
This is a work item for #685
We need to archive the following 103 event pages (and their translations) as they are not about web platform events.
Chrome code related
Browser API related
Firefox OS related
XUL
Misc
@wbamberg and @chrisdavidmills, can you review this planned work and help deciding if we want to delete or archive the above event pages?
I'm leaning towards deleting most of this, but I know not everyone is a fan of that. We have no deletion policy still (cf. https://discourse.mozilla.org/t/410-gone-our-policy-for-deleting-documentation/30902)
The text was updated successfully, but these errors were encountered: