Issue Details (XML | Word | Printable)

Key: ABOUT-157
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: sonyabarry
Reporter: RickieES
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Some info should be posted about plans (or lack of them) to migrate to

Created: 08/Oct/12 10:10 PM   Updated: 10/Oct/12 02:05 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Original Estimate: 2 hours
Original Estimate - 2 hours
Remaining Estimate: 2 hours
Remaining Estimate - 2 hours
Time Spent: Not Specified
Time Spent - Not Specified


Tags: kenai migration
Participants: RickieES and sonyabarry

 Description  « Hide is supposed to be superseded by the new infrastructure. Months ago, some comments were made about plans to provide tools to ease migration from to, but no other news have happened since then. There is some uncertainty about this, so it would be nice that a post were published in both and making clear these points:

1) Is there any schedule to shutdown

2) Is still receiving maintenance and/or operators time?

3) Is there any plan to migrate projects, especially the contents other than in SCM repositories (like wikis, blogs, forums, etc.)?

4) If the answer to 3) is No or there is no schedule for it, are there any hints to manually migrate the projects from to

In my case, I have a project in that currently uses just a Mercurial repo and the downloads section, but now I need to set up a wiki for docs. As migrating the wiki would be a manual task and I could have difficulties keeping track of the images to be migrated, I'd rather know if it is better to migrate to or stay at

RickieES added a comment - 08/Oct/12 10:49 PM

Just after creating this issue I have found this thread in forums:

I guess it answers some of the points outlined in the description:

1) No schedule yet. It seems that will be alive at least until 2014.

2) IIUC, yes, its stack is receiving updated at the same time does.

3) Not yet, and people won't be able to start seriously looking at it before, probably, 2014.

4) No hints for manual migration. Owners of projects based at are welcomed to migrate the content themselves to (or even to keep the sister projects in sync both in and

Still, I feel (and other participants in them mentioned forum thread too) that a post in with this information is much desired. Probably just copying and pasting the questions and answers in this issue with a "Q & A regarding migration to" title would be enough.