Good morning,
The gatekeeper this week is ... me :-)
https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota
Of course, all input, help and review from the rest of the team most welcome.
Open PR count is at 62. 22 of those have DNM labels on them.
Graham
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
On Wed, Feb 27, 2019 at 06:51:49PM -0500, Erik McCormick wrote:
> In future, we would love to know cutoff dates as soon as you know what
> they are. We don't have a lot of control over exact dates of the
> meetup as it's based primarily on the availability of the host
> organization. However, if it comes soon enough we can try to influence
> the date and plan for it as best we can.
Given it's the same format every time they're known now?
See: https://wiki.openstack.org/wiki/Forum for the format.
So we know the post Denver summit is in Shnaghai:
[tony@thor ~]$ python3
Python 3.7.2 (default, Jan 16 2019, 19:49:22)
[GCC 8.2.1 20181215 (Red Hat 8.2.1-6)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> T=datetime.date(2019,11,4)
>>> print('Etherpads %s' % (T - datetime.timedelta(weeks=11)))
Etherpads 2019-08-19
>>> print('Deadline %s' % (T - datetime.timedelta(weeks=7)))
Deadline 2019-09-16
>>>
> I would also be curious to hear from anyone who is basing their travel
> choices on the approval status of a Forum session. I believe that this
> number is 0, but I'm ready to be proven wrong.
There are companies that only fund 'speakers' for travel and there are
some developer types (like myself) that will be moderating forum
sessions (hopefully) but not talking at the summit.
So there certainly *are* people in this situation.
Tony.
Sean,
> Sean McGinnis <mailto:sean.mcginnis@gmx.com>
> February 27, 2019 at 4:08 PM
>
> To be clear, the issue isn't needing help writing up the submission.
> So great
> if someone can attend or watch for topics coming up that can be pulled
> out into
> Forum ideas, but the crux is that there are a lot of things discussed
> at these
> events and it may take several days after it is over to realize, "hey,
> that
> would be really useful if we could discuss that at the Forum."
Totally understood. That's why we're suggesting to put a few (I counted
five Ops specific Forum talks in Berlin) placeholder sessions in for Ops
with a couple of high level sentences, to be defined later. We're happy
to help update the Forum suggestions after y'all have had a chance to
parse Meetup outcomes into Forum topics that makes sense.
>
> I don't think what Erik asked for is unreasonable. The Ops Meetup event is
> exactly the target we want feeding into Forum discussions. If we can
> give a
> week after the event for the Ops Meetup ends for this processing to
> happen, I
> think we increase the odds of an effective and useful Forum.
I understand the POV, but keep in mind we're also trying to program
against many other interests and we have deadlines that we have to reach
with regards to getting comms out to the rest of the community. We've
extended the deadline by two days, which I hope will give the Ops
Community enough time to parse the info from the Meetup into a few
bite-size bits that we can use as placeholders on the schedule, with
details TBD.
I want to re-emphasize, Kendall and I are happy to help in any way
possible on this. If you want to pass along some napkin notes, we can do
help get those into the schedule :) It's critical that we provide at
least a straw man schedule to the community as early as possible, so we
can identify conflicts and travel considerations for our attendees.
Thanks,
Jimmy
>
> Can we please extend that deadline out a few more days to make sure we
> get this
> valuable input?
>
> Sean
> Kendall Nelson <mailto:kennelson11@gmail.com>
> February 27, 2019 at 3:57 PM
> Hello :)
>
> On Wed, Feb 27, 2019 at 1:26 PM Chris Morgan <mihalis68(a)gmail.com
> <mailto:mihalis68@gmail.com>> wrote:
>
> I think the issue is that forum submissions building on what gets
> discussed in Berlin can't be expected to be finalised whilst
> attendees to the berlin meetup are still traveling. It's not that
> Erik can't pull these things together, in fact he's an old hand at
> this, it's more that this process isn't reasonable if there's so
> little time to collate what we learn in Berlin and feed it forward
> to Denver. Frankly it sounds like because the planning committee
> needs 5 weeks, Erik can have two days. Seem unfair.
>
>
> Honestly, the decision process doesn't take much time, aside from
> organizing a time that all 10 people can meet across x timezones (a
> thing unto itself). Its the community feedback period, giving people
> enough time to secure travel approval from their management, loading
> the sessions into the actual schedule app, and other print deadlines
> that force us to have everything set this far out.
>
> I will definitely help the ops community in whatever way I can! Do you
> have remote attendance set up for the meetup?
>
>
> Chris
>
> On Wed, Feb 27, 2019 at 2:29 PM Kendall Nelson
> <kennelson11(a)gmail.com <mailto:kennelson11@gmail.com>> wrote:
>
> Another- nother thought: You could take a look at what is
> submitted by project teams closer to the deadline and see if
> your ideas might fit well with theirs since they are looking
> for feedback from operators anyway. In the past I have always
> hoped for more engagement in the forum sessions I've submitted
> but only ever had one or two operators able to join us.
>
> -Kendall (diablo_rojo)
>
> On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson
> <kennelson11(a)gmail.com <mailto:kennelson11@gmail.com>> wrote:
>
> Hello :)
>
> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur
> <jimmy(a)openstack.org <mailto:jimmy@openstack.org>> wrote:
>
> Erik,
>
> I definitely understand the timeline is tight. One of
> the reasons that we publish the schedule so early is
> to enable community members to plan their schedule
> early, especially as there is more overlap with the
> main Summit Schedule in Denver. Additionally, travel
> approval is often predicated upon someone showing
> they're leading/moderating a session.
>
> Before publishing the schedule, we print a draft
> Forum schedule for community feedback and start
> promotion of the schedule, which we have to put up on
> the OpenStack website and apps at 5 weeks out.
> Extending the date beyond the 10th won't give the
> Forum Selection Committee enough time to complete
> those tasks.
>
> I think if the Ops team can come up with some high
> level discussion topics, we'll be happy to put some
> holds in the Forum schedule for Ops-specific content.
> diablo_rojo has also offered to attend some of the Ops
> sessions remotely as well, if that would help you all
> shape some things into actual sessions.
>
>
> I'm definitely happy to help as much as I can. If you'll
> have something set up that I can call into (zoom, webex,
> bluejeans, hangout, whatever), I definitely will. I could
> also read through etherpads you take notes in and help
> summarize things into forum proposals.
>
> Another thing to note is that whatever you/we submit, it
> doesn't have to be award winning :) Its totally possible
> to change session descriptions and edit who the speaker is
> later.
>
> Other random thought, I know Sean McGinnis has attended a
> lot of the Operators stuff in the past so maybe he could
> help narrow things down too? Not to sign him up for more
> work, but I know he's written a forum propsal or two in
> the past ;)
>
>
> I wish I could offer a further extension, but
> extending it another week would push too far into the
> process.
>
> Cheers,
> Jimmy
>> Erik McCormick <mailto:emccormick@cirrusseven.com>
>> February 27, 2019 at 12:43 PM
>> Jimmy,
>>
>> I won't even get home until the 10th much less have
>> time to follow up
>> with anyone. The formation of those sessions often
>> come from
>> discussions spawned at the meetup and expanded upon
>> later with folks
>> who could not attend. Could we at least get until
>> 3/17? I understand
>> your desire to finalize the schedule, but 6 weeks out
>> should be more
>> than enough time, no?
>>
>> Thanks,
>> Erik
>> Jimmy McArthur <mailto:jimmy@openstack.org>
>> February 27, 2019 at 12:04 PM
>> Hi Erik,
>>
>> We are able to extend the deadline to 11:59PM
>> Pacific, March 10th. That should give the weekend to
>> get any additional stragglers in and still allow the
>> Forum Programming Committee enough time to manage the
>> rest of the approval and publishing process in time
>> for people's travel needs, etc...
>>
>> For the Ops Meetup specifically, I'd suggest going a
>> bit broader with the proposals and offering to fill
>> in the blanks later. For example, if something comes
>> up and everyone agrees it should go to the Forum,
>> just submit before the end of the Ops session.
>> Kendall or myself would be happy to help you add
>> details a bit later in the process, should
>> clarification be necessary. We typically have enough
>> spots for the majority of proposed Forum sessions.
>> That's not a guarantee, but food for thought.
>>
>> Cheers,
>> Jimmy
>>
>>
>> _______________________________________________
>> Airship-discuss mailing list
>> Airship-discuss(a)lists.airshipit.org
>> <mailto:Airship-discuss@lists.airshipit.org>
>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>> Erik McCormick <mailto:emccormick@cirrusseven.com>
>> February 27, 2019 at 11:31 AM
>> Would it be possible to push the deadline back a
>> couple weeks? I expect there to be a few session
>> proposals that will come out of the Ops Meetup which
>> ends the day before the deadline. It would be helpful
>> to have a little time to organize and submit things
>> afterwards.
>>
>> Thanks,
>> Erik
>>
>> Jimmy McArthur <mailto:jimmy@openstack.org>
>> February 27, 2019 at 10:40 AM
>> Hi Everyone -
>>
>> A quick reminder that we are accepting Forum [1]
>> submissions for the 2019 Open Infrastructure Summit
>> in Denver [2]. Please submit your ideas through the
>> Summit CFP tool [3] through March 8th. Don't forget
>> to put your brainstorming etherpad up on the Denver
>> Forum page [4].
>>
>> This is not a classic conference track with speakers
>> and presentations. OSF community members
>> (participants in development teams, operators,
>> working groups, SIGs, and other interested
>> individuals) discuss the topics they want to cover
>> and get alignment on and we welcome your
>> participation. The Forum is your opportunity to help
>> shape the development of future project releases.
>> More information about the Forum [1].
>>
>> If you have questions or concerns, please reach out
>> to speakersupport(a)openstack.org
>> <mailto:speakersupport@openstack.org>.
>>
>> Cheers,
>> Jimmy
>>
>> [1] https://wiki.openstack.org/wiki/Forum
>> [2] https://www.openstack.org/summit/denver-2019/
>> [3]
>> https://www.openstack.org/summit/denver-2019/call-for-presentations
>> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
>> ___________________________________________
>>
>
> Hopefully that helps!
>
> -Kendall (diablo_rojo)
>
>
>
> --
> Chris Morgan <mihalis68(a)gmail.com <mailto:mihalis68@gmail.com>>
>
>
> - Kendall Nelson (diablo_rojo)
> _______________________________________________
> Airship-discuss mailing list
> Airship-discuss(a)lists.airshipit.org
> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
> Chris Morgan <mailto:mihalis68@gmail.com>
> February 27, 2019 at 3:25 PM
> I think the issue is that forum submissions building on what gets
> discussed in Berlin can't be expected to be finalised whilst attendees
> to the berlin meetup are still traveling. It's not that Erik can't
> pull these things together, in fact he's an old hand at this, it's
> more that this process isn't reasonable if there's so little time to
> collate what we learn in Berlin and feed it forward to Denver. Frankly
> it sounds like because the planning committee needs 5 weeks, Erik can
> have two days. Seem unfair.
>
> Chris
>
>
>
> --
> Chris Morgan <mihalis68(a)gmail.com <mailto:mihalis68@gmail.com>>
> Kendall Nelson <mailto:kennelson11@gmail.com>
> February 27, 2019 at 1:19 PM
> Another- nother thought: You could take a look at what is submitted by
> project teams closer to the deadline and see if your ideas might fit
> well with theirs since they are looking for feedback from operators
> anyway. In the past I have always hoped for more engagement in the
> forum sessions I've submitted but only ever had one or two operators
> able to join us.
>
> -Kendall (diablo_rojo)
>
> _______________________________________________
> Airship-discuss mailing list
> Airship-discuss(a)lists.airshipit.org
> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
> Kendall Nelson <mailto:kennelson11@gmail.com>
> February 27, 2019 at 1:14 PM
> Hello :)
>
> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur <jimmy(a)openstack.org
> <mailto:jimmy@openstack.org>> wrote:
>
> Erik,
>
> I definitely understand the timeline is tight. One of the reasons
> that we publish the schedule so early is to enable community
> members to plan their schedule early, especially as there is more
> overlap with the main Summit Schedule in Denver. Additionally,
> travel approval is often predicated upon someone showing they're
> leading/moderating a session.
>
> Before publishing the schedule, we print a draft Forum schedule
> for community feedback and start promotion of the schedule, which
> we have to put up on the OpenStack website and apps at 5 weeks
> out. Extending the date beyond the 10th won't give the Forum
> Selection Committee enough time to complete those tasks.
>
> I think if the Ops team can come up with some high level
> discussion topics, we'll be happy to put some holds in the Forum
> schedule for Ops-specific content. diablo_rojo has also offered
> to attend some of the Ops sessions remotely as well, if that would
> help you all shape some things into actual sessions.
>
>
> I'm definitely happy to help as much as I can. If you'll have
> something set up that I can call into (zoom, webex, bluejeans,
> hangout, whatever), I definitely will. I could also read through
> etherpads you take notes in and help summarize things into forum
> proposals.
>
> Another thing to note is that whatever you/we submit, it doesn't have
> to be award winning :) Its totally possible to change session
> descriptions and edit who the speaker is later.
>
> Other random thought, I know Sean McGinnis has attended a lot of the
> Operators stuff in the past so maybe he could help narrow things down
> too? Not to sign him up for more work, but I know he's written a forum
> propsal or two in the past ;)
>
>
> I wish I could offer a further extension, but extending it another
> week would push too far into the process.
>
> Cheers,
> Jimmy
>> Erik McCormick <mailto:emccormick@cirrusseven.com>
>> February 27, 2019 at 12:43 PM
>> Jimmy,
>>
>> I won't even get home until the 10th much less have time to follow up
>> with anyone. The formation of those sessions often come from
>> discussions spawned at the meetup and expanded upon later with folks
>> who could not attend. Could we at least get until 3/17? I understand
>> your desire to finalize the schedule, but 6 weeks out should be more
>> than enough time, no?
>>
>> Thanks,
>> Erik
>> Jimmy McArthur <mailto:jimmy@openstack.org>
>> February 27, 2019 at 12:04 PM
>> Hi Erik,
>>
>> We are able to extend the deadline to 11:59PM Pacific, March
>> 10th. That should give the weekend to get any additional
>> stragglers in and still allow the Forum Programming Committee
>> enough time to manage the rest of the approval and publishing
>> process in time for people's travel needs, etc...
>>
>> For the Ops Meetup specifically, I'd suggest going a bit broader
>> with the proposals and offering to fill in the blanks later. For
>> example, if something comes up and everyone agrees it should go
>> to the Forum, just submit before the end of the Ops session.
>> Kendall or myself would be happy to help you add details a bit
>> later in the process, should clarification be necessary. We
>> typically have enough spots for the majority of proposed Forum
>> sessions. That's not a guarantee, but food for thought.
>>
>> Cheers,
>> Jimmy
>>
>>
>> _______________________________________________
>> Airship-discuss mailing list
>> Airship-discuss(a)lists.airshipit.org
>> <mailto:Airship-discuss@lists.airshipit.org>
>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>> Erik McCormick <mailto:emccormick@cirrusseven.com>
>> February 27, 2019 at 11:31 AM
>> Would it be possible to push the deadline back a couple weeks? I
>> expect there to be a few session proposals that will come out of
>> the Ops Meetup which ends the day before the deadline. It would
>> be helpful to have a little time to organize and submit things
>> afterwards.
>>
>> Thanks,
>> Erik
>>
>> Jimmy McArthur <mailto:jimmy@openstack.org>
>> February 27, 2019 at 10:40 AM
>> Hi Everyone -
>>
>> A quick reminder that we are accepting Forum [1] submissions for
>> the 2019 Open Infrastructure Summit in Denver [2]. Please submit
>> your ideas through the Summit CFP tool [3] through March 8th.
>> Don't forget to put your brainstorming etherpad up on the Denver
>> Forum page [4].
>>
>> This is not a classic conference track with speakers and
>> presentations. OSF community members (participants in development
>> teams, operators, working groups, SIGs, and other interested
>> individuals) discuss the topics they want to cover and get
>> alignment on and we welcome your participation. The Forum is
>> your opportunity to help shape the development of future project
>> releases. More information about the Forum [1].
>>
>> If you have questions or concerns, please reach out to
>> speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>.
>>
>> Cheers,
>> Jimmy
>>
>> [1] https://wiki.openstack.org/wiki/Forum
>> [2] https://www.openstack.org/summit/denver-2019/
>> [3]
>> https://www.openstack.org/summit/denver-2019/call-for-presentations
>> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
>> ___________________________________________
>>
>
> Hopefully that helps!
>
> -Kendall (diablo_rojo)
> _______________________________________________
> Airship-discuss mailing list
> Airship-discuss(a)lists.airshipit.org
> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
Hello :)
On Wed, Feb 27, 2019 at 1:26 PM Chris Morgan <mihalis68(a)gmail.com> wrote:
> I think the issue is that forum submissions building on what gets
> discussed in Berlin can't be expected to be finalised whilst attendees to
> the berlin meetup are still traveling. It's not that Erik can't pull these
> things together, in fact he's an old hand at this, it's more that this
> process isn't reasonable if there's so little time to collate what we learn
> in Berlin and feed it forward to Denver. Frankly it sounds like because the
> planning committee needs 5 weeks, Erik can have two days. Seem unfair.
>
Honestly, the decision process doesn't take much time, aside from
organizing a time that all 10 people can meet across x timezones (a thing
unto itself). Its the community feedback period, giving people enough time
to secure travel approval from their management, loading the sessions into
the actual schedule app, and other print deadlines that force us to have
everything set this far out.
I will definitely help the ops community in whatever way I can! Do you have
remote attendance set up for the meetup?
> Chris
>
> On Wed, Feb 27, 2019 at 2:29 PM Kendall Nelson <kennelson11(a)gmail.com>
> wrote:
>
>> Another- nother thought: You could take a look at what is submitted by
>> project teams closer to the deadline and see if your ideas might fit well
>> with theirs since they are looking for feedback from operators anyway. In
>> the past I have always hoped for more engagement in the forum sessions I've
>> submitted but only ever had one or two operators able to join us.
>>
>> -Kendall (diablo_rojo)
>>
>> On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson <kennelson11(a)gmail.com>
>> wrote:
>>
>>> Hello :)
>>>
>>> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur <jimmy(a)openstack.org>
>>> wrote:
>>>
>>>> Erik,
>>>>
>>>> I definitely understand the timeline is tight. One of the reasons that
>>>> we publish the schedule so early is to enable community members to plan
>>>> their schedule early, especially as there is more overlap with the main
>>>> Summit Schedule in Denver. Additionally, travel approval is often
>>>> predicated upon someone showing they're leading/moderating a session.
>>>>
>>>> Before publishing the schedule, we print a draft Forum schedule for
>>>> community feedback and start promotion of the schedule, which we have to
>>>> put up on the OpenStack website and apps at 5 weeks out. Extending the date
>>>> beyond the 10th won't give the Forum Selection Committee enough time to
>>>> complete those tasks.
>>>>
>>>> I think if the Ops team can come up with some high level discussion
>>>> topics, we'll be happy to put some holds in the Forum schedule for
>>>> Ops-specific content. diablo_rojo has also offered to attend some of the
>>>> Ops sessions remotely as well, if that would help you all shape some things
>>>> into actual sessions.
>>>>
>>>
>>> I'm definitely happy to help as much as I can. If you'll have something
>>> set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I
>>> definitely will. I could also read through etherpads you take notes in and
>>> help summarize things into forum proposals.
>>>
>>> Another thing to note is that whatever you/we submit, it doesn't have to
>>> be award winning :) Its totally possible to change session descriptions and
>>> edit who the speaker is later.
>>>
>>> Other random thought, I know Sean McGinnis has attended a lot of the
>>> Operators stuff in the past so maybe he could help narrow things down too?
>>> Not to sign him up for more work, but I know he's written a forum propsal
>>> or two in the past ;)
>>>
>>>
>>>>
>>>> I wish I could offer a further extension, but extending it another week
>>>> would push too far into the process.
>>>>
>>>> Cheers,
>>>> Jimmy
>>>>
>>>> Erik McCormick <emccormick(a)cirrusseven.com>
>>>> February 27, 2019 at 12:43 PM
>>>>
>>>> Jimmy,
>>>>
>>>> I won't even get home until the 10th much less have time to follow up
>>>> with anyone. The formation of those sessions often come from
>>>> discussions spawned at the meetup and expanded upon later with folks
>>>> who could not attend. Could we at least get until 3/17? I understand
>>>> your desire to finalize the schedule, but 6 weeks out should be more
>>>> than enough time, no?
>>>>
>>>> Thanks,
>>>> Erik
>>>>
>>>> Jimmy McArthur <jimmy(a)openstack.org>
>>>> February 27, 2019 at 12:04 PM
>>>>
>>>> Hi Erik,
>>>>
>>>> We are able to extend the deadline to 11:59PM Pacific, March 10th.
>>>> That should give the weekend to get any additional stragglers in and still
>>>> allow the Forum Programming Committee enough time to manage the rest of the
>>>> approval and publishing process in time for people's travel needs, etc...
>>>>
>>>> For the Ops Meetup specifically, I'd suggest going a bit broader with
>>>> the proposals and offering to fill in the blanks later. For example, if
>>>> something comes up and everyone agrees it should go to the Forum, just
>>>> submit before the end of the Ops session. Kendall or myself would be happy
>>>> to help you add details a bit later in the process, should clarification be
>>>> necessary. We typically have enough spots for the majority of proposed
>>>> Forum sessions. That's not a guarantee, but food for thought.
>>>>
>>>> Cheers,
>>>> Jimmy
>>>>
>>>>
>>>> _______________________________________________
>>>> Airship-discuss mailing list
>>>> Airship-discuss(a)lists.airshipit.org
>>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>>>>
>>>> Erik McCormick <emccormick(a)cirrusseven.com>
>>>> February 27, 2019 at 11:31 AM
>>>> Would it be possible to push the deadline back a couple weeks? I expect
>>>> there to be a few session proposals that will come out of the Ops Meetup
>>>> which ends the day before the deadline. It would be helpful to have a
>>>> little time to organize and submit things afterwards.
>>>>
>>>> Thanks,
>>>> Erik
>>>>
>>>> Jimmy McArthur <jimmy(a)openstack.org>
>>>> February 27, 2019 at 10:40 AM
>>>> Hi Everyone -
>>>>
>>>> A quick reminder that we are accepting Forum [1] submissions for the
>>>> 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas
>>>> through the Summit CFP tool [3] through March 8th. Don't forget to put
>>>> your brainstorming etherpad up on the Denver Forum page [4].
>>>>
>>>> This is not a classic conference track with speakers and presentations.
>>>> OSF community members (participants in development teams, operators,
>>>> working groups, SIGs, and other interested individuals) discuss the topics
>>>> they want to cover and get alignment on and we welcome your participation.
>>>> The Forum is your opportunity to help shape the development of future
>>>> project releases. More information about the Forum [1].
>>>>
>>>> If you have questions or concerns, please reach out to
>>>> speakersupport(a)openstack.org.
>>>>
>>>> Cheers,
>>>> Jimmy
>>>>
>>>> [1] https://wiki.openstack.org/wiki/Forum
>>>> [2] https://www.openstack.org/summit/denver-2019/
>>>> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations
>>>> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
>>>> ___________________________________________
>>>>
>>>>
>>> Hopefully that helps!
>>>
>>> -Kendall (diablo_rojo)
>>>
>>
>
> --
> Chris Morgan <mihalis68(a)gmail.com>
>
- Kendall Nelson (diablo_rojo)
Erik,
I definitely understand the timeline is tight. One of the reasons that
we publish the schedule so early is to enable community members to plan
their schedule early, especially as there is more overlap with the main
Summit Schedule in Denver. Additionally, travel approval is often
predicated upon someone showing they're leading/moderating a session.
Before publishing the schedule, we print a draft Forum schedule for
community feedback and start promotion of the schedule, which we have to
put up on the OpenStack website and apps at 5 weeks out. Extending the
date beyond the 10th won't give the Forum Selection Committee enough
time to complete those tasks.
I think if the Ops team can come up with some high level discussion
topics, we'll be happy to put some holds in the Forum schedule for
Ops-specific content. diablo_rojo has also offered to attend some of
the Ops sessions remotely as well, if that would help you all shape some
things into actual sessions.
I wish I could offer a further extension, but extending it another week
would push too far into the process.
Cheers,
Jimmy
> Erik McCormick <mailto:emccormick@cirrusseven.com>
> February 27, 2019 at 12:43 PM
> Jimmy,
>
> I won't even get home until the 10th much less have time to follow up
> with anyone. The formation of those sessions often come from
> discussions spawned at the meetup and expanded upon later with folks
> who could not attend. Could we at least get until 3/17? I understand
> your desire to finalize the schedule, but 6 weeks out should be more
> than enough time, no?
>
> Thanks,
> Erik
> Jimmy McArthur <mailto:jimmy@openstack.org>
> February 27, 2019 at 12:04 PM
> Hi Erik,
>
> We are able to extend the deadline to 11:59PM Pacific, March 10th.
> That should give the weekend to get any additional stragglers in and
> still allow the Forum Programming Committee enough time to manage the
> rest of the approval and publishing process in time for people's
> travel needs, etc...
>
> For the Ops Meetup specifically, I'd suggest going a bit broader with
> the proposals and offering to fill in the blanks later. For example,
> if something comes up and everyone agrees it should go to the Forum,
> just submit before the end of the Ops session. Kendall or myself
> would be happy to help you add details a bit later in the process,
> should clarification be necessary. We typically have enough spots for
> the majority of proposed Forum sessions. That's not a guarantee, but
> food for thought.
>
> Cheers,
> Jimmy
>
>
> _______________________________________________
> Airship-discuss mailing list
> Airship-discuss(a)lists.airshipit.org
> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
> Erik McCormick <mailto:emccormick@cirrusseven.com>
> February 27, 2019 at 11:31 AM
> Would it be possible to push the deadline back a couple weeks? I
> expect there to be a few session proposals that will come out of the
> Ops Meetup which ends the day before the deadline. It would be helpful
> to have a little time to organize and submit things afterwards.
>
> Thanks,
> Erik
>
> Jimmy McArthur <mailto:jimmy@openstack.org>
> February 27, 2019 at 10:40 AM
> Hi Everyone -
>
> A quick reminder that we are accepting Forum [1] submissions for the
> 2019 Open Infrastructure Summit in Denver [2]. Please submit your
> ideas through the Summit CFP tool [3] through March 8th. Don't forget
> to put your brainstorming etherpad up on the Denver Forum page [4].
>
> This is not a classic conference track with speakers and
> presentations. OSF community members (participants in development
> teams, operators, working groups, SIGs, and other interested
> individuals) discuss the topics they want to cover and get alignment
> on and we welcome your participation. The Forum is your opportunity
> to help shape the development of future project releases. More
> information about the Forum [1].
>
> If you have questions or concerns, please reach out to
> speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>.
>
> Cheers,
> Jimmy
>
> [1] https://wiki.openstack.org/wiki/Forum
> [2] https://www.openstack.org/summit/denver-2019/
> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations
> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
> ___________________________________________
>
Hi Erik,
We are able to extend the deadline to 11:59PM Pacific, March 10th. That
should give the weekend to get any additional stragglers in and still
allow the Forum Programming Committee enough time to manage the rest of
the approval and publishing process in time for people's travel needs,
etc...
For the Ops Meetup specifically, I'd suggest going a bit broader with
the proposals and offering to fill in the blanks later. For example, if
something comes up and everyone agrees it should go to the Forum, just
submit before the end of the Ops session. Kendall or myself would be
happy to help you add details a bit later in the process, should
clarification be necessary. We typically have enough spots for the
majority of proposed Forum sessions. That's not a guarantee, but food
for thought.
Cheers,
Jimmy
> Erik McCormick <mailto:emccormick@cirrusseven.com>
> February 27, 2019 at 11:31 AM
> Would it be possible to push the deadline back a couple weeks? I
> expect there to be a few session proposals that will come out of the
> Ops Meetup which ends the day before the deadline. It would be helpful
> to have a little time to organize and submit things afterwards.
>
> Thanks,
> Erik
>
> Jimmy McArthur <mailto:jimmy@openstack.org>
> February 27, 2019 at 10:40 AM
> Hi Everyone -
>
> A quick reminder that we are accepting Forum [1] submissions for the
> 2019 Open Infrastructure Summit in Denver [2]. Please submit your
> ideas through the Summit CFP tool [3] through March 8th. Don't forget
> to put your brainstorming etherpad up on the Denver Forum page [4].
>
> This is not a classic conference track with speakers and
> presentations. OSF community members (participants in development
> teams, operators, working groups, SIGs, and other interested
> individuals) discuss the topics they want to cover and get alignment
> on and we welcome your participation. The Forum is your opportunity
> to help shape the development of future project releases. More
> information about the Forum [1].
>
> If you have questions or concerns, please reach out to
> speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>.
>
> Cheers,
> Jimmy
>
> [1] https://wiki.openstack.org/wiki/Forum
> [2] https://www.openstack.org/summit/denver-2019/
> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations
> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
> ___________________________________________
>
Hi Everyone -
A quick reminder that we are accepting Forum [1] submissions for the
2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas
through the Summit CFP tool [3] through March 8th. Don't forget to put
your brainstorming etherpad up on the Denver Forum page [4].
This is not a classic conference track with speakers and presentations.
OSF community members (participants in development teams, operators,
working groups, SIGs, and other interested individuals) discuss the
topics they want to cover and get alignment on and we welcome your
participation. The Forum is your opportunity to help shape the
development of future project releases. More information about the Forum
[1].
If you have questions or concerns, please reach out to
speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>.
Cheers,
Jimmy
[1] https://wiki.openstack.org/wiki/Forum
[2] https://www.openstack.org/summit/denver-2019/
[3] https://www.openstack.org/summit/denver-2019/call-for-presentations
[4] https://wiki.openstack.org/wiki/Forum/Denver2019
___________________________________________
Hello,
This is the pre-calling for presentations at the OpenInfra Day in Vietnam
this year. If you love to visit Hanoi <https://en.wikipedia.org/wiki/Hanoi>,
the capital of Vietnam, and share your passion for the Open Infrastructure
of any topic (container, CI, deployment, edge computing, etc.), please let
me know by replying to this email. Below is the tentative information of
the event:
- Date: 31 August 2019
- Location: Hanoi, Vietnam
We are working with the OpenStack Foundation to organize the Upstream
Institute at the day so this will be a great opportunity for potential
contributors to come and learn. There is also a couple of PTLs and projects
core members have shown their interest in visiting Hanoi for this event.
We will send out the official call-for-presentations after we've done with
the logistic vendors and It would be around the beginning of May or sooner.
If you have any questions, please do not hesitate to contact me.
See you in Hanoi :)
Bests,
On behalf of VietOpenInfra Group.
P/S: Have a look at our last OpenInfra Day: https://2018.vietopenstack.org/
--
*Trinh Nguyen*
*www.edlab.xyz <https://www.edlab.xyz>*
Good morning.
This week's gatekeepers are James and Rico.
https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota
Open PRs across the repos is up to 68. Let's see if we can bring that down this week.
There have been a couple of changes in the last week that unsettled the CIs a bit and we will need to work them through the system - so, thanks in advance for your patience whilst we iron out those wrinkles. In particular I'm thinking of:
- kernel updates to 4.19.x
- OBS repo name changes
Graham
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Hi Kata devs/users:
We have just published the first KCSA (Kata Containers Security
Advisories) about the impact of cve-2019-5736 on Kata Containers.
The CVE-2019-5736 does not affect Kata Containers. Kata Containers
does use the runc libcontainer library as part of its 'kata-agent' to
launch container workloads, but the kata-agent executable is a
permanently running application within the Kata Containers VM. Thus,
the exit/re-execute cycle utilised by CVE-2019-5736 to execute the
injected code is never undertaken.
It should be noted, if the exploit had escaped from the kata-agent,
the exploit code would have been executing inside the Kata Containers
VM as root, and would not have direct access to either the host system
or other container/pods.
It is highly likely Kata Containers will vendor in and adopt all
relevant libcontainer updates and changes, but given the 'copying'
nature of some fixes, a performance and resource impact review will be
undertaken.
For details about the KCSA, please see
https://github.com/kata-containers/community/blob/master/VMT/KCSA/KCSA-CVE-…
Cheers,
Tao
--
bergwolf(a)hyper.sh