Closed Bug 550214 Opened 11 years ago Closed 11 years ago

Remove redundant SDK information from wiki


(Add-on SDK Graveyard :: General, defect)

Not set


(Not tracked)



(Reporter: avarma, Unassigned)



There are some pages on the wiki that are completely out-of-date and partially or completely superseded by the SDK documentation, e.g.:

This needs to be fixed, probably by just pointing the pages to the online SDK docs (see bug 548165) and removing all links that point to the pages.
Blocks: 549017
Depends on: 548165
The main wiki page should also be cleaned up some to not point to outdated information, among other things:
For reference, a list of all wiki pages starting with 'Labs/Jetpack' can be found here:

After talking to Myk, one way to fix this issue is to move all old prototype-specific pages to be under Labs/Jetpack/Prototype/, and have all up-to-date, non-SDK pages (such as the roadmap) still be at Labs/Jetpack/, and have all SDK-specific pages be at Labs/Jetpack/SDK/.

Thus most pages at Labs/Jetpack/Reboot/ will be moved to Labs/Jetpack/ or Labs/Jetpack/SDK/.

Old JEPs for the prototype would be moved to Labs/Jetpack/Prototype/.

And so forth.
My last comment is probably more apropos to bug 550341. All that's needed for this bug, blocking the 0.1 release, is to remove all redundant information that's duplicated in the SDK--i.e., make all relevant pages just point to the SDK docs here:
Done. I created a new template called "Jetpack/Moved_to_SDK" and put it at the top of all pages that contain redundant information; you can see the pages that embed the template here:
Closed: 11 years ago
Resolution: --- → FIXED
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
You need to log in before you can comment on or make changes to this bug.