User:Dogi/meeting: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(18 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{TOCright}}
= Meeting (Bot) =
= Meeting (Bot) =


== What is it? ==
== What is it? ==
Meeting is a bot that has been designed to make the process of summarizing meetings easier. It is a modified [[http://www.eggheads.org/|eggdrop bot]], running a custom script written in TCL.
Meeting is a bot that has been designed to make the process of summarizing meetings easier. It is a modified [[http://www.eggheads.org/|eggdrop bot]], running a custom script written in TCL. See also http://wiki.debian.org/MeetBot.


== Who Would Use It? ==
== Who Would Use It? ==
Meeting was designed for Chairperson of a meeting to use. A chairperson can flag parts of the meeting for specific topics, actions, and agreed resolutions, which will be outputted into a HTML, Plaintext, or Wiki Formatted document to enable easier browsing of the IRC chat logs.
Meeting was designed for the Chairperson of a meeting to use. A chairperson can flag parts of the meeting for specific topics, actions, and agreed resolutions, which will be outputted into an HTML, Plaintext, or Wiki Formatted document to enable easier browsing of the IRC chat logs.


== How do I request the bot? ==
== How do I request the bot? ==
The bot will always be available in the #olpc-bot channel, If you are running a meeting in a different channel then contact someone in the #olpc-admin IRC channel on OFTC.
The bot will always be available in the #olpc-bot channel, If you are running a meeting in a different channel, then contact someone in the [http://embed.mibbit.com/?server=irc.oftc.net&channel=%23treehouse #treehouse] IRC channel on OFTC.


== How do I use it? ==
== How do I use it? ==
The commands for the bot are shown below:
The commands for the bot are shown below:


* #startmeeting Tells the bot to start listening. Sets the meeting chair to whoever issues this command
* #startmeeting Tells the bot to start listening. Sets and locks the meeting chair to the user who issues this command
* #TOPIC Records a topic of discussion (Can only be issued by the meeting chair)
* #TOPIC Records a topic of discussion (Can only be issued by the meeting chair)
* #IDEA Records an idea releated to the current topic of discussion (Can be used by everyone)
* #IDEA Records an idea related to the current topic of discussion (Can be used by everyone)
* #ACTION Records an action that is decided on (Can only be issued by the meeting chair)
* #ACTION Records an action that is decided on (Can only be issued by the meeting chair)
* #AGREED Records and agreement on a idea (Can only be issued by the meeting chair)
* #AGREED Records and agreement on a idea (Can only be issued by the meeting chair)
Line 22: Line 23:


=== Starting a Meeting ===
=== Starting a Meeting ===
To begin the meeting, the chairperson issues the "#startmeeting" command. This tells the bot to start logging.
To begin the meeting, the chairperson issues the <code>#startmeeting</code> command. This tells the bot to start logging.


<pre>
<pre>
Line 32: Line 33:


=== Changing the Topic ===
=== Changing the Topic ===
As you progress through the meeting the current discussion point should be noted to enable easier reading of the IRC logs. You can change the current topic of discussion by issuing a [TOPIC] command:
As the meeting progresses, the current discussion point should be noted to enable easier reading of the IRC logs. The chair can change the current topic of discussion by issuing a #TOPIC command:


<pre>
<pre>
Line 39: Line 40:
</pre>
</pre>


=== Ideas, Actions and Agreed Actions ===
=== Ideas, Link, Actions and Agreed Actions ===
The #IDEA command are supplied so attendees can provide and log ideas regarding the current topic of discussion, this is useful in brainstorming sessions where all input should be registered for future examination.
The #IDEA command are supplied so attendees can provide and log ideas regarding the current topic of discussion; this is useful in brainstorming sessions where all input should be registered for future examination.


<pre>
<pre>
Line 46: Line 47:
</pre>
</pre>


Similar to this is the #ACTION and #AGREED commands, but these can only be used by the Chairperson. This will add an entry into the log denoting a action to be taken, or a agreement on the current topic.
Similar to this is the #ACTION and #AGREED commands, but these can only be used by the Chairperson. These commands will add an entry into the log denoting a action to be taken, or a agreement on the current topic.


<pre>
<pre>
<dogi> #ACTION Manual to be produced by dogi
<dogi> #ACTION Manual to be produced by dogi
...
<dogi> #LINK http://me.etin.gs/
...
...
<dogi> #AGREED Work on documentation will commence as soon as possible
<dogi> #AGREED Work on documentation will commence as soon as possible
Line 60: Line 63:
<dogi> #endmeeting
<dogi> #endmeeting
<meeting> Meeting Ended: 01:11
<meeting> Meeting Ended: 01:11
<meeting> Summary available at: http://meeting.laptop.org/test-20081104.html
<meeting> Summary available at: http://me.etin.gs/treehouse/
</pre>
</pre>


== What output does the bot produce? ==
== What output does the bot produce? ==
Some recent output can be found [http://meeting.laptop.org/ here]
Some recent output can be found at http://me.etin.gs/treehouse/ and http://meeting.sugarlabs.org/.


== Can I see the bot in action? ==
== Can I see the bot in action? ==
You can try the bot out in the #meeting-test channel on Freenode and OFTC. If you have any further questions just ask someone in the #olpc-admin channel on OFTC. Please feel free to try out starting meetings and various other commands, but we ask if someone else is testing the bot that you wait until they've finished.
You can try the bot out in the #meeting-test channel on Freenode and OFTC. If you have any further questions just ask someone in the [http://embed.mibbit.com/?server=irc.oftc.net&channel=%23treehouse #treehouse] channel on OFTC. Please feel free to try out the #startmeeting and various other commands, but we ask if someone else is testing the bot that you wait until they've finished.


== Do you have an example test script? ==
== Do you have an example test script? ==


Yes, check the [[User:Dogi/Meeting/TestScript Testscript]] page for an example testscript that will use all of Meeting's features.
Yes, check the [[User:Dogi/Meeting/TestScript|Testscript]] page for an example testscript that will use all of Meeting's features.

Latest revision as of 15:53, 10 February 2010

Meeting (Bot)

What is it?

Meeting is a bot that has been designed to make the process of summarizing meetings easier. It is a modified [bot], running a custom script written in TCL. See also http://wiki.debian.org/MeetBot.

Who Would Use It?

Meeting was designed for the Chairperson of a meeting to use. A chairperson can flag parts of the meeting for specific topics, actions, and agreed resolutions, which will be outputted into an HTML, Plaintext, or Wiki Formatted document to enable easier browsing of the IRC chat logs.

How do I request the bot?

The bot will always be available in the #olpc-bot channel, If you are running a meeting in a different channel, then contact someone in the #treehouse IRC channel on OFTC.

How do I use it?

The commands for the bot are shown below:

  • #startmeeting Tells the bot to start listening. Sets and locks the meeting chair to the user who issues this command
  • #TOPIC Records a topic of discussion (Can only be issued by the meeting chair)
  • #IDEA Records an idea related to the current topic of discussion (Can be used by everyone)
  • #ACTION Records an action that is decided on (Can only be issued by the meeting chair)
  • #AGREED Records and agreement on a idea (Can only be issued by the meeting chair)
  • #LINK Records a URL link of any format
  • #endmeeting Ends the meeting (Can only be issued by the meeting chair)

Starting a Meeting

To begin the meeting, the chairperson issues the #startmeeting command. This tells the bot to start logging.

<dogi> #startmeeting
<meeting> Meeting started at 01:00

After issuing the #startmeeting command, the rest of the commands will be enabled.

Changing the Topic

As the meeting progresses, the current discussion point should be noted to enable easier reading of the IRC logs. The chair can change the current topic of discussion by issuing a #TOPIC command:

<dogi> #TOPIC Changing the Topic
* meeting has changed the topic to: Changing the Topic

Ideas, Link, Actions and Agreed Actions

The #IDEA command are supplied so attendees can provide and log ideas regarding the current topic of discussion; this is useful in brainstorming sessions where all input should be registered for future examination.

<dogi> #IDEA Provide full details of the commands on the Wiki

Similar to this is the #ACTION and #AGREED commands, but these can only be used by the Chairperson. These commands will add an entry into the log denoting a action to be taken, or a agreement on the current topic.

<dogi> #ACTION Manual to be produced by dogi
...
<dogi> #LINK http://me.etin.gs/
...
<dogi> #AGREED Work on documentation will commence as soon as possible

Ending the Meeting

After all topics are discussed, the chairperson can then call a close to the meeting using the #endmeeting command

<dogi> #endmeeting
<meeting> Meeting Ended: 01:11
<meeting> Summary available at: http://me.etin.gs/treehouse/

What output does the bot produce?

Some recent output can be found at http://me.etin.gs/treehouse/ and http://meeting.sugarlabs.org/.

Can I see the bot in action?

You can try the bot out in the #meeting-test channel on Freenode and OFTC. If you have any further questions just ask someone in the #treehouse channel on OFTC. Please feel free to try out the #startmeeting and various other commands, but we ask if someone else is testing the bot that you wait until they've finished.

Do you have an example test script?

Yes, check the Testscript page for an example testscript that will use all of Meeting's features.