...
|
...
|
@@ -1,6 +1,9 @@
|
1
|
1
|
# $Id$
|
2
|
2
|
|
3
|
|
-Use tells how deployable a module is. Regular indicates
|
|
3
|
+'Owner' field contains a developers CVS username, see file
|
|
4
|
+AUTHORS for more details.
|
|
5
|
+
|
|
6
|
+'Use' tells how deployable a module is. Regular indicates
|
4
|
7
|
we deploy and use this feature in our infrastructure.
|
5
|
8
|
Experimental tells we are still gaining operation experience.
|
6
|
9
|
Temporary labels modules which momentarily fix some
|
...
|
...
|
@@ -8,14 +11,15 @@ bugs/lacks and will disappear later. Example modules
|
8
|
11
|
are primarily useful as educational source code for
|
9
|
12
|
ser programmers.
|
10
|
13
|
|
11
|
|
-Maturity is label as stable if a module has been deployed
|
|
14
|
+'Maturity' is label as stable if a module has been deployed
|
12
|
15
|
for longer time, alpha if it is still being developed and
|
13
|
16
|
beta if it is under test.
|
14
|
17
|
|
15
|
|
-Modules underway include presence server functionality,
|
16
|
|
-firewall control, message store and more. If you are
|
17
|
|
-interested in any of these or other modules, write us
|
18
|
|
-to info@iptel.org.
|
|
18
|
+'Depends on' field tells which modules the module needs.
|
|
19
|
+
|
|
20
|
+Modules underway include firewall control, and more.
|
|
21
|
+If you are interested in any of these or other modules,
|
|
22
|
+write us to info@iptel.org.
|
19
|
23
|
|
20
|
24
|
List of currently available ser modules:
|
21
|
25
|
|