> As promised at this week’s TC meeting, I have applied the various blog posts > and mailing list threads related to changing our governance model to a > series of patches against the openstack/governance repository . > > I have tried to include all of the inputs, as well as my own opinions, and > look at how each proposal needs to be reflected in our current policies so > we do not drop commitments we want to retain along with the processes we are > shedding . > > I am sure we need more discussion, so I have staged the changes as a series > rather than one big patch. Please consider the patches together when > commenting. There are many related changes, and some incremental steps won’t > make sense without the changes that come after (hey, just like code!).
Thanks Doug for moving this discussion out of the blogosphere and into gerrit. That will be very helpful in driving the discussion forward. However, given the proximity of the TC elections, should these all patches all be workflow -1'd as WIP to ensure nothing lands before the incoming TC is ratified? (I'm assuming here that the decision-making on these fairly radical proposals should rest with the new post-election TC - is that a correct assumption?) Cheers, Eoghan _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev