Difference between revisions of "IncCom Meeting7"
Jump to navigation
Jump to search
(→Agenda) |
(→Agenda) |
||
| Line 14: | Line 14: | ||
* Discuss MapBuilder's readiness for graduation (possibly vote on graduating?) | * Discuss MapBuilder's readiness for graduation (possibly vote on graduating?) | ||
* Discuss items coming out of Sean's post. | * Discuss items coming out of Sean's post. | ||
| + | # it is implied that all 8 original projects will graduate | ||
| + | # bug tracking | ||
| + | # social health (processes institutionalised - in practice for 6 months) | ||
| + | # user documentation | ||
| + | # documented release cycle | ||
| + | # marketing requirements | ||
| + | * formal process for updating oficial OSGeo docs | ||
| + | # There should only be a limited set of Formal documents - the rest can remain in the current wiki format. | ||
| + | # 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. | ||
| + | # 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. | ||
| + | # 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. | ||
| + | # The workflow for a documentation issue would be: | ||
| + | ## Open: Issue created by someone referencing document and version | ||
| + | ## Open: Comments added to issue | ||
| + | ## Fixed: Rough concensus has produced suggested replacement text | ||
| + | ## Approved: Owner committee has voted and approved change | ||
| + | ## Closed: Change has been incorpored in new version of document | ||
| + | |||
| + | To minimise overhead, the committee would probably approve a number of | ||
| + | issues at once. | ||
Revision as of 03:33, 7 August 2006
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.
- it is implied that all 8 original projects will graduate
- bug tracking
- social health (processes institutionalised - in practice for 6 months)
- user documentation
- documented release cycle
- marketing requirements
- formal process for updating oficial OSGeo docs
- There should only be a limited set of Formal documents - the rest can remain in the current wiki format.
- 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.
- 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.
- 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.
- The workflow for a documentation issue would be:
- Open: Issue created by someone referencing document and version
- Open: Comments added to issue
- Fixed: Rough concensus has produced suggested replacement text
- Approved: Owner committee has voted and approved change
- Closed: Change has been incorpored in new version of document
To minimise overhead, the committee would probably approve a number of issues at once.