On 06.04.2013 15:06, Michaël Michaud wrote: > Hi Ede, > > Do you mean we should let them migrate the project ?
yes. > I think we can undertake this migration just after 1.6 release. why bother. > Have we got a backup of the wiki ? I remember you did that, > but don't know where it is / how it works. yes.. in the sf.net files section. and on my private backups over the last 3 months. > What about the automatic build system for snapshots ? > Is it part of sourceforge services ? Where is it run from ? my private server. no problem there. > > Sorry for all these questions, I feel really a newby as regards > the administrative tasks, no worries.. appreciate you asking ;) ..ede > > Michaël > > PS : I've been told by one other sourceforge project admin > that the migration is quite easy, but I think they just had > a svn to migrate > > Michaël > >> ok, >> >> we now have a definitive deadline for sf.net changing us over to the new >> platform. here's what they wrote >> >>> We're going to start upgrading active projects starting on Monday, April >>> 22, starting with the longest-inactive and moving forward. Since each >>> upgrade takes a different amount of time, depending on the size of the >>> repositories, mailing list archives, and so on, we can't tell for sure when >>> we'll get to your project. >> i also asked some specifics and got the answers below. let's be prepared and >> see how our sf.net page and wiki come out afterwards. it reads like there'll >> be no significant losses, but who knows? >> >> ..ede >> >> >> -------- Original Message -------- >> Subject: Re: allura >> Date: Fri, 5 Apr 2013 17:03:07 -0400 >> From: Chris Tsai >> To: Edgar Soldin >> CC: communityt...@sourceforge.net >> >> >> >> I assume you're concerned about the "jump-pilot" project, as that's the only >> one I see associated with your account. >> >> This page shows some of the features of the new platform in general: >> https://sourceforge.net/create/ >> >> And the upgrade page itself also has detail on what will happen to the >> different tools: https://sourceforge.net/p/upgrade/ >> >> MediaWiki won't be affected by the upgrade, however, if you choose, we now >> have a script available to migrate Hosted Apps MediaWiki content into the >> Allura wiki system. This has yet to be used widely, but it is >> non-destructive if it doesn't work out, and you can continue to use the >> Hosted Apps MediaWiki until that system is retired. >> >> As for the specific tools on your project that will be affected, your ticket >> trackers <https://sourceforge.net/tracker/?group_id=118054>, forums >> <https://sourceforge.net/projects/jump-pilot/forums>, and svn code >> repository <http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/> will >> be upgraded to the corresponding tools on the new platform. >> >> The other tools will generally be left as is, though some of links in the >> navigation bar, and links to the admin pages will change. >> > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
