Ideas for OGC Leadership Meeting 25 July 2013
Agenda
Meeting Objectives
Shared Leadership Approach
Twiki
New Table Format
Proposed Layout Simplification
Issues Collection to Recommendations process
Validation
Any Other Business (AOB
Shared Leadership Approach
see attached meeting pdf.
(10 min) Discuss the Twiki
Discuss recent changes
- Decide if the new table can be our working reference.
Discuss simplification proposal
- Decide who the twiki audiences are (us, those following the process, those leaving comments, those trying to understand our report).
- Decide how best to serve those audiences.
- Adopt or reject the WebHomeNew design.
Discuss the location of the minutes/recordings of past meetings.
- check that they are still on the todo list.
(30 min) Make work plans
We need to decide on current work and our plans for the next steps. We need to answer:
- how much more ideas collection are we going to do? (5 min)
- how do we review the ideas collected? (15min)
- when do we classify? (5 min)
- What will our next steps be? (5min)
The collection of ideas is well underway. We could simply leave the wiki open and collect new ideas only in the remaining teleconference (July 31st) or we could undertake new outreach to new groups, or even set up a permanent avenue for feedaback. The latter is probably better as a recommendation for the report.
To review the ideas, we need to find an efficient system. Given the discussion last week, it seems we all have somethingto say about the issues. However, starting the discussion on the phone is very slow. Therefore, I suggest that we adopt a formal procedure for discussion.
For example, we could adopt a process where:
- we start the discussion of each issue on the twiki to collect the various points of view,
- we discuss the issue for ten minutes to develop our position on it,
- we delegate one of ourselves to write a new section on the twiki presenting our writeup,
- we review the writeup and adopt it or amend it.
In this view the writeup would express our understanding of the issue. It would:
- explain the issue, who is affected and the consequences of dealing with or ignoring the issue,
- present possible avenues of resolution of the issue,
- present the position of this group as either consensus towards one approach, partial consensus, or complete dissent.
If we adopt this process or something similar we could also choose which topics we will tackle next week. It would be best if we started with the simplest in order to work out our process before we get embroiled with complex discussions.
Also, we should review the previous twiki pages to ensure all the ideas they present have been integrated into the new table, and to go through emails and other sources of ideas to check wehave a complete list.
The classification of the issues keeps coming up. The twiki was started splitting up ideas into separate pages and assigning someone responsible for each. Trevor suggests in
his agenda, (see 4a.) that we pick 'buckets' for the ideas. It is my feeling that this should be done late in the process, when we have a good handle on each topic. Indeed, it occurs to me that we should add 'tags' to each idea rather than a hierarchical classification since the former allows us to dealwith issues that cut across whatever classification scheme we might adopt.
We need to agree when in our process this happens and what thepurpose is of classification (assign responsible parties, organize the report, other).
The next steps should be clear to all. Given that, following the agenda, we will have:
* agreed on how much more work we put into ideas collection,
- agreed on how to process each idea,
we will need to agree on what the next steps will be and how we will decide to start on those steps. This may merely be framing our discussion for our next teleconference but would at least get us all started on discussion.
Any Other Business
.
Attendance
Minutes
See attached
Recordings
See attached transcripts