[TEAM] Vote on changes to the meeting structure

[Micah Gersten]

On October 16, 2015 3:13:21 PM CDT, Pasi Lallinaho <pasi at shimmerproject.org> wrote:
>Since the meetings have been far apart, and not many people have been 
>around, let's do the voting on the meeting structure changes on the 
>mailing list. Here's the proposal again for clarity:
>
>
>1) Stop running the "Team updates" section
>
>Pasting the updates in a meeting means more work (through having to 
>memorize/note down items) for contributors. It also means that those
>who 
>can't attend the meeting (which means many people per meeting), can't 
>paste the updates unless somebody does this for them.
>
>Since we now have a timeline tab [2] in the tracker, most of these 
>updates can be seen live.
>
>The only real change in action contributors would need to take would 
>apply to work items. Practically this means that everything that could 
>be worth mentioning for people outside the team - or added in the 
>release notes - should be in the blueprints. Doing the updates like
>this 
>also improves their findability. As I see it, this isn't much different
>
>from what we currently do, or at least what I try to do.
>
>Finally, the updates that aren't worth/important enough to add to the 
>blueprints could still be shared in the meeting, thus...
>
>2) Rename the "Announcements" section to "Updates and Announcements"
>
>This is just semantics, but it should be done to avoid confusion and be
>
>more accurate.
>
>
>Team members, cast your vote by sending +1, -1 or +/-0 on this list. If
>
>you wish to vote privately, you cand send a mail to Simon or me (you'll
>
>find the emails - or can ask on IRC).
>
>We'll have a week for the votes. The results are gathered and published
>
>after next Friday (or after 21UTC next Friday) when me and Simon crash 
>on IRC at the same time.
>

+1