23 | | - Ensure no banner is printed if the user cancelled his job |
24 | | through pknotify+PyKotIcon. |
25 | | |
26 | | - Add a third settable price for printers : a minimal cost |
27 | | for a page, with a default value of 0.0. The value would |
28 | | be used instead of the computed price in the case of ink |
29 | | accounting if the computed price would be lower than this |
30 | | minimal price. The value wouldn't be used (yet?) for |
31 | | normal page accounting. |
32 | | |
33 | | - Document the PYKOTA_HOME environment variable. |
34 | | |
35 | | - LDAP : See if setting cn=ThePrinter for user print quota entries |
36 | | could be done, only in the case where userquotabase=user |
37 | | (idem for groups). Would make direct modifications (e.g. |
38 | | with gq) more easy. |
39 | | |
40 | | - Allow the disabling of an user print quota entry without |
41 | | deleting it. |
42 | | |
43 | | - Store the value of the user's account balance in the |
44 | | printing history (the value at the time of printing) |
45 | | as well as in the payments history (as a safety check |
46 | | in case an user complains). |
47 | | |
48 | | - PJL for non-networked backends (see ML's history) |
49 | | |
50 | | - Add the listing of the member printers in pkprinters if the printer |
51 | | is a printer group. |
52 | | |
53 | | - Allow several levels of administrative priviledges by allowing |
54 | | files like ~pykota/pykotadmin.someusername.conf (readonly by |
55 | | user 'someusername'), and have the database server deal |
56 | | with the permissions : no need for additionnal code or data |
57 | | in PyKota's database ! |
58 | | |
59 | | - Try to talk to education based distribution coordinators |
60 | | (SambaEdu, SkoleLinux, K12LTSP, ...) to see how to |
61 | | better integrate PyKota with these. |
62 | | |
63 | | - Add most configuration directives to the database itself, |
64 | | while still allowing to overwrite them with the configuration |
65 | | files at run time. |
66 | | |
67 | | - Price and statistics per page format. |
68 | | |
69 | | - Allow the admin to choose an action to take when the database |
70 | | is unavailable (server is down or something like that), so |
71 | | introduce two directives : |
72 | | |
73 | | nodb: accept|reject|hold |
74 | | lognodb: /path/to/file/for/later/batch/update/of/database |
75 | | |
76 | | - CUPS accepts the "STATE: ..." message as backchannel |
77 | | data : use this to tell CUPS what action has been taken |
78 | | for current job. I did some testing but wasn't able to |
79 | | make it work... |
80 | | |
81 | | - Documentation... |
82 | | |
83 | | - Learn more bits of PHP to help with phpPyKotaAdmin, which |
84 | | is a GREAT tool ! |
85 | | |
86 | | - Multidatabase support, e.g. store users in LDAP, quota |
87 | | related datas in PostgreSQL, history in text file, |
88 | | and so on... For 2.0, probably not before. |
89 | | |
90 | | - Re-add support for LPRng if interest is high enough (it is |
91 | | not for now) |
92 | | |
93 | | |
94 | | ============================================================ |
95 | | |
96 | | Please e-mail bugs to: alet@librelogiciel.com (Jerome Alet) |
| 30 | Thanks in advance. |