Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359754 - We need an archival strategy for EF-maintained websites
Summary: We need an archival strategy for EF-maintained websites
Status: RESOLVED WONTFIX
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Website (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: phoenix.ui CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 214277 341037 359749 359757
  Show dependency tree
 
Reported: 2011-10-03 15:13 EDT by Wayne Beaton CLA
Modified: 2011-10-24 22:07 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Beaton CLA 2011-10-03 15:13:04 EDT 
We've identified several websites that are maintained by the Eclipse Foundation (i.e. they are not part of projects) that need to be archived.

Should we set up a separate directory on the archive server (e.g. foundation/www) for Eclipse Foundation specific resources? Perhaps with a ZIP archive of each individual subsite?
Comment 1 Wayne Beaton CLA 2011-10-24 15:40:22 EDT 
Come to think of it... isn't it enough to just delete the files and let them live on in the repository's history?

Is there any point in inventing a new solution for this? I'm inclined to mark it as WONTFIX.
Comment 2 Denis Roy CLA 2011-10-24 15:42:02 EDT 
Agreed.
Comment 3 Wayne Beaton CLA 2011-10-24 22:07:02 EDT 
Okay. WONTFIX it is.