root / pykota / trunk / TODO @ 2250

Revision 2250, 5.0 kB (checked in by jerome, 20 years ago)

New item added

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