Hope you all safely travel back to home now.
Here is the summarize from some discussions (as much as I can trigger or
attend) in PTG for SIGs/WGs expose and some idea for action,
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134689.html
I also like the idea to at least expose
Folks,
Sorry for the top post - Those of you that are still at PTG, please feel
free to drop in to the Clear Creek room today.
Thanks,
Dims
On Thu, Sep 13, 2018 at 2:44 PM Jeremy Stanley wrote:
> On 2018-09-12 17:50:30 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > Again, I'm not saying TC
On 2018-09-12 17:50:30 -0600 (-0600), Matt Riedemann wrote:
[...]
> Again, I'm not saying TC members should be doing all of the work
> themselves. That's not realistic, especially when critical parts
> of any major effort are going to involve developers from projects
> on which none of the TC
On Thu, Sep 13, 2018 at 9:14 AM, Fox, Kevin M wrote:
> How about stated this way,
> Its the tc's responsibility to get it done. Either by delegating the
> activity, or by doing it themselves. But either way, it needs to get done.
> Its a ball that has been dropped too much in OpenStacks
On Thu, Sep 13, 2018 at 10:15 AM Fox, Kevin M wrote:
> How about stated this way,
> Its the tc's responsibility to get it done. Either by delegating the
> activity, or by doing it themselves. But either way, it needs to get done.
> Its a ball that has been dropped too much in OpenStacks history.
On Thu, 13 Sep 2018 08:05:17 +0900 Lance Bragstad
wrote
>
>
> On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > So I encourage all elected TC members to work directly with the
> > various SIGs
You're welcome!
--
Kind regards,
Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
On Wed, Sep 12, 2018, 5:52 PM Matt Riedemann wrote:
> On 9/12/2018 5:32 PM, Melvin Hillsman wrote:
> > We basically spent the day focusing on two things specific to what you
> > bring up and are in
On 9/12/2018 5:32 PM, Melvin Hillsman wrote:
We basically spent the day focusing on two things specific to what you
bring up and are in agreement with you regarding action not just talk
around feedback and outreach. [1]
We wiped the agenda clean, discussed our availability (set reasonable
On 9/12/2018 5:13 PM, Jeremy Stanley wrote:
Sure, and I'm saying that instead I think the influence of TC
members_can_ be more valuable in finding and helping additional
people to do these things rather than doing it all themselves, and
it's not just about the limited number of available hours
We basically spent the day focusing on two things specific to what you
bring up and are in agreement with you regarding action not just talk
around feedback and outreach. [1]
We wiped the agenda clean, discussed our availability (set reasonable
expectations), and revisited how we can be more
On 2018-09-12 17:05:17 -0600 (-0600), Lance Bragstad wrote:
[...]
> IMHO, I think the point Matt is making here is more about ensuring
> sure we have people to do what we've agreed upon, as a community,
> as being mission critical. Enablement is imperative, but no matter
> how good we are at it,
On 2018-09-12 17:03:10 -0600 (-0600), Matt Riedemann wrote:
> On 9/12/2018 4:14 PM, Jeremy Stanley wrote:
> > I think Doug's work leading the Python 3 First effort is a great
> > example. He has helped find and enable several other goal champions
> > to collaborate on this. I appreciate the
On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > So I encourage all elected TC members to work directly with the
> > various SIGs to figure out their top issue and then work on
> > managing those deliverables across
On 9/12/2018 4:14 PM, Jeremy Stanley wrote:
I think Doug's work leading the Python 3 First effort is a great
example. He has helped find and enable several other goal champions
to collaborate on this. I appreciate the variety of other things
Doug already does with his available time and would
On 9/12/2018 3:55 PM, Jeremy Stanley wrote:
I almost agree with you. I think the OpenStack TC members should be
actively engaged in recruiting and enabling interested people in the
community to do those things, but I don't think such work should be
solely the domain of the TC and would hate to
On 2018-09-12 16:03:12 -0600 (-0600), Zhipeng Huang wrote:
> On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> > On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> > [...]
> > > So I encourage all elected TC members to work directly with the
> > > various SIGs to figure out their
On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > So I encourage all elected TC members to work directly with the
> > various SIGs to figure out their top issue and then work on
> > managing those deliverables across
On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
[...]
> So I encourage all elected TC members to work directly with the
> various SIGs to figure out their top issue and then work on
> managing those deliverables across the community because the TC is
> particularly well suited to do so
Well Public Cloud WG has prepared the ammo as you know and to discuss with
TC on Friday :)
A hundred percent with you on this matter.
On Wed, Sep 12, 2018 at 9:47 AM Matt Riedemann wrote:
> Rather than take a tangent on Kristi's candidacy thread [1], I'll bring
> this up separately.
>
> Kristi
19 matches
Mail list logo
