root / pykota / trunk / TODO @ 2264

Revision 2264, 5.1 kB (checked in by jerome, 19 years ago)

Improved data dumper : speed and correctness

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