1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" "http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd" [
<!ENTITY Lire "<productname>Lire</productname>">
]>
<!-- vim:syntax=xml
FIXME: this document could better use print.dsl as in
cvs-hibou/hibou/doc/foundation ...
-->
<article id="roadmap">
<articleinfo>
<title>The Lire Roadmap</title>
<subtitle>March 2002</subtitle>
<author>
<firstname>Joost</firstname><surname>van Baal</surname>
</author>
<copyright>
<year>2001, 2002</year>
<holder>Stichting LogReport Foundation</holder>
</copyright>
<revhistory>
<revision>
<revnumber>20020313</revnumber>
<date>$Date: 2002/01/31 19:07:11 $</date>
<revremark>
$Id: roadmap.dbx,v 1.5 2002/01/31 19:07:11 vanbaal Exp $
</revremark>
</revision>
</revhistory>
</articleinfo>
<section>
<title>Introduction</title>
<para>
This document gives a roadmap for the development of the LogReport
software, and its role. It serves as a reference point when working on
the software and states the current ideas and plans of the LogReport
developers.
</para>
</section>
<section>
<title>Tasks and dates</title>
<para>
Mid february 2002, we ship a &Lire; release. In march 2002, we could be ready
to ship &Lire; 1.0. If everything works out as planned, major improvements and
features are added at that time, to justify a 1.0 version. We list the tasks,
roughly in order of priority and expected completion time.
</para>
<variablelist>
<varlistentry>
<term>add services</term>
<listitem>
<para>
squid (Joost, code supplied by Joost Bekkers) service is to be added, as well
as MS Proxy, in a proxy superservice. The socks support should be resurrected.
The WELF convertor should be splitted in a welf_packet and welf_proxy part,
since it offers two kinds of functionality. Bugs in the firewall superservice
should be fixed. This superservice is not robust yet. Should be finished
february 14, 2002.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>reusable filters</term>
<listitem>
<para>
It should be possible to reuse filters in report specifications. This makes it
much easier to create and extend reports. See the December 23 mail of Francis
to the LogReport Development List for details. This should be finished
february 14.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>developers documentation</term>
<listitem>
<para>
The xml-ified backend should be properly documented, so that it's easy for
developers to write their own hooks. Should be finished february 14, 2002.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>build binary packages</term>
<listitem>
<para>
Francis will build an <acronym>RPM</acronym> for RedHat, Mandrake and SuSE.
Joost will build a Debian package from the February 2002 release.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>merging and splitting</term>
<listitem>
<para>
It should be possible to merge and split log files and reports. The data could
be stored in some database backend, though this is not absolutely needed: the
interface to access this data could be build with a poor-man's backend,
initially. Later we could e.g. use ODBC databases (like MySQL). Should be
shipped with the 1.0 release in march. We'll try to get some of the tasks
below done too, before the 1.0 release.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>display</term>
<listitem>
<para>
User configuration hooks should be added to tweak various display settings,
the overall sexyness of the output should be improved. A first shot was
made for the december 2001 release. This could go in the 1.0 release.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>jade</term>
<listitem>
<para>
All jade dependencies should be removed, including the depency on jade to
produce PDF output.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>and even more services</term>
<listitem>
<para>
We plan to create a new messagestore superservice, for POP and IMAP servers.
Furthermore, LDAP log file support, and support for extra email services
(iPlanet and Netscape Messaging Server) is planned.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>online responder</term>
<listitem>
<para>
The online responder we offer on our website should be able to produce HTML
output. Addresses like <email>log-html@combined.logreport.org</email> should
get advertised. The HTTP upload interface should be completed. Email
attachment handling should get improved. Installation of a responder from
tarball should be better documented and should be easier.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>configuration interface</term>
<listitem>
<para>
There should be a better configuration interface than the lr_config script we
offer now. The CGI interface should get completed. A GUI interface should get
added.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>internationalisation</term>
<listitem>
<para>
&Lire; should support other languages in its error messages and other output.
This is a long-term task.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>log file recognisition</term>
<listitem>
<para>
We could use tools like bison and flex, the GPL implementations of yacc and
lex, to describe formally the log files, and deal with any input automatically.
This is a long term (and very ambitious) task.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
</article>
<!--
Local Variables:
mode: xml
sgml-indent-step: 2
End:
-->
|
