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.
 * Discuss MapBuilder's readiness for graduation (possibly vote on graduating?)
 * 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:
 * 6) Open: Issue created by someone referencing document and version
 * 7) Open: Comments added to issue
 * 8) Fixed: Rough concensus has produced suggested replacement text
 * 9) Approved: Owner committee has voted and approved change
 * 10) Closed: Change has been incorpored in new version of document

To minimise overhead, the committee would probably approve a number of issues at once.