I think it's a good idea however I think there are a few things you might want to consider:
CloudStack.org<http://CloudStack.org> gets about 500,000 unique visits a month though that's also partially because of the content on the current pages e.g. forums, blog, videos, directory. etc. Also CloudStack.org<http://CloudStack.org> as it stands get's about 125,000 visits a month from organic search and tens of thousands of links to direct pages, you should 301 redirect the old to the new so all the search and hard link folks don't get 404'd. You'll need someone to map all the redirects and it's not trivial. Also If you break all those links traffic will drop pretty significantly IMHO until Google re-indexes and all the old content and then the number of people that would normally find out about CloudStack.org<http://CloudStack.org> through search wouldn't. Also the content on the incubator site is pretty good for the hard-hitting sysadmin or open source guys but new users might be a little intimidated. I think we should also answer the following questions: - What should we do with the old content is do you want to keep it or move it to something like CloudStackUsers.org<http://CloudStackUsers.org> or the like? - Apache Incubator doesn't have forums so do you abandon the forums? (There are over 11,000 registered forum users) - Do you want to have a blog, move it to a new place or give it up? - Should we still announce events and do sign-ups (we have thousands of historical sign-ups for Build a Cloud Days and user conferences and the capability to send invites to past attendees based on geography etc. baked into the site). - There are 30,000+ people signed up for a newsletter on CloudStack.org<http://CloudStack.org> when we donated the project to the ASF I stopped sending updates. Do you want to start doing that to help promote the project, migrate to some new system or some other option. My suggestion would be: - Alias a new community approved domain to the existing site eg CloudStackUsers.org<http://CloudStackUsers.org>. test it to make sure it works and nothing's hard-coded or broken. - Really make sure that the incubator site experience is good (my pet peeve is that there is no common navigation to get from bugs to docs to the main site) - Then point CloudStack.org<http://CloudStack.org> to the Incubator site - http://incubator.apache.org/cloudstack/ - Divide content for Apache CloudStack development to CloudStack.org<http://CloudStack.org> and really work on the user experience for developers and start migrating content systematically to Apache. - Come to consensus on what to do with the old content on CloudStack (i'll volunteer to keep it maintained and collaborate with whomever the PPMC wants to give access to is cool with me) until we decide. Thoughts, flames, etc.? Regards, Mark Mark R. Hinkle Senior Director, Cloud Computing Community Citrix Systems p: 919.228.8049 m: 919.522.3520 e: mark.hin...@citrix.com<mailto:mark.hin...@citrix.com> twitter: @mrhinkle On Oct 3, 2012, at 1:26 PM, Chip Childers <chip.child...@sungard.com<mailto:chip.child...@sungard.com>> wrote: All, I'd like to propose that Citrix (if willing) redirect cloudstack.org<http://cloudstack.org> to http://incubator.apache.org/cloudstack/ and docs.cloudstack.org<http://docs.cloudstack.org> to the appropriate sub-page of the ASF site. Specifically, I'd like to propose that this happens as fast as possible. The impact will be a simplified experience for users, once we get through our first official ASF release. I don't see any reason to wait... Any concerns? Can someone make this happen? -chip
