OSGeo Portal Site

From OSGeo
Revision as of 10:44, 15 August 2006 by Warmerdam (talk | contribs)
Jump to navigation Jump to search

This page is intended to document issues, policies and plans with regard to transitioning to the new Drupal based CMS as the OSGeo front end.

New Site

The site currently lives at:

 http://frot.org/osgeo/portal/

It is expected that we would point www.osgeo.org at this at some point when we are ready to transition.

General Plan

The general plan is to move from using the CollabNet "www.osgeo.org" project as the public web presence for OSGeo to using a Drupal based CMS. In the short term this will not affect other osgeo.org sub-domains such as those for projects (MapGuide, etc), nor for committee work which will remain the same. It is anticipated that other items hosted on the CollabNet infrastructure will eventually be transitioned to new homes though that is a longer term issue.

Issues

  • We need to port over content. Apparently this can mostly be done by pasting our existing content/* HTML files into Drupal, though various details need to be worked out and we need to pick a point at which we would stop updating the old web site and complete the transition.
  • We need to update the News Queue process for announcements on the Drupal site.
  • The www.osgeo.org web site
  • We need a mechanism for new users to join the web site and for this to update the LDAP backend database. Currently the drupal site is using the LDAP database in read-only fashion (as far as I know). This work might be integrated with the Membership Application project.
  • At transition we will need to broadly explain the issues with regard to distinct userids for the main web site (and all non-CN stuff), and the CN sub-sites like mapguide, and the committee websites.
  • What system will we be running the portal off? Perhaps an OSU Open Source Lab system? Or a Telascience system?

Policies

  • Should we try to retain the existing heirarchy as much as possible? ie. content/foundation/faq.html If the paths remain the same it will greatly reduce "link breakage" issues.