[Incubator] Infrastructure Migration

[Jo Walsh]

dear Frank, incubators, your patience ongoingly is appreciated.
On Sun, Sep 24, 2006 at 12:28:10AM -0400, Frank Warmerdam wrote:
> 1) The tables don't address how we will manage DNS.  Will we aim to
>    preserve the large set of subdomains we have now?  Will we use some
>    sort of DNS front end?  Any idea if there are issues on DNS management
>    while we are transitioning?

Hobu suggested that DNS should be managed entirely by a third party,
OSGeo delegated people have web admin access to manage subdomains.
and I would agree with that completely. I definitely want to
rationalise the subdomain sprawl now existing but attempt to preserve
what is there. One small element I want to contribute to this is a
simple domain / URI audit tool of what OSGeo is now running and where
things get moved to. http://wiki.osgeo.org/index.php/URI_Migration_Map 
is an aging sketch of what I envisioned moving where. 

DNS is in Gary's name, Jason B was happy to become technical contact.
 
> 2) You show handling LDAP and DNS near the end of the transition
>    strategy.  It seems to me we will need some sort of DNS handling
>    mechanism pretty soon (perhaps just depend on CollabNet till later?)
>    Further, if we are serious about "single signon" it seems like we
>    should be handling LDAP before the services that depend on it (CMS,
>    bug tracker, svn).  Perhaps your LDAP item is when we migrate it to
>    OSL?

Nod, depending on CN until in a position to move the zone files.
Imagining some osgeostaging.org type domain to mirror the setup with.

> 3) Is the design/interaction development someone to work on Drupal addons
>    and so forth? Is the system administrator doing essentially everything
>    else?

I hope this would result in a generic design/layout plus CSS, UI
elements etc that can be reused across different OSGeo affiliated sites - 
for projects hosting themselves, for the wiki, for local chapters. 
It wouldnt be drupal focused though that provides an easy environment
to sketch things out in. 

Despite the fact that this plan includes a couple months sysadmin time 
(overkill) to work on setup, security, fiddly integration issues, that
wouldn't prevent anyone else who felt like mucking in from adding to
or working on any resulting toolset. Right? Or am i such a mug? 

> The plan looks promising, and I hope we can get it launched soon.

Thanks, Frank; regrets that this is coming down so close to the wire...

cheers,


jo