Jon Steinhart <[EMAIL PROTECTED]> writes: > I'm willing to take over > releases if need be. Any time that I've tried to push on this in the > past the current maintainer has gotten offended and promised to eventually > do something. We did have a change in maintainer a few years ago, and I > get the idea that that person got burned out by the savannah problems. > I'll take it over if that's OK with the current maintainer.
With Savannah, there is no need to "take it over." You probably already have commit privileges. I think Ken would consider giving one or two others release privileges as well. If Ken goes this route, or hands over the reigns to you and you go this route, it might be useful to create a nmh Maintainer's Document to keep the project managers on the same page. I've been keeping up a maintainer's guide for the MH-E project at: http://mh-e.sourceforge.net/doc/devguide.html This will be useful if I get hit by a truck and someone else needs to figure out what was going on in my mind. I find it invaluable as a checklist every time I make a release as well. Feel free to use this as a starting point for the nmh project. If you do, let me know and I'll give you instructions for getting the Texinfo source via CVS or you can grab it yourself via ViewCVS. -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. _______________________________________________ Nmh-workers mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/nmh-workers
