Closed
Bug 657004
Opened 13 years ago
Closed 9 years ago
Archive or migrate Xforms pages on www.mozilla.org
Categories
(Developer Documentation Graveyard :: HTML, defect, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: davidwboswell, Assigned: teoli)
References
()
Details
(Whiteboard: u=webdev p=0 c=HTML)
The Xforms pages on www.mozilla.org are out of date and should either be migrated to MDN (where there are already Xforms pages) or archived so that people understand this information is not current. I recommend redirecting the main Xforms main page to the Xforms page on MDN and then archiving the rest of the files so people will see a note about this content being out of date. Archiving legacy content is also now a requirement for being able to move forward with the mozilla.org/.com merge, so I'll go ahead and archive things soon unless I hear any objections.
Reporter | ||
Comment 1•13 years ago
|
||
/projects/xforms directory archived and redirect for main XForms page to the Xforms page on MDN set up in r88928.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 2•13 years ago
|
||
(In reply to comment #0) > The Xforms pages on www.mozilla.org are out of date and should either be > migrated to MDN (where there are already Xforms pages) or archived so that > people understand this information is not current. Why? Wouldn't it make more sense to actually fix the parts which are outdated.
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to comment #2) > > The Xforms pages on www.mozilla.org are out of date and should either be > > migrated to MDN (where there are already Xforms pages) or archived so that > > people understand this information is not current. > Why? As mentioned in the original comment, people come across out of date content and assume it is current and it causes confusion. Leaving pages that haven't been touched in years also makes it difficult to modernize the site (we had to touch 1000s of pages in the last redesign). Leaving these pages in place also makes it more difficult to get them current again -- pages on MDN and the wiki are much easier for people to update. The process for updating www.mozilla.org is also going to get more difficult when the www.mozilla.org and www.mozilla.com merge is completed. > Wouldn't it make more sense to actually fix the parts which are outdated. Yes. I would recommend updating those pages either on MDN or the wiki. I'm happy to set up redirects for previous URLs for any pages you move to new locations. All of the old content is also still available in the SVN repository as well as on the archived version of the site at http://www-archive.mozilla.org/projects/xforms/
Comment 4•13 years ago
|
||
Two pices of content are especially valuable here: the compat table (http://www-archive.mozilla.org/projects/xforms/status-detail.html, it's generated by a script) and the demo forms (http://www-archive.mozilla.org/projects/xforms/samples.html). I guess the script approach is not possible on the wiki and we need to hand-edit it all? Also, it is possible on the wiki to somehow integrate the demo forms?
Reporter | ||
Comment 5•13 years ago
|
||
(In reply to comment #4) > Two pices of content are especially valuable here: the compat table > (http://www-archive.mozilla.org/projects/xforms/status-detail.html, it's > generated by a script) and the demo forms > (http://www-archive.mozilla.org/projects/xforms/samples.html). I guess the > script approach is not possible on the wiki and we need to hand-edit it all? In the short-term we can move things back to www.mozilla.org if it isn't possible to easily move something to the wiki. Longer term though, www.mozilla.org isn't for hosting documentation in general and hosting scripts is problematic because of security reasons. > Also, it is possible on the wiki to somehow integrate the demo forms? I'll let Sheppy answer this question about the wiki on MDN.
Comment 6•13 years ago
|
||
(In reply to comment #5) > (In reply to comment #4) > > Two pices of content are especially valuable here: the compat table > > (http://www-archive.mozilla.org/projects/xforms/status-detail.html, it's > > generated by a script) and the demo forms > > (http://www-archive.mozilla.org/projects/xforms/samples.html). I guess the > > script approach is not possible on the wiki and we need to hand-edit it all? > > In the short-term we can move things back to www.mozilla.org if it isn't > possible to easily move something to the wiki. Longer term though, > www.mozilla.org isn't for hosting documentation in general and hosting > scripts is problematic because of security reasons. It was only script-generated, not a live script, so no security issue here. Anyway, I think we can move the table into a wiki document if it needs to be that way. I'll do that if nobody objects. Olli, Aaron, Alex, is that ok? > > Also, it is possible on the wiki to somehow integrate the demo forms? > > I'll let Sheppy answer this question about the wiki on MDN. That would be great to know, until then linking them to www-archive should be sufficient. The content stays there, right? It's not planned to delete the stuff there after some time as well?
> It was only script-generated, not a live script, so no security issue here.
> Anyway, I think we can move the table into a wiki document if it needs to be
> that way. I'll do that if nobody objects. Olli, Aaron, Alex, is that ok?
>
Works for me.
Reporter | ||
Comment 8•13 years ago
|
||
> It was only script-generated, not a live script, so no security issue here. > Anyway, I think we can move the table into a wiki document if it needs to be > that way. I'll do that if nobody objects. Olli, Aaron, Alex, is that ok? Great, glad to hear there's a way to move this into a wiki. > That would be great to know, until then linking them to www-archive should > be sufficient. The content stays there, right? It's not planned to delete > the stuff there after some time as well? No, the www-archive.mozilla.org site is intended just to sit there. The only reason something would be removed is if there was a security concern that wasn't able to be addressed by updating the page (which has happened just once since the archive was set up). For getting Sheppy's feedback, it may make sense to move this bug into the MDN product if that's where you would move the content. I think it's easy for doc bugs to get missed in other Bugzilla components.
Comment 9•13 years ago
|
||
Yes, that's the way to go. Move it to the MDN component.
Reporter | ||
Updated•13 years ago
|
Component: www.mozilla.org → Documentation Requests
Product: Websites → Mozilla Developer Network
QA Contact: www-mozilla-org → doc-request
Reporter | ||
Comment 10•13 years ago
|
||
Moved and reopened.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•12 years ago
|
Component: Documentation Requests → Documentation
Updated•12 years ago
|
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Comment 11•11 years ago
|
||
For historic purposes, this should be done, but it's worth noting that xforms is dead.
Priority: -- → P5
Whiteboard: u=webdev p=0
Updated•11 years ago
|
Assignee: nobody → jypenator
Component: General → HTML
Whiteboard: u=webdev p=0 → u=webdev p=0 c=HTML
Comment 12•11 years ago
|
||
This appears to block mozilla.org migration work. Jennifer might be able to say more about this content in light of comment 11.
Assignee | ||
Comment 13•9 years ago
|
||
We don't work anymore about XForms in MDN (lack of resources)
Status: REOPENED → RESOLVED
Closed: 13 years ago → 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•