* Holger Levsen > today I stumbled upon #403341, which has a very simple fix. There are > quite some similar bugs (simple, with patch) in the debian BTS which > I would like to help fixing, as I use munin heavily for work, in > Debian Edu and privatly. > > So I like to request access to the upstream SVN, as this is where the > debian packaging is kept, AIUI. > > Jose (as new owner of this bug), what do you think? I cc:ed Bernd, as > we spoke about team maintaining munin in December last year.. > > Also, I would suggest to build the munin-plugins-contrib per default > and upload it to Debian, so that these plugins are available even > more easily. Of course there should be a prominent reminder that > those plugins are not part of munin upstream. Then I would also > suggest to include plugins to monitor vservers and xen instances.
Hi guys, glad there's finally some interest in taking over the package from me. I think there's at least a year since I've had any free time and motivation to work on Debian packaging, so it's about high time somebody takes care of it again... Matthias Schmitz was the first one to contact me about taking over the package, and he's been actively following up on that by taking on lots of outstanding work on the 1.2.x branch. My colleague Stig Sandbeck Mathisen has also been trying to work his way through the huge backlog of bug reports (sorry about those). I am under the impression that their work will likely result in a new upstream release (1.2.6) as well as new Debian packages. So I intend to give the package to Matthias, and leave it up to him to decide how he wants to arrange the maintanership, that is, if he wants co-maintainers, if he still wants to keep the code in the upstream SVN repo, and so on. So you should all talk to him. :-) I never heard anything from Jose Carlos Medeiros about taking over the package, by the way. BTW. We have an IRC channel, [EMAIL PROTECTED] Matthias, Stig, and me hangs out there. Feel free to stop by. :-) Regards -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
