On 05/12/13 at 13:46 +0100, Thijs Kinkhorst wrote: > On Thu, December 5, 2013 11:46, Lucas Nussbaum wrote: > > This was discussed in > > https://lists.debian.org/debian-project/2013/05/msg00018.html. > > Main points are: > > * it facilitates the monitoring of the team manpower, which helps > > taking proactive actions before things get too difficult. > > * it provides a place to clearly define what are the roles, > > responsibilities, powers of the team. > > * it's a rather lightweight process when things work well. It's > > bureaucratic, yes, but not so expensive bureaucracy. > > These arguments are all inherently bureaucratic in nature (monitoring, > defining responsibilities). That's not bad per se, if it can be justified > that this form of monitoring or formal responsibility determination > actually solved concrete issues. Since you skipped my request for concrete > examples, I'm assuming you also haven't seen such cases :)
I don't think that delegations solve any problem per se. They are a tool that facilitate the monitoring of key teams in the project. Obviously, from the DPL POV, the goal should not be to focus on the bureaucracy side, but rather on having well-functioning key teams. I am convinced that delegations help with making sure that teams stay functional, and I'd assume that Stefano agrees given the amount of work he put during his three terms into clarifying the roles of teams, and delegating additional teams. > I'm not convinced that the work done on all these delegations is a net win. I am. Lucas -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131205132105.ga3...@xanadu.blop.info