Document practices around meetings

[nottrobin]

Document practices around meetings, with some mention of philosophy. Are we for or against solving issues through meetings vs e.g. emails? Some ideas:

• Every meeting should have a description, including expected outcomes
• Every meeting should have meeting notes, emailed round of published in https://github.com/ubuntudesign/meeting-notes/issues
• Before starting a one-off meeting consider whether it's still needed - feel free to cancel the meeting if it's not needed (don't skip regular process meetings - demos, retros, dev catch-up etc.)
• Feel free to shake it up and leave the office for a meeting =)