On Tue, Feb 21, 2012 at 05:59:58PM -0500, Kent A. Reed wrote: > Finally, perhaps you've already addressed this, but will it be possible > to leave "forwarding addresses" on the old sites, at least for a time, > so that people directed to us by mostly old links from external sites > will be able to find us?
I probably didn't address this, or didn't do so clearly. If we pursue a sourceforge renaming, then old links on sourceforge that refer to the old project name will stop working. If we leave the old sourceforge project, then links will continue referring to the same thing. Unfortunately, there is no uniform provision to say "look in a new location for the new stuff". So I don't see either of the options as being very good in terms of automatically sending people who use old URLs to current, relevant resources. It's a choice between breaking URLs right now, or leaving them "working" but stale until we request project deletion. On data migration: sourceforge actually seems to be pretty good at providing data for export (for project administrators). Chris Radek has investigated and found that the mailing list archives are available in mbox format, the subscriber lists are available as flat files, and the bug tracker information is available in an xml format. Specific to the mailing lists: Dreamhost says they support importing mailing list archives. This is via a support request, not automated via the web panel, so I haven't tested it. I believe gmane.org (the site I generally use when referring people to mailing list posts via the web) can import old posts when we open new groups to archive our new lists. I also suspect but can't promise that they will retain the historical posts at the same URLs as now. If we switch to dreamhost mailman, I anticipate that a html-format archive plus monthly "mbox" archives will be available through a web interface, probably to the public but maybe only to subscribers. This is a standard mailman feature. I personally keep full archives of the list on my home system. These archives could be used in case of loss of data by dreamhost. I'm not aware of an automated way to back up the roster of subscribers, but this can be done manually by list administrators. Specific to the bug tracker: There are indications that others have written sourceforge tracker xml to bugzilla importers, but we haven't yet investigated how well they actually work. If there's someone who is interested in pursuing this specific question, I don't think there's any reason that we couldn't furnish a copy of the xml export for that purpose. If we switch to dreamhost bugzilla, I anticipate that bug exports will be available in bugzilla's xml format, probably to the public but maybe only to bugzilla account holders. This is a standard bugzilla feature. In addition, I anticipate that a board member will regularly make backups of the contents of the bugzilla sql database that will be stored on a separate system, in case of data loss by dreamhost. This got a little bit wordy, so I hope that you're still with me and that this answered your questions. Jeff ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
