Nathanael Nerode wrote: > The classic thing to do is to send a note to the bug trail saying one of > "I sent the fix upstream and will wait for them to fix it" > "I need help finding out whether this patch works" > "This patch doesn't work" > "I don't have time to deal with this, NMUs please" > > Within three months or so of the bug being opened. Or at least after > someone has sent a message to the bug trail saying "Since the mhash > maintainer seems to be inactive..." > > I don't think this is an unreasonable requirement. Just a *little* bit > of communication every so often. > > In particular, since many maintainers can be quite snippy about NMUs, > requesting them explicitly is the best way to get other people to > maintain your package when you're too busy to.
OK, I can certainly try to do better. Usually I _am_ better about this, but this past term I really lost control of everything except my class. Add to that a personal bias towards saying nothing when I'm not sure what to say, and it's a natural response for me. (I'm not justifying myself, just passing on an observation.) Given that, though, I also think you're making more of this than is justified. Being a DD is a voluntary activity, and consequently a certain amount of flakiness is to be expected and tolerated. I've filed many bug reports against packages and have gotten used to many of them being met with silence. I also find that frustrating, but I've accepted that it's just the way things often work in Debian. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
