Closed Bug 725079 Opened 12 years ago Closed 11 years ago

[One Mozilla clean-up] Retire & 301 for NPSR Content on mozilla.org

Categories

(www.mozilla.org :: Pages & Content, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christine.brodigan, Assigned: sgarrity)

References

(Blocks 1 open bug, )

Details

(Whiteboard: r101552, b=trunk)

Steven,

In preparing for mozilla.org's migration to Bedrock, we're moving content around, and retiring it.

Can you set up a 301 for all NPSR content http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/projects/nspr/?sortdir=down

It has already been relocated to:

https://developer.mozilla.org/en/NSPR

Ping for details.
Once this redirect is in place, should the contents of /projects/mozilla.org/trunk/projects/nspr just be removed, or moved to http://www-archive.mozilla.org/ as David Boswell has been doing for some stuff?
(In reply to Steven Garrity from comment #1)
> Once this redirect is in place, should the contents of
> /projects/mozilla.org/trunk/projects/nspr just be removed, or moved to
> http://www-archive.mozilla.org/ as David Boswell has been doing for some
> stuff?

Steven, since everything has been moved to MDN, we should be covered on removing content entirely from trunk, and setting the redirect.

David, your thoughts?
Is a single redirect from all urls starting with /projects/nspr/ to https://developer.mozilla.org/en/NSPR sufficient, or should some of the sub-pages be redirected to particular sub-pages on MDN?
(In reply to Steven Garrity from comment #3)
> Is a single redirect from all urls starting with /projects/nspr/ to
> https://developer.mozilla.org/en/NSPR sufficient, 

Is sufficient, thanks for helping clean this up Steven.
Redirect is setup in trunk in r101552. I'll wait to remove the pages, since that will happen instantly given that they are in the .org repo.
Keywords: qawanted
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: r101552, b=trunk
(In reply to mcbmoz from comment #2)
> David, your thoughts?

CC'ing NPSR module owners and peers for input.
I don't think the full API reference here:
http://www.mozilla.org/projects/nspr/reference/html/index.html
has made its way into MDN:
https://developer.mozilla.org/en/NSPR_API_Reference

which is unfortunate. I'd hate to lose access to that, we should figure out how to fix that.
Adding Luke Crouch & Sheppy:

We're a few weeks away from moving mozilla.org, and need to retire old content. Ted makes a request in comment 7 to  have 

http://www.mozilla.org/projects/nspr/reference/html/index.html moved to
 
https://developer.mozilla.org/en/NSPR_API_Reference

Are either of you able to move this for him?

Thanks for helping out :-)
This is already at least partially migrated. See:

https://developer.mozilla.org/en/NSPR_API_Reference

Anyone want to figure out what's missing and get it moved?
yeah, it's a wiki, and we always love having new contributors to MDN! ;)
Should this delay our retire/redirect of the page, or is it sufficient to let anyone finishing the content porting work from the SVN archive?

The page in question will still be accessible here even after it is removed from the website: http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/projects/nspr/reference/html/index.html?view=co&revision=48936&content-type=text%2Fplain
I don't see anyone stepping up to the plate to make it happen, so I would say don't let it block the migration. I don't know if Wan-Teh feels differently.
Target Milestone: 1.6 → 1.7
There are a couple of other bugs I currently know of regarding 404s in the npsr directory
https://bugzilla.mozilla.org/show_bug.cgi?id=773244
https://bugzilla.mozilla.org/show_bug.cgi?id=456437

At first, I thought it would be better not to address those, because of this bug. However, this bug seems to have stalled. Is this bug waiting for someone or some action?
It's been two weeks and no-one has answered comment 14. Is this bug waiting for someone or some action?
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
/projects/nspr/ is gone.
Status: NEW → RESOLVED
Closed: 11 years ago
Component: General → Pages & Content
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.