SchoolTool and Debian Edu
Hi,
As a follow up to my earlier RFS for SchoolTool [1], I'd like to announce
that SchoolTool has passed muster with the FTP masters and is now installable
from unstable.
Some of the new features in these packages address the issues raised in the
original RFS:
* Support for TCP wrappers (requires python-tcpwrap) [3]
* Native SSL support - no apache virtual hosting required [4]
* Pre-seedable debconf configuration for interfaces and SSL certificates
(if I did it right) [2]
Now i'd like to ask - How do I, from a packaging point of view, make it
easy for Debian Edu users to use SchoolTool?
Some idea's that pop into my mind are (Brain-storming):
* Sarge Backport
- How does SkoleLinux release? Is it with every Debian stable release?
- SchoolTool is young and fast developing package, so would maintaining
a backport for sarge be of any use?
* Write a preseed file for a default Debian Edu setup
- What ports should the server listen on? (we have 2 interfaces, A
RESTive and web interface)
- SSL by default?
- what data to use in the SSL certificate?
* education-* metapackage
- I cannot find a place for SchoolTool in the existing Debain Edu
metapackages. Can someone suggest one? or should i propose an
education-administration package?
* Anything else?
Finally, it's my personal opinion that SchoolTool development could
benefit a lot from wider testing by the future users.
hopefully we will have some;).
[1] http://lists.debian.org/debian-edu/2004/09/msg00029.html
[2] http://lists.debian.org/debian-edu/2004/09/msg00030.html
[3] http://lists.debian.org/debian-edu/2004/09/msg00037.html
[4] http://lists.debian.org/debian-edu/2004/09/msg00039.html
--
Brian Sutherland
Reply to: