Hi folks,
One idea that achieved consensus here at WMF, but was never discussed publicly (that I'm aware of) is the idea that meetings should use the Google Calendar speedy meeting option.[1]
Since we didn't have a public discussion of this, it's technically not the standard for RFC review meetings. However, this led to the natural question "why not?"
So....why not? Is there any opposition to us ending RFC meetings 5-10 minutes early?
Rob
[1] http://getsolid.io/blog/enabling-speedy-meetings-google-calendar/
From the link: But there’s the alternative setting called “Speedy Meetings”, here’s what it does:
- Encourage meeting efficiency and get to your next meeting on time.
- 30 minute meetings end 5 minutes early, 1 hour and longer meetings end
10 minutes early.
Rob Lanphier wrote:
So....why not? Is there any opposition to us ending RFC meetings 5-10 minutes early?
Requests for comments used to be 30 minutes (two in an hour), but the trend lately seems to have shifted toward one per hour.
I would hope that most people aren't paying attention to the meeting time length. RFCs vary widely in scope and complexity, so I think it makes sense to hold a meeting (or multiple meetings) as often as is appropriate and necessary for the specific RFC. If you think a topic can be discussed in a time slot smaller than 60 minutes, schedule it for that.
This is to say, I can't imagine anyone cares what your Google Calendar settings are, but I do think people shouldn't let themselves or their thoughts be cut off by arbitrary time limits. The start and end to the "formal" discussion can be decided by the person operating that silly bot.
MZMcBride
Thoughts are always cut off by arbitrary time limits, currently that arbitrary time is 1 hour. I'm in favor of changing this to 50 minutes. This ensures participants can be involved in the entirety of the RFC discussion and not have to leave early due to another commitment that starts on the hour.
On Tue, Nov 24, 2015 at 6:08 PM, MZMcBride z@mzmcbride.com wrote:
From the link:
But there’s the alternative setting called “Speedy Meetings”, here’s what it does:
- Encourage meeting efficiency and get to your next meeting on time.
- 30 minute meetings end 5 minutes early, 1 hour and longer meetings end
10 minutes early.
Rob Lanphier wrote:
So....why not? Is there any opposition to us ending RFC meetings 5-10 minutes early?
Requests for comments used to be 30 minutes (two in an hour), but the trend lately seems to have shifted toward one per hour.
I would hope that most people aren't paying attention to the meeting time length. RFCs vary widely in scope and complexity, so I think it makes sense to hold a meeting (or multiple meetings) as often as is appropriate and necessary for the specific RFC. If you think a topic can be discussed in a time slot smaller than 60 minutes, schedule it for that.
This is to say, I can't imagine anyone cares what your Google Calendar settings are, but I do think people shouldn't let themselves or their thoughts be cut off by arbitrary time limits. The start and end to the "formal" discussion can be decided by the person operating that silly bot.
MZMcBride
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org