Thierry Carrez wrote:
> As announced previously[1][2], there were no PTL candidates within the
> election deadline for a number of official OpenStack project teams:
> Astara, UX, OpenStackSalt and Security.
>
> In the Astara case, the current team working on it would like to abandon
> the project
Sorry for the top post - fyi, i've submitted a review for OpenStackSalt
https://review.openstack.org/#/c/377906/
-- Dims
On Mon, Sep 26, 2016 at 2:58 AM, Flavio Percoco wrote:
> On 22/09/16 17:15 -0400, Anita Kuno wrote:
>>
>> On 16-09-21 01:11 PM, Doug Hellmann wrote:
>>>
On 22/09/16 17:15 -0400, Anita Kuno wrote:
On 16-09-21 01:11 PM, Doug Hellmann wrote:
Excerpts from Clint Byrum's message of 2016-09-21 08:56:24 -0700:
I think it might also be useful if we could make the meeting bot remind
teams of any pending actions they need to take such as elections upon
Hiya,
On 24/09/2016 03:46, Mike Perez wrote:
On 11:03 Sep 21, Doug Hellmann wrote:
A separate mailing list just for “important announcements” would
need someone to decide what is “important”. It would also need
everyone to be subscribed, or we would have to cross-post to the
existing list.
+1! The security project adds tremendous value to OpenStack.
Regards
-steve
From: Doug Hellmann
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, September 23, 2016 at 10:35 AM
To: openstack-dev
On 11:03 Sep 21, Doug Hellmann wrote:
>
> > On Sep 21, 2016, at 8:58 AM, Filip Pytloun
> > wrote:
> >
> > Hello,
> >
> > it's definately our bad that we missed elections in OpenStackSalt
> > project. Reason is similar to Rob's - we are active on different
> >
Excerpts from Rob C's message of 2016-09-23 17:46:46 +0100:
> I wanted to provide a quick update from Security.
>
> We had our weekly IRC meeting yesterday, dhellman was kind enough to attend
> to help broker some of the discussion. In advance of the meeting I prepared
> a blog post where I tried
On 13:17 Sep 21, Rob C wrote:
> For my part, I missed the elections, that's my bad. I normally put a
> calendar item in for that issue. I don't think that my missing the election
> date should result in the group being treated in this way. Members of the
> TC have contacted me about unrelated
I wanted to provide a quick update from Security.
We had our weekly IRC meeting yesterday, dhellman was kind enough to attend
to help broker some of the discussion. In advance of the meeting I prepared
a blog post where I tried to articulate my position and where I think
things need to go next
Steven,
Fair point.
Thanks,
Dims
On Thu, Sep 22, 2016 at 11:04 PM, Steven Dake (stdake) wrote:
> Dims,
>
> This isn’t any of my particular business except it could affect emerging
> technology projects (which I find important to OpenStack’s future) negatively
> – so I
Dims,
This isn’t any of my particular business except it could affect emerging
technology projects (which I find important to OpenStack’s future) negatively –
so I thought I’d chime in.
A lack of activity in a specs repo doesn’t mean much to me. For example, as
Kolla was an emerging project
On 16-09-21 01:11 PM, Doug Hellmann wrote:
Excerpts from Clint Byrum's message of 2016-09-21 08:56:24 -0700:
Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200:
Hello,
it's definately our bad that we missed elections in OpenStackSalt
project. Reason is similar to Rob's - we
-Original Message-
From: Filip Pytloun
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 22, 2016 at 10:34:00
To: OpenStack Development Mailing List (not for usage questions)
On 16-09-22 11:32 AM, Filip Pytloun wrote:
If there's more we can do, we are available at Freenode/#openstack-salt.
I think this right here is your issue. Believing it is the
responsibility of the tc or other leaders to find you. It isn't.
Be available on #openstack-dev at the very least.
Thank you for your feedback - this is first one since we joined Big Tent
and very useful.
On 2016/09/21 17:08, Davanum Srinivas wrote:
> Data points so far are:
> 1. No response during Barcelona planning for rooms
> 2. Lack of candidates for PTL election
> 3. No activity in the releases/
On 16-09-21 05:08 PM, Davanum Srinivas wrote:
Jakub,
Please see below.
On Wed, Sep 21, 2016 at 3:46 PM, Jakub Pavlik wrote:
Hello all,
it took us 2 years of hard working to get these official. OpenStack-Salt is
now used by around 40 production deployments and it is
"My answer would be -that- is the most ideal scenario. I care about
OpenStack and ensuring quality projects have adequate representation so I
checked to see which ones didn't have anyone defined for leadership and
picked one to step in and help, assuming no one was able to fill that role
for that
On 2016-09-21 22:53:10 +0100 (+0100), Dave Walker wrote:
> On 21 September 2016 at 22:41, Kyle Mestery wrote:
> > On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez
> > wrote:
> > > I privately received information that explains why the PTL was
> > > not
Excerpts from Dave Walker's message of 2016-09-21 22:53:10 +0100:
> On 21 September 2016 at 22:41, Kyle Mestery wrote:
>
> > On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez
> > wrote:
> > > Chivers, Doug wrote:
> > >> My concern is with the original
On 21 September 2016 at 22:41, Kyle Mestery wrote:
> On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez
> wrote:
> > Chivers, Doug wrote:
> >> My concern is with the original wording “The suggested way forward
> there would be to remove the "Security
On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez wrote:
> Chivers, Doug wrote:
>> My concern is with the original wording “The suggested way forward there
>> would be to remove the "Security project team"”.
>>
>> This seems like a move to instantly reduce investment in
On 2016-09-21 10:18:58 -0700 (-0700), Morgan Fainberg wrote:
[...]
> For what it is worth the VMT had some discussion about this and in the case
> the security team was/is dissolved/moved to a WG we will take some action
> and make some proposals to handle the situation so we have a nice place to
Jakub,
Please see below.
On Wed, Sep 21, 2016 at 3:46 PM, Jakub Pavlik wrote:
> Hello all,
>
> it took us 2 years of hard working to get these official. OpenStack-Salt is
> now used by around 40 production deployments and it is focused very on
> operation and
Please see below.
On Wed, Sep 21, 2016 at 4:35 PM, Thierry Carrez wrote:
> Chivers, Doug wrote:
>> My concern is with the original wording “The suggested way forward there
>> would be to remove the "Security project team"”.
>>
>> This seems like a move to instantly reduce
Hello all,
We have our weekly OSSP IRC meeting tomorrow at 1700UTC (1200 Central) in
#openstack-meeting-alt. This thread has raised some important issues, and
we will devote a significant portion of our meeting to discussing them. My
IRC handle is "ccneill" on freenode if you'd like to get in
Chivers, Doug wrote:
> My concern is with the original wording “The suggested way forward there
> would be to remove the "Security project team"”.
>
> This seems like a move to instantly reduce investment in OpenStack security,
> because the majority of members of the Security Project are
Jakub Pavlik wrote:
> it took us 2 years of hard working to get these official. OpenStack-Salt
> is now used by around 40 production deployments and it is focused very
> on operation and popularity is growing. You are removing the project
> week after one of top contributor announced that they
Travis,
My answer would be -that- is the most ideal scenario. I care about
OpenStack and ensuring quality projects have adequate representation so I
checked to see which ones didn't have anyone defined for leadership and
picked one to step in and help, assuming no one was able to fill that role
Hello all,
it took us 2 years of hard working to get these official. OpenStack-Salt
is now used by around 40 production deployments and it is focused very
on operation and popularity is growing. You are removing the project
week after one of top contributor announced that they will use that
Excerpts from Filip Pytloun's message of 2016-09-21 20:36:42 +0200:
> On 2016/09/21 13:23, Doug Hellmann wrote:
> > The idea of splitting the contributor list comes up pretty regularly
> > and we rehash the same suggestions each time. Given that what we
> > have now worked fine for 57 of the 59
"So all this said, there are individuals interested in the PTL role to
ensure project teams have someone handling the logistics and coordination.
My issue however was that I was not yet eligible to be a candidate which
I'll remedy moving forward.
I'm still interested in serving as a PTL for a
Excerpts from Chivers, Doug's message of 2016-09-21 18:20:35 +:
> My concern is with the original wording “The suggested way forward there
> would be to remove the "Security project team"”.
>
> This seems like a move to instantly reduce investment in OpenStack security,
> because the
On 21 September 2016 at 19:20, Chivers, Doug wrote:
> My concern is with the original wording “The suggested way forward there
> would be to remove the "Security project team"”.
>
> This seems like a move to instantly reduce investment in OpenStack
> security, because the
On 2016/09/21 13:23, Doug Hellmann wrote:
> The idea of splitting the contributor list comes up pretty regularly
> and we rehash the same suggestions each time. Given that what we
> have now worked fine for 57 of the 59 offical teams (the Astara
> team knew in advance it would not have a PTL
My concern is with the original wording “The suggested way forward there would
be to remove the "Security project team"”.
This seems like a move to instantly reduce investment in OpenStack security,
because the majority of members of the Security Project are corporately funded,
which will be
Excerpts from Filip Pytloun's message of 2016-09-21 17:43:46 +0200:
> Hello,
>
> > With 59 separate teams, even emailing the PTLs directly is becoming
> > impractical. I can’t imagine trying to email all of the core members
> > directly.
> >
> > A separate mailing list just for “important
On Sep 21, 2016 09:37, "Adam Lawson" wrote:
>
> But something else struck me, the velocity and sheer NUMBER of emails
that must be filtered to find and extract these key announcements is tricky
so I don't fault anyone for missing the needle in the haystack. Important
needle no
Agreed entirely with Travis's points. I think it was a given to anyone within
the OSSP that Rob would be our PTL going forward. I recognize that the
community needs feedback to make these decisions, but I am in our IRC channel 5
days a week, at least 8 hours a day, and I have never seen any
Excerpts from Clint Byrum's message of 2016-09-21 08:56:24 -0700:
> Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200:
> > Hello,
> >
> > it's definately our bad that we missed elections in OpenStackSalt
> > project. Reason is similar to Rob's - we are active on different
> >
You know something that struck me, I noticed there were several teams last
cycle that did not elect a PTL so this round I was watching to see if any
teams did not have a PTL elected and presumed it was because of many of the
reasons surfaced in previous emails in this thread including being heads
But something else struck me, the velocity and sheer NUMBER of emails that
must be filtered to find and extract these key announcements is tricky so I
don't fault anyone for missing the needle in the haystack. Important needle
no doubt but I wonder if there are more efficient ways to ensure
Ouch. I'd be among the first to admit I don't keep up with dev ML
as I should. Missing the PTL elections is certainly embarrassing
for us and it shouldn't be the community's job to baby-sit us and
make sure we're meeting our OpenStack deadlines.
That being said, relegating us to a working group
Hello,
> With 59 separate teams, even emailing the PTLs directly is becoming
> impractical. I can’t imagine trying to email all of the core members directly.
>
> A separate mailing list just for “important announcements” would need someone
> to decide what is “important”. It would also need
Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200:
> Hello,
>
> it's definately our bad that we missed elections in OpenStackSalt
> project. Reason is similar to Rob's - we are active on different
> channels (mostly IRC as we keep regular meetings) and don't used to
> reading
On 09/21/2016 05:17 AM, Rob C wrote:
> Apart from missing elections, I think we do a huge amount for the community
> and removing us from OpenStack would in no way be beneficial to either the
> Security Project or OpenStack as a whole.
I definitely agree with Rob here and I support keeping the
> On Sep 21, 2016, at 8:58 AM, Filip Pytloun wrote:
>
> Hello,
>
> it's definately our bad that we missed elections in OpenStackSalt
> project. Reason is similar to Rob's - we are active on different
> channels (mostly IRC as we keep regular meetings) and don't used
Excerpts from Rob C's message of 2016-09-21 13:17:07 +0100:
> For my part, I missed the elections, that's my bad. I normally put a
> calendar item in for that issue. I don't think that my missing the election
> date should result in the group being treated in this way. Members of the
> TC have
-Original Message-
From: Rob C
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 21, 2016 at 07:19:40
To: OpenStack Development Mailing List (not for usage questions)
Hello,
it's definately our bad that we missed elections in OpenStackSalt
project. Reason is similar to Rob's - we are active on different
channels (mostly IRC as we keep regular meetings) and don't used to
reading mailing lists with lots of generic topics (it would be good to
have separate
For my part, I missed the elections, that's my bad. I normally put a
calendar item in for that issue. I don't think that my missing the election
date should result in the group being treated in this way. Members of the
TC have contacted me about unrelated things recently, I have always been
50 matches
Mail list logo