IncCom Meeting7

Time

Proposed date: Monday August 7th.

Proposed time: 19:30 UTC - Fixed time around the world (3:30pm EST, 12:30am PST)

Proposed location: IRC channel #osgeo.

Agenda

• Approve minutes from IncCom Meeting6.
• Assign MapGuide mentor (Paul?)
• Discuss FDO as a subproject of MapGuide.
• Motion to update project status template with regard to committer responsibilities.
• Discuss items coming out of Sean's post.

1. it is implied that all 8 original projects will graduate
2. bug tracking
3. social health (processes institutionalised - in practice for 6 months)
4. user documentation
5. documented release cycle
6. marketing requirements

• formal process for updating oficial OSGeo docs

1. There should only be a limited set of Formal documents - the rest can remain in the current wiki format.
2. Formal documents should not editable (via a wiki or similar). This could mean exporting to PDF, HTML or maybe locking the wiki editors to one person.
3. The document should be given a version number, release date and owner. The owner will probably be one of the OSGeo committees. For the ProjectStatusTemplate, this would be the Incubator Committee.
4. People should be able to raise "issues" against the document (referencing the doc and version number). These issues could be captured in the document's wiki, or in a bug tracking system. I'd be inclined to track issues in a bug tracking system.
5. The workflow for a documentation issue would be as follows, though to minimise overhead, the committee would probably approve a number of issues at once.
   1. Open: Issue created by someone referencing document and version
   2. Open: Comments added to issue
   3. Fixed: Rough concensus has produced suggested replacement text
   4. Approved: Owner committee has voted and approved change
   5. Closed: Change has been incorpored in new version of document

• Discuss MapBuilder's readiness for graduation (possibly vote on graduating?)
• Documentation license, advice? (something that is delaying geotools)
• Procedure to assign code to OSGEO foundation

1. completed provience review
2. completed product reivew, see marketting requirements above
3. request approval from the OSGEO board, with included header, and sample release candidate showing complete product and documentation
4. based on positive response from board release is produced published