root / pykota / trunk / TODO @ 2325

Revision 2325, 4.8 kB (checked in by jerome, 19 years ago)

Improves the newly added item.
Severity : who reads TODO lists anyway ?

  • 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., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
19
20============================================================
21
22TODO, in no particular order :
23       
24        - Adds configurability to what happens when the user/group doesn't exist
25          when running edpykota. Rewrite the main loop to be able to abort
26          early, before any modification has taken place.
27         
28        - Add the listing of the member printers in pkprinters if the printer
29          is a printer group.
30         
31        - Add a new external hook to allow the overwriting of the job's ticket       
32          (mainly username and billing code) at startup time :
33         
34            1 - hook is launched and can do whatever it wants, like asking
35                the user for username+password or billing code
36               
37            2 - hook prints any (or all) of :   
38           
39                USER:some_username
40                BILLING:some_billingcode
41                DENY
42               
43                if hook doesn't print anything, job processed as usual.
44                if DENY, job is rejected.
45               
46            3 - if billing code or username is invalid, and if PyKota
47                is configured to loop in this case, hook is launched
48                again, otherwise job is rejected.
49               
50            4 - if billing code and/or username is valid, the job's
51                billing code and/or username are overwritten with
52                these values, and PyKota processes the job as usual.
53         
54        - Allow several levels of administrative priviledges by allowing
55          files like ~pykota/pykotadmin.someusername.conf (readonly by
56          user 'someusername'), and have the database server deal
57          with the permissions : no need for additionnal code or data
58          in PyKota's database !
59       
60        - Try to talk to education based distribution coordinators
61          (SambaEdu, SkoleLinux, K12LTSP, ...) to see how to
62          better integrate PyKota with these.
63         
64        - Allow soft and hard limits to be increased/decreased.
65       
66        - Add most configuration directives to the database itself,
67          while still allowing to overwrite them with the configuration
68          files at run time.
69       
70        - Ink accounting ala PrintBill.
71       
72        - Price and statistics per page format.
73       
74        - Allow the admin to choose an action to take when the database
75          is unavailable (server is down or something like that), so
76          introduce two directives :
77         
78            nodb: accept|reject|hold
79            lognodb: /path/to/file/for/later/batch/update/of/database
80       
81        - CUPS accepts the "STATE: ..." message as backchannel
82          data : use this to tell CUPS what action has been taken
83          for current job. I did some testing but wasn't able to
84          make it work...
85         
86        - Think about some possible client <=> PyKota dialog
87          possibilities, like embedding a small web server in
88          PyKota for example, or something like that.
89       
90        - Log something when --add is used with existing entries.
91          Maybe add a new command line option to force/not force
92          modification of existing entries.
93         
94        - Finish implementation of quota-then-balance and
95          balance-then-quota.
96         
97        - Introduce the pkusers command.
98          pkusers --nogroup
99          pkusers --ingroups gr1,gr2,... --outgroups gr3,gr4,...
100         
101        - Allow the --ingroups command line option to repykota, to
102          report only users members of the specified groups.
103         
104        - Documentation...
105         
106        - Learn more bits of PHP to help with phpPyKotaAdmin, which
107          is a GREAT tool !
108       
109        - Multidatabase support, e.g. store users in LDAP, quota 
110          related datas in PostgreSQL, history in text file,
111          and so on... For 2.0, probably not before.
112       
113       
114============================================================
115
116Please e-mail bugs to: alet@librelogiciel.com (Jerome Alet)
Note: See TracBrowser for help on using the browser.