root / pykota / trunk / TODO @ 2162

Revision 2150, 4.0 kB (checked in by jerome, 20 years ago)

New entry about pass-through mode for printers

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