Infrastructure Proposal

This is an effort of the Infrastructure Working Group to produce a definitive baseline spec for what online services the OSGeo Foundation, and the Foundation's projects, really need in order to be able to do their thing will full visibility, legitimacy and interconnectedness.

Critical Services

Code versioning / repository

Candidate: Subversion. Constraints: need to be able to import full version history from other SVN/CVS instances

Mailing lists

Candidates:Mailman,Sympa Constraints:

• Needs searchable, index-friendly web archives
• RSS feeds out very desirable
• Web forum integration quite desirable

Bug Tracker

Candidates: Trac, RT, Bugzilla

LDAP

Candidates: OpenLDAP

Centralise user management details. Used to store rights and permissions to distributed OSGeo systems, ideally also to SVN and bug tracker.

Web Publishing System

Candidates: Drupal/Civicspace, Plone/OpenPlans

Needed for the foundation website at minimum. Nice to be able to offer to projects which are unhappy with the solution they currently have (GRASS,MapGuide in particular) but not obligatory for all to use.

Other less project critical but still desirable services

Software stack demo site

See Software Stack for rough old notes on how this could be. Space at this for telascience - many components necessary for a shiny Geodata Repository

Geodata Repository

See Geodata Repository for outline - hosted at telascience

Please add more if you think of them... i'm sure i've forgotten some stuff

Community Tools

General suite of tools that would put OSGeo on top, adding value to membership and engaging members

• Survey/polling & voting tools
• User profiles
• Code snippit/example repository
• Project management app for planning release cycles and events