Changes between Version 4 and Version 5 of JabberTracScript


Ignore:
Timestamp:
May 13, 2010 1:36:18 AM (4 years ago)
Author:
XayOn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JabberTracScript

    v4 v5  
    1 = Import jabber-muc logs = 
    2  
    3 == Description == 
    4  
    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. 
    6  
    7 == Bugs/Feature Requests ==  
    8  
    9 Existing bugs and feature requests for JabberTracScript are  
    10 [report:9?COMPONENT=JabberTracScript here]. 
    11  
    12 If you have any issues, create a  
    13 [http://trac-hacks.org/newticket?component=JabberTracScript&owner=XayOn new ticket]. 
    14  
    15 == Download == 
    16  
    17 Download the zipped source from [download:jabbertracscript here]. 
    18  
    19 == Source == 
    20  
    21 You can check out JabberTracScript from [http://trac-hacks.org/svn/jabbertracscript here] using Subversion, or [source:jabbertracscript browse the source] with Trac. 
    22  
    23 == Recent Changes == 
    24  
    25 [[ChangeLog(jabbertracscript, 3)]] 
    26  
    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 == 
    76  
    77 '''Author:''' [wiki:XayOn] [[BR]] 
    78 '''Contributors:'''