| 23 | | == Recent Changes == |
| | 25 | == Configuration |
| | 26 | |
| | 27 | First you'll need to have a working Trac environment. |
| | 28 | Then, install and enable plugin TicketBackLinksMacro. |
| | 29 | Then you will need a Jabber server with logging enabled, for chatrooms, configured to be ordered by subdirectories (dates). Jabber with jcr and muc is known to work ok. |
| | 30 | |
| | 31 | You'll have to configure j2t (config done from inside the script) to fit your needs, consisting of Trac's main location, conference server address etc. |
| | 32 | Run `touch /etc/j2t.cfg`. |
| | 33 | Then launch "j2t -c chatroom tracname" for each chatroom you want. |
| | 34 | |
| | 35 | You can make a cron to launch j2t (without arguments) each time you want it to be updated. |
| | 36 | |
| | 37 | WARNING: This should be done at most once a day, otherwise it will make too much noise on your timelines. |
| | 38 | |
| | 39 | === Recommendations |
| | 40 | |
| | 41 | Now, you'll have logs uploaded to wiki and shown in tickets' description. I recommend using TracFineGrainedPermissions to block undesired traffic to the conversations. |
| | 42 | |
| | 43 | Chatrooms will not be created automatically, so, if they don't exists, you'll have to join to them. A workaround for automatising this is having a gozerbot doing that work for you. |
| | 44 | |
| | 45 | I've also built a gozerplug for this: j2t.py. |
| | 46 | You'll have to modify it a bit, since it's ready to get config trought ssh, and that might not be what you want. Also, you'll have to configure that user |
| | 47 | to don't require passwords if you use ssh, because of certificates. |
| | 48 | |
| | 49 | If you wan't you can configure your bot nick inside j2t (botnick variable) so its messages won't be shown. Also, commands are not saved (!whatever strings) into wiki. |
| | 50 | |
| | 51 | === Other |
| | 52 | |
| | 53 | Check out my other gozerplugs: showticket and showrevision, for better integration with Trac: http://public.warp.es/trac-stuff/browser/tools/gozerplugs |
| | 54 | |
| | 55 | I know there are gozerplugs already for Trac integration, but those are adapted for this system using j2t.cfg same way as j2t does, so it interact perfectly with them. |
| | 56 | |
| | 57 | == Recent Changes |
| 27 | | |
| 28 | | = Howto integrate trac with jabber = |
| 29 | | |
| 30 | | === Deps === |
| 31 | | First you'll need to have a working trac environment. |
| 32 | | Then, install plugin (and enable it) TicketBackLinksMacro |
| 33 | | This script. |
| 34 | | A jabber server with logging enabled, for chatrooms, configured to be ordered by subdirectories (dates). Jabber with jcr and muc is known to work ok. |
| 35 | | |
| 36 | | === Configuring === |
| 37 | | You'll have to config j2t (config done from inside the script) to fit your needs |
| 38 | | (tracs main location, conference server address etc) |
| 39 | | Do a touch /etc/j2t.cfg |
| 40 | | Then, launch "j2t -c chatroom tracname" foreach chatroom you want. |
| 41 | | |
| 42 | | You can make a cron to launch j2t (without args) each time you want |
| 43 | | it to be updated. |
| 44 | | |
| 45 | | WARNING: This should be at most once a day, otherwise |
| 46 | | it will make too much noise on your timelines. |
| 47 | | |
| 48 | | === Recomendations === |
| 49 | | Now, you'll have logs uploaded to wiki and shown in tickets' description. |
| 50 | | I recommend using TracFineGrainedPermissions to block undesired traffic to |
| 51 | | the conversations. |
| 52 | | |
| 53 | | Chatrooms will not be created automatically, so, if they don't exists, you'll have |
| 54 | | to join to them. |
| 55 | | A workaround for automatising this is having a gozerbot doing that work for you. |
| 56 | | |
| 57 | | I've also built a gozerplug for this: j2t.py ( original, isn't it? ;-) ) |
| 58 | | You'll have to modify it a bit, since it's ready to get config trought ssh, |
| 59 | | and that might not be what you want. Also, you'll have to configure that user |
| 60 | | to don't require passwords if you use ssh (you know, certificates and so). |
| 61 | | |
| 62 | | If you wan't you can configure your bot nick inside j2t (botnick variable) so |
| 63 | | its messages won't be shown, also, commands are not saved (!whatever strings) into wiki. |
| 64 | | |
| 65 | | == Others == |
| 66 | | Check out my other gozerplugs: showticket and showrevision, to better integration |
| 67 | | with trac. http://public.warp.es/trac-stuff/browser/tools/gozerplugs |
| 68 | | |
| 69 | | I know there are gozerplugs already for trac integration, but those are adapted for |
| 70 | | |
| 71 | | this system (using j2t.cfg same way as j2t does, so it interact perfectly with them). |
| 72 | | |
| 73 | | |
| 74 | | |
| 75 | | == Author/Contributors == |
| | 61 | == Author/Contributors |
