On 06/23/2012 10:26 AM, KP Kirchdoerfer wrote: > Hello Mike; > > Am 23.06.2012 19:00, schrieb Mike Noyes: >> On 06/23/2012 08:23 AM, KP Kirchdoerfer wrote: >>> Am 23.06.2012 16:45, schrieb Mike Noyes: >>>> On 06/23/2012 05:58 AM, Mike Noyes wrote: >>>>> Everyone, >>>>> I will migrate Mediawiki and use it to replace our aging website. >>>>> >>>>> Hosted apps retirement >>>>> *Hosted Apps will go offline permanently on September 1, 2012* >>>>> http://sourceforge.net/blog/hosted-apps-retirement >>>>> >>>>> Migrating MediaWiki from Hosted Apps to Project Web >>>>> http://sourceforge.net/p/forge/community-docs/Migrating%20MediaWiki%20from%20Hosted%20Apps/ >>>> >>>> Hosted Apps Retirement >>>> http://sourceforge.net/p/forge/community-docs/Hosted%20Apps%20Retirement/ >>>> MediaWiki In progress, on hold due to Project web limitation that >>>> prevents MediaWiki installs of versions 1.17 and later >>>> >>>> >>> >>> Mike, >>> can you explain a bit more? >>> >>> They'll close 'hosted apps', but migration is on hold?? >> >> KP, >> Correct. They won't close hosted apps until Sep 1 st. They're working on >> the fix for Mediawiki, so we shouldn't attempt migration yet. > > understood. > >>> How much are we affected? The wiki pages? >> >> MediaWiki and Trac. We may want to upgrade our project to Allura (SF 2) >> allowing track migration to Allura. Trac migration details are fuzzy at >> this time. The Allura wiki is integrated with SF it isn't feature >> compatible with Mediawiki, so I recommend we migrate Mediawiki to our SF >> project web. > > Ok; speaking for myself I get used to mediawiki for our documentation > and Trac in the last two years and dislike an interruption in the > workflow this time. The less time I'm spending to adopt myself to a new > infrastructure, the more is left to improve the project. > So please try to preserve as much as possible :)
KP, With this in mind, see comment below: >>> And any chance our old webpages won't be replaced by a wiki? IMHO a wiki >>> looks odd as entry point - it's serving well for the documentation though. >> >> This is possible. SF project web supports multiple mysql databases. >> >> I think the wiki is a better representation of our project at this time, >> and making it the default is advisable. Instead of me trying to generate >> the new website off SF, then migrate it to SF like I did last time, I'd >> like to work from the SF project web. This will allow creation of our >> new drupal? website on the SF project web by our development team, >> instead of a single member. > > So what are you're plans for the website? A transition period based on > mediawiki? Why not starting a drupal website ASAP instead of porting > current content to a wiki?? Tentative plan based on input: 1. Wait for SF to implement OpenID for project web. 2. Wait for SF to resolve Mediawiki issues on project web. 3. Migrate Mediawiki to project web. 4. Install Drupal on project web. 5. Migrate Trac to project web. 6. When community consensus is reached that the new Drupal install is sufficient for project website, remove phpWebSite from project web. Comments and/or suggestions welcome. -- Mike Noyes http://sourceforge.net/users/mhnoyes https://profiles.google.com/mhnoyes ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
