| | 1 | == IRC communication == |
| | 2 | Parrot developers can frequently be found in the `#parrot` channel of [irc://irc.perl.org]. [http://www.irc.perl.org/ New to IRC]? |
| | 3 | |
| | 4 | === Message Relay Now Available on `#parrot` === |
| | 5 | (Adapted from Will Coleda's posting on our mailing list Aug 29 2007.) |
| | 6 | |
| | 7 | purl in `#parrot` now supports message relay, thanks to Masque++. |
| | 8 | |
| | 9 | To send a message to another user via purl, you can (either in private conversation with purl or in #parrot), type: |
| | 10 | {{{ |
| | 11 | 19:15 <@Fred> msg Coke The frobulator is borken. |
| | 12 | 19:15 <+purl> Message for coke stored. |
| | 13 | }}} |
| | 14 | |
| | 15 | Note that your msg entry does not begin with the forward slash character (/) which other IRC commands begin with. |
| | 16 | |
| | 17 | Then, when purl sees the recipient unidle, she will send them a private message: |
| | 18 | {{{ |
| | 19 | 19:16 <purl> You have 1 message waiting. |
| | 20 | }}} |
| | 21 | |
| | 22 | Respond to the private message with: |
| | 23 | {{{ |
| | 24 | 19:16 <Coke> messages |
| | 25 | 19:16 <purl> You received the following messages: |
| | 26 | 19:16 <purl> Fred [Wed Aug 29 16:15:57 2007] said: The frobulator is borken. |
| | 27 | }}} |
| | 28 | |
| | 29 | When you're done, don't forget to erase the messages (still in private:) |
| | 30 | {{{ |
| | 31 | 19:16 <Coke> messages erase |
| | 32 | 19:16 <purl> Messages erased |
| | 33 | }}} |
| | 34 | |
| | 35 | Note that timestamps are based on purl's time zone, not yours. |
| | 36 | |
| | 37 | Note that gossipbot (née messagebot) was a completely separate code base developed by Infinoid (based on a throw away idea from me); As this was being tested, purl started responding to some of the automated messages, and masque was prompted to fix purl's messages. gossipbot is now frozen in an svn repository somewhere; long live purl! |
| | 38 | |
| | 39 | === svnbotl on `#parrot` === |
| | 40 | svnbotl is our intermittently functioning SVN log bot. The following instructions in operating svnbotl are non-definitive and not guaranteed to work for you. (Isn't that reassuring!) |
| | 41 | |
| | 42 | You must have an account on the feather server. |
| | 43 | Log in to feather. |
| | 44 | {{{ |
| | 45 | ssh youraccount@feather.perl6.nl |
| | 46 | }}} |
| | 47 | Open a screen session. |
| | 48 | {{{ |
| | 49 | screen |
| | 50 | }}} |
| | 51 | Enter this command: |
| | 52 | {{{ |
| | 53 | pugs -I/home/audreyt/pugs/blib6/lib /home/audreyt/pugs/examples/network/svnbot.pl svnbotl irc.perl.org:6667 300 http://svn.perl.org/parrot true true #parrot |
| | 54 | }}} |
| | 55 | Once the bot is operating, you can detach from your _screen session. |
| | 56 | {{{ |
| | 57 | Ctrl+A,d |
| | 58 | }}} |
| | 59 | Then, on #parrot, enter: |
| | 60 | {{{ |
| | 61 | /invite svnbotl #parrot |
| | 62 | }}} |
| | 63 | |
| | 64 | And it might work! Note: snvbotl has historically had a tendency to leave the channel when processing commits with many files. |
