Changes between Version 4 and Version 5 of JabberTracScript


Ignore:
Timestamp:
Sep 9, 2015, 12:31:11 PM (2 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • JabberTracScript

    v4 v5  
    1 = Import jabber-muc logs =
     1= Import Jabber-muc logs
    22
    3 == Description ==
     3== Description
    44
    5 Just a simple script that formats and imports into wiki a series of jabber-muc logs inside a series of tracs, organised by chatrooms.
     5This is a Perl script that formats and imports into Trac wiki a series of Jabber-muc logs, organised by chatrooms. [http://www.jabber.org/ Jabber] is an IM service based on XMPP and one of the key nodes on the XMPP network.
    66
    7 == Bugs/Feature Requests ==
     7== Bugs/Feature Requests
    88
    99Existing bugs and feature requests for JabberTracScript are
     
    1111
    1212If you have any issues, create a
    13 [http://trac-hacks.org/newticket?component=JabberTracScript&owner=XayOn new ticket].
     13[/newticket?component=JabberTracScript new ticket].
    1414
    15 == Download ==
     15[[TicketQuery(component=JabberTracScript&group=type,format=progress)]]
     16
     17== Download
    1618
    1719Download the zipped source from [download:jabbertracscript here].
    1820
    19 == Source ==
     21== Source
    2022
    2123You can check out JabberTracScript from [http://trac-hacks.org/svn/jabbertracscript here] using Subversion, or [source:jabbertracscript browse the source] with Trac.
    2224
    23 == Recent Changes ==
     25== Configuration
     26
     27First you'll need to have a working Trac environment.
     28Then, install and enable plugin TicketBackLinksMacro.
     29Then 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
     31You'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.
     32Run `touch /etc/j2t.cfg`.
     33Then launch "j2t -c chatroom tracname" for each chatroom you want.
     34
     35You can make a cron to launch j2t (without arguments) each time you want it to be updated.
     36
     37WARNING: This should be done at most once a day, otherwise it will make too much noise on your timelines.
     38
     39=== Recommendations
     40
     41Now, you'll have logs uploaded to wiki and shown in tickets' description. I recommend using TracFineGrainedPermissions to block undesired traffic to the conversations.
     42
     43Chatrooms 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
     45I've also built a gozerplug for this: j2t.py.
     46You'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
     47to don't require passwords if you use ssh, because of certificates.
     48
     49If 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
     53Check out my other gozerplugs: showticket and showrevision, for better integration with Trac: http://public.warp.es/trac-stuff/browser/tools/gozerplugs
     54
     55I 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
    2458
    2559[[ChangeLog(jabbertracscript, 3)]]
    2660
    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
    7662
    7763'''Author:''' [wiki:XayOn] [[BR]]
     64'''Maintainer:''' [[Maintainer]] [[BR]]
    7865'''Contributors:'''