Difference between revisions of "Infrastructure Working Group"

From OSGeo
Jump to navigation Jump to search
(adding quick use case thoughts)
Line 23: Line 23:
 
== Use Cases ==
 
== Use Cases ==
  
=== [[Public Geospatial Data Committee]] use case ===
+
=== Non-software/operations Committee use case ===
  
 
The Geodata committee is the first attempt at moving forward on a non-software project Committee that isn't concerned with OSGeo internal operations, so we are figuring out a lot as we go along.  
 
The Geodata committee is the first attempt at moving forward on a non-software project Committee that isn't concerned with OSGeo internal operations, so we are figuring out a lot as we go along.  
Line 29: Line 29:
 
* Wiki works well for sketching out rough requirements - e.g. [[Geodata Repository]]
 
* Wiki works well for sketching out rough requirements - e.g. [[Geodata Repository]]
 
* Wiki doesn't work well as a shared editing environment for pages which are destined to go onto the "Official" site - e.g. [[Geodata Homepage Draft]]
 
* Wiki doesn't work well as a shared editing environment for pages which are destined to go onto the "Official" site - e.g. [[Geodata Homepage Draft]]
* We need some way to get multiple authors working on pages for the "official" site, without having to check them back into a live repository on subversion, or branch the pages and then re-merge them...  
+
* We need some way to get multiple authors working on pages for the "official" site, without having to check them back into a live repository on subversion, or branch the pages and then re-merge them...
  
 
 
 
== See Also ==
 
== See Also ==
  
 
* [[Incubation Committee]]  
 
* [[Incubation Committee]]  
 
* [[Web Committee]]
 
* [[Web Committee]]

Revision as of 23:34, 29 March 2006

This is a proposal for a Working Group to assess OSGeo's software infrastructure needs and provisions.

Focus

  • Assess the OSGeo community's needs for code management and collaboration tools, particularly collecting requirements and feedback from the Incubation Committee and Website Committee
  • Offer recommendations on future development directions to the Board

Participants

Meetings and discussions

  • When there's enough to chat about, suggest a chat session time (perhaps one that works well with the existing Website Committee timings?
  • If necessary, start a mailing list

Documents

  • Project Infrastructure Migration is a very comprehensive overview of what tools the individual software projects are using now, both to manage their codebase and their communications.

Use Cases

Non-software/operations Committee use case

The Geodata committee is the first attempt at moving forward on a non-software project Committee that isn't concerned with OSGeo internal operations, so we are figuring out a lot as we go along.

  • Wiki works well for sketching out rough requirements - e.g. Geodata Repository
  • Wiki doesn't work well as a shared editing environment for pages which are destined to go onto the "Official" site - e.g. Geodata Homepage Draft
  • We need some way to get multiple authors working on pages for the "official" site, without having to check them back into a live repository on subversion, or branch the pages and then re-merge them...

See Also