From Fedora Project Wiki

(Trying to give this a real usefulness)
Line 1: Line 1:
== Introduction ==
== Introduction ==


This is an [[:Category:Ambassadors SOPs|Ambassadors SOP]] that describes how to SHORT_DESCRIPTION_OF_TASK.
This is an [[:Category:Ambassadors SOPs|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 ==
== Examples ==


You can see examples of past TYPE_OF_DELIVERABLES at LINK_TO_REPOSITORY_OF_SIMILAR_DELIVERABLES.
You can see examples of past '''Meeting successfully run''' at [http://meetbot.fedoraproject.org/fedora-meeting/2011-01-22/famsco.2011-01-22-13.08.html FAmSCo meeting of January 22, 2011].


== Instructions ==
== Instructions ==


=== Step 1 ===
=== Step 1 : Have a agenda===
 
'''Never spend the time of the people attending the meeting, always publish extensive information of the issues to discuss'''.
 
Use the preferred communication tool of the project/group you are attending, if it has one yet, for example, FAmSCo uses [[FAmSCo_agenda]] in this wiki. Latin American Ambassadors maintain another wiki page, but they use a ticketing system based on Redmine. FESCo uses his own project on trac, other teams prefer their mailing lists. If your team has not estabished a formal communication tool, anyway you should publish the issues and get noticed the people to know it.
 
Whatever way the people wants to get informed of the matter of the meeting, don't forget: '''Never spend the time of the people you want to join the meeting''', nor your oportunity to getting more people actually become engaged into Fedora.
 
=== Step 2 : Use wisely Zodbot commands ===
 
Learn to use [[Zodbot]], and use its commands wisely to get a minute informative to people using it to remember the most importants items discussed on the meeting, or willing to know the meeting results, if they didn't attend the meeting.
 
=== Step 3 : Publish the minutes ===


=== Step 2 ===
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.


=== Last step ===
=== Step 4 : Update the wiki ===
include into the wiki the link to the log. (re-word into more detailed) --[[User:Yn1v|Yn1v]] 13:43, 22 January 2011 (UTC)


== Templates ==
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.


=== Template 1 ===
=== Following Steps ===


=== Template 2 ===
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! ==
== Improve this SOP! ==

Revision as of 02:43, 24 January 2011

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

Never spend the time of the people attending the meeting, always publish extensive information of the issues to discuss.

Use the preferred communication tool of the project/group you are attending, if it has one yet, for example, FAmSCo uses FAmSCo_agenda in this wiki. Latin American Ambassadors maintain another wiki page, but they use a ticketing system based on Redmine. FESCo uses his own project on trac, other teams prefer their mailing lists. If your team has not estabished a formal communication tool, anyway you should publish the issues and get noticed the people to know it.

Whatever way the people wants to get informed of the matter of the meeting, don't forget: Never spend the time of the people you want to join the meeting, nor your oportunity to getting more people actually become engaged into Fedora.

Step 2 : Use wisely Zodbot commands

Learn to use Zodbot, and use its commands wisely to get a minute informative to people using it to remember the most importants items discussed on the meeting, or willing to know the meeting results, if they 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.