Mike> I'm a little nervous about the time commitment, and I'm not Mike> a strong Lisp programmer. So if someone else wants to take Mike> the position, that's fine with me. Thanks for taking this on! Steve Y is the best to advise you about the time commitment for Gnus maintenance, but you don't need to be a strong Lisp programmer. As package maintainer, mostly you need to - keep abreast of changes in your package, - of changes in the package infrastructure, - try to integrate both into your package, - notify the relevant teams of problems you have, and - tell the Package Release Engineer when a release is ready. Since you're not a Lisp programmer (yet? :), the other thing you can do is LART us if there's a problem that's more an XEmacs problem than a Gnus problem, but we seem to be ignoring it. Since it's unreasonable for you to take too much responsibility for those yourself. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.