Difference between revisions of "Infrastructure Working Group"
Jump to navigation
Jump to search
Wiki-JoWalsh (talk | contribs) m (→Documents) |
Wiki-JoWalsh (talk | contribs) |
||
| Line 31: | Line 31: | ||
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. | ||
| − | * Wiki works well for sketching out rough requirements | + | * Wiki works well for sketching out rough requirements and for planning stages |
* 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... | ||
Revision as of 12:49, 5 April 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
- Frank Warmerdam
- Jo Walsh
- Schuyler Erle
- Please add yourself
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.
- WebCom OSGeo Site Focus is a collection of site visitor use cases; when people come to the public front, what do they expect and need to find from OSGeo?
- Geodata Repository is an overview of what metadata / archiving / redistribution facilities people have discussed wanting to offer through OSGeo
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 and for planning stages
- 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...