Tim Bell wrote: > As part of the user feedback loop, we've found the PTL role extremely useful > to channel feedback. The operator PTL discussions during the Atlanta summit > helped to clarify a number of areas where the PTL can then take the points > back to the design summit. It is not clear how czars would address the > outward facing part of the PTL role which is clearly needed in view of the > various discussions around program management and priorities. > > If we have lots of czars or major differences in how each project is > structured, it is not clear how we channel user feedback to the project > teams. Would there be a user czar on each project ?
I agree that this external/user communication role is essential, and is likely to stay with the PTL, which is why I didn't have a "User czar" in my list. > I have no problem with lots of czars to delegate activities across the > projects but having a single accountable and elected PTL who can choose the > level of delegation (and be assessed on that) seems to be a very good feature. Indeed, I see it more as a clear list of the duties that usually fall onto the PTL lap, but which could be delegated. If some programs want to keep it the way it is (with the PTL being responsible for all those duties), it's totally fine. It's a framework for clear delegation within the current system, not a whole new system :) -- Thierry Carrez (ttx) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
