Hi all, Specialisation is good. I prefer not to hop onto any Debian team I can get on, but rather choose a few places where my help is useful and do them well, rather than to do many things not that well. The security team takes a lot of my 'Debian time', and I also have a number of other packages. So, while reviewing my work on ctn I believe it's better to give that away. I don't have the time to maintain it properly. As previously discussed on this list, ctn hasn't seen an upstream release in years, and may be better replaced by MESA. However, I do not have the time to research that and make it happen. The popcon numbers are not high, especially votes, and it doesn't work with MySQL >= 4. MySQL 3 can be considered ancient these days. Keeping the status quo is not helpful. I suggest any of the following paths: 1) The Debian-Med team takes over CTN maintenance and does something to resolve it's bitrot, e.g. replacing it with MESA. 2) I ask for ctn to be removed. This of course doesn't preclude the first option to be carried out on a later moment. I'm interested to hear your opinions. In any case it doesn't make sense to me to ship ctn with Lenny in its current form. Either path 1 or 2 needs to be chosen. cheers, Thijs
Attachment:
pgpCNMAoiAlB1.pgp
Description: PGP signature