root / pykota / trunk / README @ 2684

Revision 2638, 28.8 kB (checked in by matt, 19 years ago)

Initial MySQL support

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1# $Id$
2
3PyKota - Print Quotas for CUPS and LPRng
4
5(c) 2003, 2004, 2005, 2006 Jerome Alet <alet@librelogiciel.com>
6This program is free software; you can redistribute it and/or modify
7it under the terms of the GNU General Public License as published by
8the Free Software Foundation; either version 2 of the License, or
9(at your option) any later version.
10
11This program is distributed in the hope that it will be useful,
12but WITHOUT ANY WARRANTY; without even the implied warranty of
13MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
14GNU General Public License for more details.
15
16You should have received a copy of the GNU General Public License
17along with this program; if not, write to the Free Software
18Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
19
20====================================================================
21
22READ SPECIAL LICENSING AND REDISTRIBUTION TERMS IN THE FILE 'LICENSE'
23
24====================================================================
25
26PyKota features :
27-----------------
28
29    Free Software :
30   
31        - Licensed under the terms of the GNU General Public License.
32       
33    Commercially Supported :   
34   
35        - Support Contracts are available from http://www.librelogiciel.com/techsupport/
36       
37    Operating systems :
38   
39        - Any Unix-like system as print server.
40           
41        - Any operating system as client.
42           
43    Printing systems :
44   
45        - Supports both CUPS and LPRng as the printing system.
46          NB : LPRng is only supported with versions
47          of PyKota <= v1.22HotFix1, but support for LPRng
48          may be reintroduced at a later date.
49          This version DOES NOT support LPRng !
50       
51    Databases :
52   
53        - Supports PostgreSQL as the database backend.
54          An SQL script to create the database is included.
55       
56        - Supports any LDAP server as the database backend.
57          Complete LDAP schema and sample empty tree are included.
58          Plugging PyKota into your existing LDAP infrastructure
59          is really easy thanks to PyKota's great configurability.
60         
61        - Supports SQLite as the database backend.
62          An SQL script to create the database is included.
63         
64        - Supports MySQL as the database backend.
65          An SQL script to create the database is included.
66
67        - The print jobs history can be stored in any database 
68          of your choice (or in plain text files) if needed.
69         
70        - Master and slave databases are supported : master 
71          in read+write mode, slave in readonly mode.
72          Master and slave databases can be of different types !
73           
74    Printers :       
75   
76        - Hardware or Software accounting methods are completely
77          configurable.
78         
79        - Supports any printer which can report its internal
80          page counter. Can ask printers for their internal
81          page counter via SNMP, Netatalk, PJL, PS, or any
82          other way.
83          This is completely configurable.
84         
85        - Supports DSC compliant and binary PostScript, PDF, PCL5 (up to),
86          PCLXL (aka PCL6), ESC/P2, DVI, TIFF, OpenOffice.org Writer and
87          OpenOffice.org Impress printers (or virtual printers) natively
88          (through the direct use of pkpgcounter's code) for software
89          accounting methods. More formats to come.
90         
91        - Supports any other Page Description Language for which you 
92          have a parser which can be scripted.
93           
94    Quota systems :       
95   
96        - Supports printers and printers groups quotas.
97       
98        - Supports users and users groups quotas.
99       
100        - Supports page quotas.
101          Page quotas can be set differently on a per printer
102          and per user/group basis.
103       
104        - Supports account balance quotas in any currency.
105          Account balance quotas can be set on a per user
106          basis. The account balance is shared amongst
107          all printers. The history of payments (positive
108          or negative credits to an user account) is kept.
109         
110        - Supports high granularity periodic print quotas : down
111          to one minute intervals if needed.
112       
113        - Page quotas and account balance can be set/reset
114          independantly.
115         
116        - Page quotas can be set on a per user or per group basis
117          for a particular printer.
118         
119        - Price per page and per job can be set differently 
120          on any printer.
121       
122        - Low level of page quota or account balance are
123          configurable.
124         
125        - Both soft and hard limit with configurable grace delay 
126          can be set for page quota.
127         
128        - Both soft and hard limits can be increased or decreased at will. 
129       
130        - Possibility to disable quota enforcement for any user
131          or group, while still keeping page accounting.
132         
133        - Each user can have an overcharging (or undercharging) factor, 
134          which is applied whenever PyKota computes the cost of a
135          print job.
136         
137        - Specific pages and credits counters can be defined per billing code,
138          and can be reset independantly of the printing history.
139         
140        - Supports a passthrough mode for printers, which doesn't modify 
141          users quota when they print.
142         
143        - Supports a maximum number of pages per job, configurable for each 
144          printer.
145         
146        - Each user can be completely forbidden to print, independantly from
147          other users.
148         
149        - A transparent printing mode is supported for users, in which
150          their quota is not modified when they print.
151         
152    Administration :       
153   
154        - Almost turn-key solution, with the help of the pkturnkey command
155          line tool for database initialization and initial configuration.
156         
157        - Powerful delegation of administrative priviledges.
158       
159        - Powerful administration tools can be used to
160          automate setting or resetting of quotas or
161          account balances at specific intervals.
162         
163        - Administration tools can modify several users, 
164          groups, or printers at once with the use of
165          powerful wildcard characters.
166         
167        - Account balances can be set, incremented, or 
168          decremented. History of payments is kept.
169         
170        - Number of pages used can be set, incremented, or 
171          decremented.
172         
173        - Both printers and users can be automatically added on
174          first print in a completely configurable way.
175         
176        - Quota report generator available either from the 
177          command line or in any web browser.
178          The web-based quota report generator can be
179          user/password protected.
180         
181        - Print quote generator can tell users how much 
182          a print job will cost them in advance.
183         
184        - Policy with regard to unregistered users can   
185          be configured for each printer to either deny
186          printing, allow printing, or delegate the
187          decision to any external tool.
188         
189        - Warning and error messages can be automatically 
190          sent via email or via any other mean to the administrator,
191          the user, both, or none.
192         
193        - Warning and error messages' content is completely
194          configurable.
195         
196        - Configuration can be changed without needing to 
197          restart the printing system.
198       
199        - Complete print job history is kept. This can be
200          disabled if needed.
201         
202        - Automated low quota or balance remainder can be
203          scheduled regularly or launched manually.
204         
205        - Starting and Ending personalized dynamic banners can be
206          generated on the fly, and accounted for or not, depending
207          on some configuration settings.
208          Banners can still be enabled even if the print job is denied.
209          NB : Banners are a CUPS only feature for now.
210         
211        - Duplicate print jobs can be forbidden automatically. The decision
212          can be left to any script to decide this on a per job basis.
213         
214        - Username and billing code can be overwritten at printing time,
215          to allow people to login as guest users and print as authenticated
216          users, for example.
217         
218        - Powerful data dumper to export datas to other
219          software (spreadsheets for example). Actually
220          supported formats are :
221         
222            - Comma separated values ;
223           
224            - Semicolon separated values ;
225           
226            - Tab separated values ;
227           
228            - XML.
229           
230            - CUPS' page_log format, to easily interface in
231              real time with third party apps like phpPrintAnalyzer
232              and similar tools.
233         
234    User Interface :         
235   
236        - All the command line tools accept the -h | --help
237          command line option which prints all the available
238          options and show usage examples.
239         
240        - Completely internationalized. Actually supports at least partially
241          English, French, Polish, Spanish, Portuguese, Brazilian, Swedish,
242          Thai, Greek, German, Italian, Norwegian (Bokm�, Turkish
243          and traditional Chinese languages.
244          More to come.
245         
246        - Web enabled print quota monitor, data dumper, and quote
247          generator.
248       
249        - An On Screen Display X-Window print quota monitor is included.
250       
251        - An email gateway to allow users to retrieve their print quota
252          information by sending an email message to a dedicated address
253          is included.
254       
255        - A cross-platform print quota monitor will soon be available
256          as an purchaseable add-on.
257         
258        - Third party web based management tools are available.
259
260====================================================================
261       
262Planned features are described in the TODO file.
263
264Actually two (or an infinity of) page accounting methods are
265implemented :
266
267  - The 'hardware' method consists in querying the printer (via SNMP
268    or Netatalk or any other method of your choice) for its total pages
269    counter.
270    This is done both at the beginning and at the end of a
271    print job. The counters difference is then immediately used to
272    decrease the user's account balance or increase his quota usage.
273   
274  - The 'software' method consists in delegating the computation of the
275    job's size in number of pages to any external command of your choice.
276    The command can read the job's data from its standard input and MUST
277    output the job's size on its standard output. Changes to the user
278    account are reported immediately.
279   
280    PyKota featured an internal software accounting method which handles
281    several Page Description Languages : DSC compliant and binary PostScript,
282    PDF, PCLXL (aka PCL6), PCL3/4/5, ESC/P2, DVI, TIFF, OpenOffice.org Writer
283    and OpenOffice.org Impress. This software is now distributed separately
284    as 'pkpgcounter', and not included anymore in PyKota, so you must now
285    download and install it before running PyKota.
286   
287PyKota is known to work fine with most laser printers, either with
288software accounting, or with hardware accounting if the printer
289supports this.
290
291============================================================
292
293SUPPORT CONTRACTS:
294==================
295
296  You can now purchase 8x5x365@NextBusinessDay Technical
297  Support Contracts from us. The yearly fee is computed with 
298  the following formula :
299
300  (100.0 * NbPrintServers) + (2.5 * NbPrinters) + (0.04 * NbUsers) EUROS.
301 
302  This fee includes the VAT, and a free subscription to Official
303  PyKota packages.
304
305  Please send an email to alet@librelogiciel.com if you're
306  interested in purchasing such a contract.   
307
308  Remember that purchasing a support contract for Free Software like PyKota
309  is a great way to show your appreciation for the work already being done
310  on this project, and will help to improve this software in the future.
311
312============================================================
313
314INSTALLATION:
315=============
316
317NB :
318====
319
320  PyKota's documentation is now at :
321 
322    http://www.librelogiciel.com/software/PyKota/WiKota/
323   
324  You may learn more about PyKota, if it fits your own organization,
325  its internal working, and some potential performance drawbacks and
326  how to avoid them, in a document created by Ryan Suarez at :
327 
328    http://archive.macosxlabs.org/forum/webcrossing_archive/documentation/Pykota_and_CUPS/Pykota_and_CUPS.html
329
330  You may also find the following document interesting :
331 
332    http://es.tldp.org/Tutoriales/doc-openldap-samba-cups-python/
333   
334  This document, written in Spanish by Sergio Gonzalez Gonzalez, 
335  describes the integration of PyKota into an OpenLDAP + Samba
336  + CUPS installation. Even for people who can't read spanish
337  this document is really interesting, and contains lots of
338  screenshots.
339 
340  Finally, SuSe users may find the following document to best describe
341  how to install PyKota on their favorite distribution. It's a Spanish
342  document written by Dennis Romero :
343 
344    http://www.cvr.espol.edu.ec/people/dennis/Pykota1.19-SuSE9.1.pdf
345 
346 
347Prerequisite :
348--------------
349   
350  You need to have the following tools installed on the CUPS Server :
351 
352    - CUPS (http://www.cups.org)
353    - Python v2.1 or above (http://www.python.org)
354    - eGenix' mxDateTime Python extension (http://www.egenix.com)
355    - The pkpgcounter command line tool, version 1.56 or higher. This
356      tool is now mandatory for PyKota to work.
357      (http://www.librelogiciel.com/software/)
358    - The JAXML Python module to be able to dump datas in the XML format.
359      (http://www.librelogiciel.com/software/)
360    - The Python-SNMP module to query printers for their page counter.
361      (http://pysnmp.sourceforge.net).
362      IMPORTANT : version 3.4.4 (or 3.4.3 or 3.4.2) is REQUIRED.
363      Versions 2.x or 4.x won't work for now.
364    - The Python-OSD module to use the graphical print quota reminder.
365      (http://repose.cx/pyosd/)
366    - SNMP tools (specifically the snmpget command) if you prefer to
367      use your own script to request query printers.
368      (http://www.net-snmp.org)
369    - Netatalk (specifically the pap command) if you plan to
370      request your printer's lifetime page counter via AppleTalk.
371      (http://netatalk.sourceforge.net)
372    - The ReportLab Python module (http://www.reportlab.org) if you want 
373      to have PyKota generate nice banners for you.
374    - The Python Imaging Library (aka PIL) module
375      (http://www.pythonware.com/downloads) if you want to have PyKota
376      generate nice banners for you.
377    - PostgreSQL's PygreSQL Python extension and the PostgreSQL client
378      libraries if you plan to use PostgreSQL as the database backend.
379      (http://www.postgresql.org and http://www.pygreql.org)
380 or     
381    - python-ldap Python module and the OpenLDAP client libraries 
382      if you plan to use an LDAP server as the database backend.
383      (http://www.openldap.org and http://python-ldap.sourceforge.net)
384 or
385    - SQLite v3.2.7 and the SQLite libraries if you plan to use SQLite
386      as the database backend (http://www.sqlite.org). You also need the
387      PySQLite module v2.0.5 or higher (http://www.pysqlite.org)
388 or
389    - MySQL 4.0 or higher and the MySQL-python bindings.
390      IMPORTANT: If you are using MySQL 4.1, then MySQL-python must be
391      version 1.2 or greater. Version 1.0 does not work correctly with 4.1.
392     
393   
394  On Intel i386 architecture, and for performance reasons, it is
395  strongly suggested that you install the Python accelerator Psyco,
396  available at :
397 
398      http://psyco.sourceforge.net
399     
400  Under Debian :   
401 
402      $ apt-get install python-psyco
403     
404  Other architectures may be supported as well in the future, check   
405  this on Psyco's website.
406 
407  Installing Psyco is not mandatory, but it will speedup PCL5 parsing
408  by almost 3 times. PostScript and PDF parsing can also benefit,
409  but in an almost unnoticeable manner since this part of the code
410  is already optimal. For PCL5 this is a completely different matter,
411  and if you install Psyco you will never regret it !
412  Same remark applies for PCL6 (aka PCLXL) : the parser is completely
413  different, but the performance gain with Psyco is impressive.
414 
415  You may also benefit from having the following tools installed to
416  deal with some printers :
417 
418    - npadmin
419    - netcat
420    - ghostscript
421   
422  You need to have the following tools installed on the database
423  server :
424 
425    - PostgreSQL (http://www.postgresql.org)
426   
427  or 
428 
429    - OpenLDAP, or any other LDAP server (http://www.openldap.org)
430   
431  or   
432 
433    - SQLite, v3.2.7 or higher (http://www.sqlite.org).
434      Beware : with SQLite the database server and the print
435      servers MUST be the very same machine.
436   
437NB :   
438
439  PygreSQL must be linked with the PostgreSQL client libraries on
440  the Print Server. The PostgreSQL client libraries' version must
441  match the PostgreSQL version used on the database server.
442 
443or 
444
445  python-ldap must be linked with the OpenLDAP client libraries on the
446  Print Server. The OpenLDAP client libraries' version should match the
447  OpenLDAP version used on the database server, if applicable.
448 
449  This list of prerequisite software may change in the future, when
450  PyKota will support more functionnalities you will be given
451  alternatives.
452 
453  Of course the Print Server and the database server can be the
454  very same machine if you've got a tiny network, or you can have
455  multiple Print Servers all storing their quotas on the same database
456  server if you've got a bigger network. (NB : with SQLite, the database
457  can't be shared between several print servers)
458 
459Hint : 
460------
461
462  - The Debian GNU/Linux distribution is to our knowledge the
463    easiest distribution to install PyKota on, because all
464    of PyKota dependencies are already included, excepted
465    for the PySNMP (http://pysnmp.sourceforge.net) module
466    and the pkpgcounter utility which for now have to be downloaded
467    and installed separately.
468
469Then :   
470------
471 
472Download the latest PyKota version from the Subversion tree :
473
474    $ svn co svn://svn.librelogiciel.com/pykota/trunk pykota
475
476You can now check if the dependencies are correct by typing :
477
478    $ python checkdeps.py
479   
480    An availability report for all the software needed by PyKota
481    will be displayed : you'll have to install the missing
482    software if you want PyKota to work correctly.
483   
484To install the software, just type :
485
486    $ python setup.py install
487
488You may need to be logged in with sufficient privileges (e.g. root)
489
490Create a system user for PyKota :
491
492    $ adduser --system --group --home /etc/pykota --gecos PyKota pykota
493   
494Put the user your printing system is run as in the pykota system group :
495
496    $ adduser lp pykota
497   
498    NB : on our system, the CUPS printing system runs as system user 'lp'.
499    Please adapt this to your own system.
500
501Go to the initscripts subdirectory of PyKota's sources, and choose
502the appropriate storage backend for your configuration. Read carefully
503the associated README file and execute the initialization script
504to create an empty PyKota database. Upgrade scripts may be
505provided as well. NB : if you use PostgreSQL, a good way to
506make PyKota work first time is to modify PostgreSQL's pg_hba.conf
507to allow the 'trust' database connection mode. However once PyKota
508works it is HIGHLY RECOMMENDED TO CHANGE THIS TO A MORE SECURE
509VALUE.
510
511Copy the conf/pykota.conf.sample and  conf/pykotadmin.conf.sample
512sample configuration files to /etc/pykota/pykota.conf and
513/etc/pykota/pykotadmin.conf 
514The installation script usually copies these files into /usr/share/pykota
515
516NB : You can move PyKota's configuration files elsewhere, they will
517be searched first in user pykota's home directory.
518
519You need to adapt these files to your own needs. Especially you may
520have to create sections named after your own printers, and change
521the administrator's email address which by default is
522root@localhost. Read and try to understand these two very well
523commented files, so that you'll encounter less problems later.
524
525Also be sure to double check that commands that query printers
526for their internal page counter work from the command line
527before using them in PyKota's configuration.
528
529The rest of the installation depends on your printing system :
530
531  - CUPS Printing System :
532 
533    Once and for all :
534   
535        Create a symbolic link to the cupspykota backend
536        in CUPS's backend directory :
537       
538          $ cd /usr/lib/cups/backend
539          $ ln -s /usr/share/pykota/cupspykota cupspykota
540         
541        Restart CUPS so that the new backend can be detected.
542       
543          $ /etc/init.d/cupsys restart
544         
545        or :   
546     
547          $ /etc/rc.d/init.d/cupsys restart
548         
549        or any similar command depending on your operating system. 
550         
551    For new printers :
552   
553        Go to CUPS management interface (http://localhost:631)
554        and choose the appropriate PyKota managed device depending
555        on the type of printer you use. For example, if your
556        printer is waiting on :
557       
558            socket://myprinter.example.com:9100
559           
560        Then choose :   
561       
562            cupspykota:socket://myprinter.example.com:9100
563           
564        Configure your printer as usual.   
565       
566        Now double check /etc/pykota/pykota.conf
567       
568        You should manually create a section named after the
569        printer you've just added, unless you have set
570        all options globally.
571       
572        The new pkturnkey command can help you with correct settings
573        for your printers, but don't rely on it because it is still
574        experimental work. To have pkturnkey give you some hints
575        about what to put into pykota.conf, just use its --doconf
576        command line switch :
577       
578          $ pkturnkey --doconf
579       
580        pkturnkey will try to tell you what is the best accounting
581        method for each printer and will print some lines you'll
582        just have to copy&paste in the appropriate sections in
583        /etc/pykota/pykota.conf
584       
585        For more informations about what pkturnkey can do for you,
586        see pkturnkey's manual page or use the --help command
587        line switch :
588       
589          $ pkturnkey --help | less
590       
591        That's all.
592   
593    For existing printers :
594   
595        If you had already installed a version of PyKota earlier
596        than 1.16alpha7, then remove the *cupsFilter lines in your
597        PPD files for each already managed printer. Each
598        line to remove is of the form :
599       
600          *cupsFilter: "application/vnd.cups-postscript 0 /usr/share/pykota/pykota"
601       
602        This means that each time the pstops filter will be executed, it will
603        pass the job's data through the pykota filter which is present in
604        /usr/share/pykota
605       
606        Don't touch anything else, especially any other *cupsFilter line.
607        Then save each of these files.
608       
609        Then, the easiest is to directly modify the DeviceURI lines
610        in /etc/cups/printers.conf, you just have to put
611        'cupspykota:' in front of what is already on these lines.
612        For example, replace :
613   
614            DeviceURI socket://myprinter.example.com:9100
615       
616        with :   
617   
618            DeviceURI cupspykota:socket://myprinter.example.com:9100
619           
620        or :   
621       
622            DeviceURI cupspykota://socket://myprinter.example.com:9100
623       
624        Save the file and restart CUPS.
625       
626        Here too, you may find it interesting to use the pkturnkey command as
627        described above to help with manual configuration of the file
628        /etc/pykota/pykota.conf
629
630  - LPRng Printing System :
631 
632    IMPORTANT : This release of PyKota DOES NOT support LPRng.
633   
634    If you want to use PyKota with LPRng, you have to download
635    an earlier release of PyKota, for example v1.22HotFix1.
636       
637Now you can begin to populate the PyKota's database with printers,
638users and groups :
639 
640Add printers and users to the quota system and set their quota values :
641
642You can either use pkturnkey, or do the same things manually by
643using the pkprinters and edpykota command line tools :
644
645    $ pkprinters --help
646   
647    will tell you how to create, manage or delete printers and
648    printers groups.
649   
650    $ pkprinters --add --charge 0.05 hp2100
651   
652    would add the printer named hp2100 with a price per page
653    of 0.05 unit.
654
655Now set quotas for users on this printer :     
656
657    $ edpykota --add -P hp2100 -S 40 -H 50 user1 ... userN
658       
659    launching edpykota without any argument or with the --help
660    command line option will show you all the possibilities.
661   
662    by default, each user is limited by "quota", this means that on
663    each printer he can have a different soft and hard limit.
664    You may want to limit the user by his account balance value,
665    in which case, the print quota is shared between all printers
666    instead of being different. To do this, use the following :
667   
668    $ edpykota --add -P hp2100 --limitby balance --balance 10 user1 ... userN
669   
670    This will put 10 $ (or Euros, PyKota doesn't care) on each user's account
671    balance, and tell PyKota to limit them by their account balance value.
672    Whenever they print on any printer, their account balance value is
673    decreased by an amount which depends on the particular price per page
674    and per job that you may have defined on the printer with edpykota's
675    --charge command line option.
676    Soft and Hard limits are not used if "--limitby balance" is used,
677    but you can define a "poorman"'s threshold in /etc/pykota/pykota.conf
678    to obtain a similar result (warning message when quota is low).
679
680Restart CUPS, for example under Debian GNU/Linux systems :         
681
682    $ /etc/init.d/cupsys restart
683   
684Your users now should be able to print but not exceed their
685printing quota.
686
687To see printer quota usage on printer hp2100, you can use :
688
689    $ repykota --printer hp2100
690   
691or :
692
693    $ repykota
694   
695    which will print quota usage for all users on all printers,
696    along with totals, if you are a PyKota Administator. If you are
697    a regular user, only your own quota report will be produced.
698   
699Quota reports are also available remotely by using the CGI script
700printquota.cgi provided in the cgi-bin/ subdirectory. You can
701also use the CSS stylesheet present in the stylesheets/ subdirectory
702and put it at your web server's DocumentRoot, to benefit from a nicer
703look, especially quota violations will appear in different colors.
704
705For additionnal security concerns, please give a look at the SECURITY
706file which is part of this software.
707
708To diagnose a problem when something doesn't work as expected,
709please read the very first entry in the FAQ document.
710           
711============================================================
712
713Additionnal tools :
714-------------------
715
716Some people have developped tools around PyKota, and make
717them available under the GNU General Public License :
718
719  - Kanakorn Horsiritham developped phpPykotaAdmin which is
720    a web based database independant administrative GUI,
721    written in PHP.
722 
723      http://opensource.psu.ac.th/~kanakorn/mambo/
724     
725    He was also kind enough to write an installation guide 
726    in english for CUPS and PyKota with phpPykotaAdmin on Fedora
727    Core 3. You'll find this document on the same website.
728   
729    This great software currently at version 0.3 is a wonderful
730    basis for an administrative GUI since it only depends on
731    PyKota commands to be present to successfully manage
732    PyKota's database.
733 
734Additionnal software will be listed here when they will be 
735ready.
736
737============================================================
738
739Mailing list :
740--------------
741
742  A mailing list is dedicated to Pykota, you can subscribe to it
743  or consult its archives at :
744 
745    http://cgi.librelogiciel.com/mailman/listinfo/pykota
746   
747  The mailing list is the preferred way to obtain support, because 
748  all members can help and can also benefit from the solutions
749  proposed by other members.
750 
751  Posts by non-members are usually rejected.
752 
753  The mailing list language is english and only english.
754   
755IRC :   
756-----
757
758  You can also chat with us :
759 
760        /server irc.freenode.net
761        /join #pykota
762       
763  Preferred language on this channel is english, but french     
764  is also accepted. Try to avoid exposing complex problems
765  in french because english speaking people on the channel
766  wouldn't benefit from the solutions.
767 
768  PyKota's main author is known as 'tamere' on IRC.
769   
770============================================================
771   
772Please e-mail bugs to the mailing list at : pykota@librelogiciel.com
773or to the main author at : alet@librelogiciel.com (Jerome Alet)
Note: See TracBrowser for help on using the browser.