Difference between revisions of "Big Meeting Minutes"

From FreekiWiki
Jump to navigation Jump to search
m
 
m (save early and often!)
Line 1: Line 1:
 
{{RightTOC}}
 
{{RightTOC}}
 
When:  
 
When:  
<br>Place:
+
<br>Place: Free Geek Big Room
<br>Facilitator:  
+
<br>Facilitator: Richard
<br>Scribe:  
+
<br>Scribe: Laurel and Ebeth
<br>Minutes Checker:
+
<br>Attendance: Taken on a sheet
<br>Attendance:
+
<br>Agenda: [[Big Meeting#Meeting Agenda|Big meeting agenda]]
<br>Last meeting:
+
 
== COMMITMENTS ==
+
== Overview ==
:Copy these from the prior meeting's minutes. Owner of each commitment should report on status: Done, In Progress, Carryover, Hand Off, or Drop. For items not completed, see http://wiki.freegeek.org/index.php/Carryovers.
+
Frameworks for considering possible paths: dichotomies that can be used to describe Free Geek, attributes and trends. (See [[Big Meeting#Meeting Agenda|agenda]]) Presented by Richard.
* Name - commitment - status (discussion points if necessary)
+
 
* Name - commitment - status (discussion points if necessary)
+
== Reports ==
== REPORTS ==
+
=== Build, production and space usage: Matteo ===
:Reports from other working groups.
+
''See [[Production plan]]''
* State of the Onion                                                                                                                http://wiki.freegeek.org/index.php/State_of_the_Onion                                                                             
+
* programs will have to change in response to changes in hardware, may become less educational
* General Priorities                                                                                                                    http://wiki.freegeek.org/index.php/General_Priorities
+
* problems in space use have arisen because of the piecemeal development of the production programs
 +
*  
 +
 
 
== BUSINESS ==
 
== BUSINESS ==
 
=== TITLE: PRESENTERS NAME (NEW/OLD)===
 
=== TITLE: PRESENTERS NAME (NEW/OLD)===
* Link to relevint conversation.
+
* Link to relevant conversation.
 
*:(Summarize Presentation)
 
*:(Summarize Presentation)
* List Clarifing Questions
+
* List Clarifying Questions
 
** Question - Answer
 
** Question - Answer
 
* List Concerns
 
* List Concerns
Line 25: Line 27:
 
* Proposal:
 
* Proposal:
 
*: (final proposal)
 
*: (final proposal)
** Decition adopted (with Unresolved Concerns Listed - AKA Stand Asides) | Send to Committee (if creating a new committee list intrested people)
+
** Decision adopted (with Unresolved Concerns Listed - AKA Stand Asides) | Send to Committee (if creating a new committee list interested people)
  
 
== REMAINING COMMITMENTS ==
 
== REMAINING COMMITMENTS ==

Revision as of 19:47, 22 August 2007


When:
Place: Free Geek Big Room
Facilitator: Richard
Scribe: Laurel and Ebeth
Attendance: Taken on a sheet
Agenda: Big meeting agenda

Overview

Frameworks for considering possible paths: dichotomies that can be used to describe Free Geek, attributes and trends. (See agenda) Presented by Richard.

Reports

Build, production and space usage: Matteo

See Production plan

  • programs will have to change in response to changes in hardware, may become less educational
  • problems in space use have arisen because of the piecemeal development of the production programs

BUSINESS

TITLE: PRESENTERS NAME (NEW/OLD)

  • Link to relevant conversation.
    (Summarize Presentation)
  • List Clarifying Questions
    • Question - Answer
  • List Concerns
    • Concern - Questions Which Clarify the Concern
  • Proposal:
    (final proposal)
    • Decision adopted (with Unresolved Concerns Listed - AKA Stand Asides) | Send to Committee (if creating a new committee list interested people)

REMAINING COMMITMENTS

New commitments, and Carry-Overs copied from above.
  • Name - commitment - status (discussion points if necessary)
  • Name - commitment - status (discussion points if necessary)

Next Meeting

  • Facilitator:
  • Scribe:
  • Minutes Checker:
  • Reporters to other meetings?
  • Date and time:
  • Place:
  • List of unfinished business for the next meeting: