On Fri, 27 Feb 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > It is such a balance isn't it, we wish the community to get > involved, but other areas of the community suffer if one doesn't > maintain it's metadata.
Absolutely. The thing to keep in mind is that for Apache projects the community has full access to a descriptor that lives inside the Gump module. So the community that can fix things includes more people - and all people who could fix things when the descriptor is in a more private module. >> If the nags are annoying, committers for the project can simply >> turn them off. Same for deferred nags. After all all committers >> are able to remove the nag elements. > > I was hoping for a little more than on/off. I see. I'm a bit unsure as to what we can do here since we'd need to know whether the nags simply get ignored (in which case there is no point in doing anything but turning them off) or just postponed. Is there any automatic way to tell? > I tried to make projects w/o nags generate nags [a single mail] to > the Gump list, so we could process things like broken packages, > etc. I need to debug why that isn't occuring. Seems to work now 8-) Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
