root / pykota / trunk / TODO @ 2262

Revision 2262, 5.2 kB (checked in by jerome, 19 years ago)

The URL to the logo used in the CGI scripts is now configurable

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1# $Id$
2
3PyKota - Print Quota for CUPS and LPRng
4
5(c) 2003, 2004, 2005 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
19
20============================================================
21
22TODO, in no particular order :
23       
24        - Add a way to strip off "smbprn.????????" from the left of
25          print jobs' titles (only appear when printing as raw from
26          Winboxes it seems)
27
28        - Ensures that all special characters in strings are properly
29          escaped when dumping datas : quotes, xml entities, etc...
30       
31        - Add date filtering options to dumpykota, something like
32                date=+20050101 date=-20050201
33          to dump all jobs printed between January 1st 2005 included     
34          and February 1st 2005 not included. This looks ugly but
35          at least we avoid the problematic '<' and '>' on command
36          lines, which would mandate the use of quotes...
37       
38        - Pass-through mode for printers : history correctly filled (including
39          job size) but no impact on user's page counter or account
40          balance : this is meant to be a temporary situation for
41          a printer to be in pass-through mode, for example during
42          an exam where the faculty pays for the printouts and we
43          don't want our users to complain about their credits being
44          "eaten" for mandatory printouts.
45         
46        - Allow several levels of administrative priviledges by allowing
47          files like ~pykota/pykotadmin.someusername.conf (readonly by
48          user 'someusername'), and have the database server deal
49          with the permissions : no need for additionnal code or data
50          in PyKota's database !
51       
52        - Add a "printing denied" indicator on user print quota entries, 
53          to temporarily forbid an user to print on a particular printer.
54         
55        - Maybe per user "denyduplicates" : my 5 years old daughter
56          just prints again when the printer is off...
57         
58        - Now that the job size is ALWAYS precomputed, add a
59          MaxJobSize attribute to users and groups (printers as
60          well, maybe ?) to limit each job's size if needed.
61         
62        - Add precomputed job size (and price) to the history for
63          controlling purpose.
64         
65        - Try to talk to education based distribution coordinators
66          (SambaEdu, SkoleLinux, K12LTSP, ...) to see how to
67          better integrate PyKota with these.
68         
69        - Allow soft and hard limits to be increased/decreased.
70       
71        - Add most configuration directives to the database itself,
72          while still allowing to overwrite them with the configuration
73          files at run time.
74       
75        - Ink accounting ala PrintBill.
76       
77        - Price and statistics per page format.
78       
79        - Add a description field to users/groups.
80       
81        - Allow the admin to choose an action to take when the database
82          is unavailable (server is down or something like that), so
83          introduce two directives :
84         
85            nodb: accept|reject|hold
86            lognodb: /path/to/file/for/later/batch/update/of/database
87       
88        - CUPS accepts the "STATE: ..." message as backchannel
89          data : use this to tell CUPS what action has been taken
90          for current job. I did some testing but wasn't able to
91          make it work...
92         
93        - Think about some possible client <=> PyKota dialog
94          possibilities, like embedding a small web server in
95          PyKota for example, or something like that.
96       
97        - Log something when --add is used with existing entries.
98          Maybe add a new command line option to force/not force
99          modification of existing entries.
100         
101        - Finish implementation of quota-then-balance and
102          balance-then-quota.
103         
104        - Introduce the pkusers command.
105          pkusers --nogroup
106          pkusers --ingroups gr1,gr2,... --outgroups gr3,gr4,...
107         
108        - Allow the --ingroups command line option to repykota, to
109          report only users members of the specified groups.
110         
111        - Documentation...
112         
113        - Learn more bits of PHP to help with phpPyKotaAdmin, which
114          is a GREAT tool !
115       
116        - Multidatabase support, e.g. store users in LDAP, quota 
117          related datas in PostgreSQL, history in text file,
118          and so on... For 2.0, probably not before.
119       
120       
121============================================================
122
123Please e-mail bugs to: alet@librelogiciel.com (Jerome Alet)
Note: See TracBrowser for help on using the browser.