Boris Pavlovic wrote: > By the way, I am really not sure how being one Program will help us to > collaborate? What it actually changes?
Being in one program means you're in the same team, the same meetings, with ultimate decisions taken by the same one PTL. It obviously makes it easier to avoid duplication of effort and make stronger architectural or placement decisions. Being in two separate programs means we need to arbitrate conflicts between the two programs at the TC level, or accept some amount of duplication of effort or technical debt increase. This is why the TC is so focused on non-overlapping scopes when considering new programs, and is willing to defer blessing applications until teams work in a complementary fashion. Here it seems that we are combining several things: an instrumentation library (which sounds more like Oslo or QA), a performance testing system (which sounds more like QA), and future operator tools like a SLA management platform, LogaaS (which sounds more like their own program, but those tools are not really "there" yet). The combination is what creates the tension. I'm not saying there is no solution to this puzzle, just explaining where the tension comes from. -- Thierry Carrez (ttx) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
