-
-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #198 from srobo/committee_meeting
Add committee meeting details
- Loading branch information
Showing
1 changed file
with
46 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# All Committees Meeting | ||
|
||
Once a month all of the committees have a meeting. | ||
This is normally held on the second Tuesday of the month. | ||
|
||
## Purpose | ||
|
||
This meeting is to help ensure smooth communications between the separate teams, and also the trustees. | ||
|
||
It is not intended that this meeting becomes the sole means of communication between teams, but rather that it helps bring to light stuff that may affect other teams and provide a forum to catch and resolve these. | ||
|
||
## Who can attend | ||
|
||
There should be at least one member of each teams' committee at each meeting. | ||
There will also be at least one trustee in attendance. | ||
|
||
Other volunteers are welcome at the invite of their committee, if the committee decide they have something to add. | ||
|
||
## Agenda | ||
|
||
The rough agenda for the all-committees meeting is as follows; | ||
|
||
* Run through updates from each committee, including successes and challenges. | ||
* Review tasks raised in previous meetings | ||
* Talking points (AOB) | ||
|
||
The minutes will be opened up for edit approximately 1 week prior to the meeting. | ||
The team updates and any talking points should be filled in by 24 hours prior to the meeting. | ||
Committees should also take this opportunity to review and update any tasks they have outstanding. | ||
|
||
24 hours prior to the meeting, the minutes will be changed to read-only[^0]. | ||
Committees are encouraged to read the committee updates from other teams during this time, as this will make the meeting go much more smoothly. | ||
If a team has a talking point to add after this cut off they should raise it to the trustees, who will add it if appropriate and there is time for discussion. | ||
|
||
The trustees will review the talking points for suitability during this 24 hours. | ||
A topic will only be removed if it is deemed to not be appropriate for discussion by all committees (this has yet to happen). | ||
|
||
During the meeting any questions around the updates and the talking points will be discussed, and any resolutions added to the minutes. | ||
|
||
After the meeting the minutes will be moved to the [organisation folder](https://drive.google.com/drive/folders/11Lsb-ooNoWHnQTQ__WoBg3guNOxBtwtF), which is accessible by all volunteers. | ||
|
||
## Tasks | ||
|
||
Action items raised during the these meetings are tracked as GitHub [issues on the committee-tasks repository](https://github.com/srobo/committee-tasks/issues). | ||
|
||
[^0]: In early meetings the document was editable at all times, and more and more talking points kept getting added as the meeting went on. This resulted in a very long meeting, and going largely out of scope. |