root / pykota / trunk / README @ 2700

Revision 2700, 28.8 kB (checked in by jerome, 18 years ago)

Added something about ZjStream?

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