Add meeting facillitation policy #238
Conversation
In an effort to distribute team leadership more we developed ideas on how to get others to run the meetings. This commit includes the policy born out of that discussion.
|
@ashleygwilliams @booyaa and @badboy here's the summary policy from today's meeting. Please poke at or correct anything if my understanding of what we talked about/action items for roles were/are incorrect |
| @@ -0,0 +1,27 @@ | |||
| # Meeting Facillitation | |||
There was a problem hiding this comment.
fwiw facilitation only has one "l" in it
| ### Facillitator | ||
|
|
||
| - On the Monday before a team meeting an agenda issue will be issued. | ||
| - This is done by copying the previous weeks agenda and removing unnecessary bits and then opening |
There was a problem hiding this comment.
we could also have a template which seems like the less complicated solution to me
There was a problem hiding this comment.
There was a problem hiding this comment.
Here's our own version https://github.com/rust-community/team/blob/master/ISSUE_TEMPLATE/meeting_agenda.md
| - On the Monday before a team meeting an agenda issue will be issued. | ||
| - This is done by copying the previous weeks agenda and removing unnecessary bits and then opening | ||
| up the issue | ||
| - The issue is then posted to IRC on #rust-community and mention all the team leads so they know |
There was a problem hiding this comment.
Mention that team leads should fill in their respective topics
| - Add estimates for time as the agenda is updated | ||
| - 10 minutes before the meeting ping everyone about it | ||
| - Post the agenda and participation sheet at the beginning of the meeting | ||
| - Run the meeting and sticking to the alloted time as much as possible |
| - 10 minutes before the meeting ping everyone about it | ||
| - Post the agenda and participation sheet at the beginning of the meeting | ||
| - Run the meeting and sticking to the alloted time as much as possible | ||
| - Review participation sheet to make sure everyone was listed and observers/guests have been maked |
There was a problem hiding this comment.
assuming it's supposed to say marked at the end?
|
|
||
| ### Facillitator | ||
|
|
||
| - On the Monday before a team meeting an agenda issue will be issued. |
There was a problem hiding this comment.
"issue will be issued" sounds so double. How about "an agenda issue should be created"
| ### Facillitator | ||
|
|
||
| - On the Monday before a team meeting an agenda issue will be issued. | ||
| - This is done by copying the previous weeks agenda and removing unnecessary bits and then opening |
There was a problem hiding this comment.
| - On the Monday before a team meeting an agenda issue will be issued. | ||
| - This is done by copying the previous weeks agenda and removing unnecessary bits and then opening | ||
| up the issue | ||
| - The issue is then posted to IRC on #rust-community and mention all the team leads so they know |
There was a problem hiding this comment.
Mention that team leads should fill in their respective topics
| - Run the meeting and sticking to the alloted time as much as possible | ||
| - Review participation sheet to make sure everyone was listed and observers/guests have been maked | ||
|
|
||
| ### Note Taker |
There was a problem hiding this comment.
Add an additional empty line after this
|
|
||
| ### Note Taker | ||
| - During the meeting keep track of what's discussed | ||
| - On the agenda issue summarize what was discussed in the meeting and key action items/take aways |
There was a problem hiding this comment.
Should we encourage opening specific action item issues directly?
|
Hi all sorry I had to go away for like two weeks so I'll take a look and address these |
In an effort to distribute team leadership more we developed ideas on
how to get others to run the meetings. This commit includes the policy
born out of that discussion.