Difference between revisions of "OSOpsNotes4Chairs"
| Line 2: | Line 2: | ||
Try to be at the meeting early, and start the meeting on time. Though give attendees ~5 mins to trickle in. | Try to be at the meeting early, and start the meeting on time. Though give attendees ~5 mins to trickle in. | ||
| + | |||
| + | #startmeeting operators_ops_tools_monitoring is the command to start the meeting. | ||
[http://jjasghar.github.io/blog/2015/11/18/characteristics-of-a-successful-chatroom-meeting/ These are some good policies to try to stick to.] | [http://jjasghar.github.io/blog/2015/11/18/characteristics-of-a-successful-chatroom-meeting/ These are some good policies to try to stick to.] | ||
Revision as of 19:02, 16 December 2015
Some notes to help chairs out.
Try to be at the meeting early, and start the meeting on time. Though give attendees ~5 mins to trickle in.
- startmeeting operators_ops_tools_monitoring is the command to start the meeting.
These are some good policies to try to stick to.
You should send out an email ideally the day before, if not the morning of, here's a copypasta for you.
Template
Hey everyone,
Here's your friendly reminder email that we have our OSOps meeting tomorrow, Wednesday at 1900 UTC in #openstack-meeting-4. The agenda is located here[1].
I hope to see you all there!
[1]: https://etherpad.openstack.org/p/osops-irc-meeting-20151216
