[osc][sdk] Merging OpenStack SDK and OpenStack Client teams
Hey everybody, I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful. I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive. Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election. Monty
I would definitely vote for that, since it will help to address one of our biggest problems - changes in OSC take very long to get in due to lack of resources (not to blame anybody). Artem
On 4. Mar 2020, at 17:19, Monty Taylor <mordred@inaugust.com> wrote:
Hey everybody,
I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election.
Monty
Monty, That sounds like a good plan thanks for proposing it. Amy (spotz) On Wed, Mar 4, 2020 at 10:22 AM Monty Taylor <mordred@inaugust.com> wrote:
Hey everybody,
I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election.
Monty
On 04/03/2020 16:19, Monty Taylor wrote:
Hey everybody,
I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
This makes sense.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Yeah - projects were supposed to be mainly about common groups of people working on stuff, so if the overlap is so close already, it seems like a no brainer.
Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election.
If this is good with the two teams, this is good with me :) Hopefully this can help with projects teams issues with OSC/SDK response times.
Monty
On Mar 4, 2020, at 10:49 AM, Graham Hayes <gr@ham.ie> wrote:
On 04/03/2020 16:19, Monty Taylor wrote:
Hey everybody, I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
This makes sense.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Yeah - projects were supposed to be mainly about common groups of people working on stuff, so if the overlap is so close already, it seems like a no brainer.
Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election.
If this is good with the two teams, this is good with me :) Hopefully this can help with projects teams issues with OSC/SDK response times.
Monty
I think it can. I’ve had some chats with some folks on the team and I think we all think this will help streamline and enable us to respond more quickly.
+1 from me for that idea.
On 4 Mar 2020, at 18:38, Monty Taylor <mordred@inaugust.com> wrote:
On Mar 4, 2020, at 10:49 AM, Graham Hayes <gr@ham.ie> wrote:
On 04/03/2020 16:19, Monty Taylor wrote:
Hey everybody, I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
This makes sense.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Yeah - projects were supposed to be mainly about common groups of people working on stuff, so if the overlap is so close already, it seems like a no brainer.
Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election.
If this is good with the two teams, this is good with me :) Hopefully this can help with projects teams issues with OSC/SDK response times.
Monty
I think it can. I’ve had some chats with some folks on the team and I think we all think this will help streamline and enable us to respond more quickly.
— Slawek Kaplonski Senior software engineer Red Hat
+1 On 3/4/20 10:19 AM, Monty Taylor wrote:
Hey everybody,
I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election.
Monty
On Wed, 2020-03-04 at 10:19 -0600, Monty Taylor wrote:
Hey everybody,
I'd like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we're Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Big +1
Dean hasn't had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I'll serve as the PTL for the new combined team until the next election.
Monty
We have been drifting this way for a while, so "yes please". Michael On Thu, Mar 5, 2020 at 2:59 AM Stephen Finucane <stephenfin@redhat.com> wrote:
On Wed, 2020-03-04 at 10:19 -0600, Monty Taylor wrote:
Hey everybody,
I'd like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we're Already ensuring that SDK does what it needs to do to facilitate that goal. We also already share PTG space, and have requested a shared set of time at the upcoming Denver PTG. So really the separation is historical not practical, and these days having additional layers of governance is not super useful.
I propose that we do a simple merge of the teams. This means the current SDK cores will become cores on OSC, and as most of the OSC cores are already SDK cores, it means the SDK team gains amotoki - which is always a positive.
Big +1
Dean hasn't had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I'll serve as the PTL for the new combined team until the next election.
Monty
On Wed, Mar 4, 2020 at 10:24 AM Monty Taylor <mordred@inaugust.com> wrote:
I’d like to propose merging the SDK and OSC teams. We already share an IRC channel, and already share a purpose in life. In OSC we have a current goal of swapping out client implementation for SDK, and we’re
++
Dean hasn’t had time to spend on OSC quite a bit, sadly, and while we remain hopeful that this will change, we’re slowly coming to terms with the possibility that it might not. With that in mind, I’ll serve as the PTL for the new combined team until the next election.
++ This is the right move whether I am able to continue to work on OpenStack or not. Thank you for picking up results from a cab-ride-to-SFO conversation with Dolph. It is in good hands with the combined team. dt -- Dean Troyer dtroyer@gmail.com
participants (9)
-
Amy Marrich
-
Artem Goncharov
-
Dean Troyer
-
Eric Fried
-
Graham Hayes
-
Michael Johnson
-
Monty Taylor
-
Slawek Kaplonski
-
Stephen Finucane