Hi Scott, It came up on the TSC call two or three weeks ago and I started to execute as I got responses from TL’s. Sorry if it felt sudden we probably should’ve given a bit longer heads up on the mailing list. As for the Koji changes, I believe that will be an excellent opportunity to see how the cross-sub-project synchronization and collaboration works within the community and improve on the parts that are less efficient. Thanks and Best Regards, Ildikó
On 2018. Nov 7., at 19:21, Scott Little <scott.little@windriver.com> wrote:
Ok.
I wasn't complaining. Just wanted to make sure it was all intentional. It was strange to have +2 power for one iteration of a review, but not the next.
Scott
PS. If the Koji train starts building momentum, there will be a lot more restructuring work to do. A lot more gits to manage. It'll be interesting.
On 18-11-07 12:25 PM, Dean Troyer wrote:
Actually I had pretty broad +2/+1 power to most repos, at least initially, to facilitate repo creation and restructuring. Roughly on par with Dean. I wasn't that I was a core reviewer in the normal sense. Just a backup to Dean that can do some of the structural work.
If I'm being demoted, fine, as long as that was the intent. The intent was to get the right people with the responsibility into
On Wed, Nov 7, 2018 at 9:58 AM Scott Little <scott.little@windriver.com> wrote: the right groups. FWIW I no longer have +2 in any of the code repos in Gerrit [0] now that we're basically up and running. The TL's have management of their groups and enough people know their way around to fix the things I needed to handle in the beginning that I can let go there.
In emergency cases where core team members may be unavailable we have the OpenStack Infrastructure team to turn to for help in IRC #openstack-infra.
dt
[0] Just docs, specs and release now. This is a Good Thing(TM).