root / pykota / trunk / TODO @ 2266

Revision 2266, 4.7 kB (checked in by jerome, 19 years ago)

Now dumpykota and dumpykota.cgi accept start= and end=
to specify the starting and ending dates when dumping the
history.
Syntax allowed is :

start|end=YYYY[MM[DD[hh[mm[ss]]]]]

and this is REALLY powerful !

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