Anthony Towns <aj@azure.humbug.org.au> wrote: > If they don't do it, and it's important, someone else will. Cf the > security team versus testing security support, backports or [...]
That's fine if "they" don't do it. I think the problem is when they're doing it and make a mistake which they won't fix: how can anyone else fix it without some pretty ugly forking/competition? I think we do need basic support from core infrastructure teams. [...] > You can reasonably expect them to do what they've said they will, or > what the role obviously entails. You can also expect that every now > and then you'll be disappointed and that won't be achieved, and that > the only things you can really do about that is not worry about it and > hope it's better next time, work out how to do it yourself, or figure > out some way of helping them out. Not worrying about it isn't always a useful option; if it requires special permissions which only the person not fixing it can grant, you can't do it yourself; and if you try to help them (sending patches and so on), they may ignore the attempt. In other words, does the above combined with a DPL who won't appoint new people to underperforming teams mean: you're blocked; enjoy the free parking? Regards, -- MJR/slef My Opinion Only: see http://people.debian.org/~mjr/ Please follow http://www.uk.debian.org/MailingLists/#codeofconduct -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
