Difference between revisions of "Tools Spec"

From OSGeo
Jump to navigation Jump to search
(asf link)
m
Line 4: Line 4:
 
[[Project Infrastructure Migration]] fit together. Single sign-on to a lot of different services could be offered.  
 
[[Project Infrastructure Migration]] fit together. Single sign-on to a lot of different services could be offered.  
  
There are really two components of this, because OSGeo the Foundation needs one set of tools to communicate between and about itself; there is also an intention to provide hosted services that OSGeo projects and participants need but can't provide themsleves, wanting the benefit of a stable home.
+
There are really two components of this, because OSGeo the Foundation needs one set of tools to communicate between and about itself; there is also an intention to provide hosted services that OSGeo projects and participants need but can't provide themselves, wanting the benefit of a stable home.
 +
 
  
 
== Member ==  
 
== Member ==  
Line 24: Line 25:
 
* Has news/talk items to publish
 
* Has news/talk items to publish
 
* Has a public bug tracker
 
* Has a public bug tracker
 +
* Has document archiving facilities
 
* Has a collaboration space
 
* Has a collaboration space
 +
 +
== Committee ==
 +
 +
* Has all the properties of a project
 +
 +
== Local Chapter ==
 +
 +
* Has all the properties of a project
  
 
== Meeting ==
 
== Meeting ==
Line 48: Line 58:
  
 
The Apache Software Foundation has a project directory at http://projects.apache.org/ built by collecting models  from DOAP, 'Description of a Project' files that each project contributes.
 
The Apache Software Foundation has a project directory at http://projects.apache.org/ built by collecting models  from DOAP, 'Description of a Project' files that each project contributes.
 
== Notes ==
 
 
This is just a start and i hope to fill this out with actual data models and a bit more specifics about current possible solutions.
 

Revision as of 14:28, 9 June 2006

Why this document exists

This is an attempt to write a role-centered description of how the different software components that projects are using, described in Project Infrastructure Migration fit together. Single sign-on to a lot of different services could be offered.

There are really two components of this, because OSGeo the Foundation needs one set of tools to communicate between and about itself; there is also an intention to provide hosted services that OSGeo projects and participants need but can't provide themselves, wanting the benefit of a stable home.


Member

  • Can be a member of one or more committees or projects
  • Has group-based access to subversion
  • May have system access, ssh etc
  • Sends messages
  • Can be subscribed to mailing lists associated with projects
  • Has a location

Project

  • Has members
  • Has mailing list facilities
  • Has home pages
  • Has its own subdomain of osgeo.org
  • Has meetings
  • Has news/talk items to publish
  • Has a public bug tracker
  • Has document archiving facilities
  • Has a collaboration space

Committee

* Has all the properties of a project

Local Chapter

* Has all the properties of a project

Meeting

  • Has participants
  • Has logs, perhaps has minutes or a summary
  • Has a time and medium/place

Message

  • Has a lot of different recipients
  • Is connected to a project
  • Could have keywords

Data Set

  • Members may want to upload and create metadata about data sets as part of a project.
  • Data sets may have spatial metadata and be indexed and searched for that way

References

ASF Projects site

The Apache Software Foundation has a project directory at http://projects.apache.org/ built by collecting models from DOAP, 'Description of a Project' files that each project contributes.