From Fedora Project Wiki

Introduction

This is an Ambassadors SOP that describes how to Host a meeting on IRC in order to it becomes productive and a way to get people involved with Fedora.

Examples

You can see examples of past Meeting successfully run at FAmSCo meeting of January 22, 2011.

Instructions

Step 1 : Have a agenda

Important.png
Please remember!
Never spend the time of the people attending the meeting, always publish extensive information of the issues to discuss beforehand

Use the preferred communication tool of the project/group you are attending, if it has one yet.

In order to have an agenda you may use one of the following :

  1. Single wiki pages (e.g. FAmSCo uses FAmSCo_agenda in this wiki)
  2. Wiki pages per meeting (e.g. EMEA Ambassadors use Meeting:EMEA_Ambassadors_<date> as their naming convention)
  3. Use an external ticketing system (e.g. LATAM Ambassadors use their own Redmine instance)
  4. Use your teams mailing list (last resort)

Step 2 : Use Zodbot

Learn to use Zodbot, and use its commands wisely to get informative meetign minutes.

Do that so people that people attended the meeting can look back on it, or so as to keep up to date people that didn't attend the meeting.

Step 3 : Publish the minutes

Send the minutes of the meeting to the mailing list of your team, identi.ca group or publish them in a blog, immediately after ending the meeting. This is a *must*, the responsible of the meeting should to do.

Step 4 : Update the wiki

Update the wiki page of your team, editing the entry of the meeting just finished, marking them as done, and including the links to the minutes and full logs.

Following Steps

Follow up the actions and agreements you have gotten in the meeting. Inform the people interested in those actions items and if you are going to delegate tasks, remember you can't delegate the responsibility of getting the agreements respected and tasks done.

Improve this SOP!

If you see a way to improve this SOP, please go ahead and edit the page - you don't need to ask for anyone's permission. Read more about our contribution philosophy here.