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
expec
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 i
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 variety
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 rat
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 gi
On 9/12/2018 3:30 PM, Dan Smith wrote:
I'm just a bit worried to limit that role to the elected TC members. If
we say "it's the role of the TC to do cross-project PM in OpenStack"
then we artificially limit the number of people who would sign up to do
that kind of work. You mention Ildiko and Lan
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 th
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
On Wed, Sep 12, 2018 at 3:30 PM Dan Smith wrote:
> > I'm just a bit worried to limit that role to the elected TC members. If
> > we say "it's the role of the TC to do cross-project PM in OpenStack"
> > then we artificially limit the number of people who would sign up to do
> > that kind of work.
> I'm just a bit worried to limit that role to the elected TC members. If
> we say "it's the role of the TC to do cross-project PM in OpenStack"
> then we artificially limit the number of people who would sign up to do
> that kind of work. You mention Ildiko and Lance: they did that line of
> work
Hello everyone,
I have set up an etherpad to collect Ops related session ideas for the
Forum at the Berlin Summit. Please suggest any topics that you would
like to see covered, and +1 existing topics you like.
https://etherpad.openstack.org/p/ops-forum-stein
Cheers,
Erik
___
So +1
Tim
From: Lance Bragstad
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, 12 September 2018 at 20:43
To: "OpenStack Development Mailing List (not for usage questions)"
, OpenStack Operators
Subject: [openstack-dev] [all] Consistent policy names
The topic of having consistent policy names has popped up a few times this
week. Ultimately, if we are to move forward with this, we'll need a
convention. To help with that a little bit I started an etherpad [0] that
includes links to policy references, basic conventions *within* that
service, and
Matt Riedemann wrote:
> [...]
> I want to see the TC be more of a cross-project project management
> group, like a group of Ildikos and what she did between nova and cinder
> to get volume multi-attach done, which took persistent supervision to
> herd the cats and get it delivered. Lance is already
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
Rather than take a tangent on Kristi's candidacy thread [1], I'll bring
this up separately.
Kristi said:
"Ultimately, this list isn’t exclusive and I’d love to hear your and
other people's opinions about what you think the I should focus on."
Well since you asked...
Some feedback I gave to
18 matches
Mail list logo