The NSPR documentation appears to be very old, but I don't know enough to be able to tell if it is obsolete. Nevertheless, it seems like something better suited for MDN, where it can be given the care it needs (if it needs it).
Copying the other NSPR owner and peer on this. It looks like the main NSPR page on www.mozilla.org hasn't been touched in over a year and a half. Are these NSPR project pages still being maintained on www.mozilla.org? If so, I recommend moving them to the existing NSPR section on MDN. It will be much easier to keep the pages up to date on the wiki. https://developer.mozilla.org/en/NSPR If the pages are no longer being maintained on www.mozilla.org, I recommend archiving them. In the move to the merged mozilla.org/.com site, we no longer want to host any unmaintained pages on the production site, but can move pages to an archived version of the site for historical reference. http://www-archive.mozilla.org/projects/nspr/.
The NSPR project pages are still being maintained on www.mozilla.org. I just made a change to http://www.mozilla.org/projects/nspr/reference/html/priofnc.html#19516 yesterday. Moving them to MDN is fine by me.
(In reply to comment #2) > Moving them to MDN is fine by me. Great. Moving bug to MDN product. Sheppy can you help migrate these pages and let me know when I can remove them and set up relevant redirects on www.mozilla.org?
Component: www.mozilla.org → Documentation Requests
Product: Websites → Mozilla Developer Network
QA Contact: www-mozilla-org → doc-request
Summary: Migrate NSPR content → Migrate NSPR content to MDN
closing this bug, as the migration is complete via https://developer.mozilla.org/en/NSPR we'll be setting up a 301 redirect for users still hitting mozilla.org via bug 725079
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Component: Documentation Requests → Documentation
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.