[Airship-discuss] Nomating Drew Walters for Airship Core

Sunil Sood sunil.sood at ericsson.com
Wed Feb 27 23:32:32 UTC 2019


+1

Sunil Sood

-----Original Message-----
From: airship-discuss-request at lists.airshipit.org <airship-discuss-request at lists.airshipit.org> 
Sent: Wednesday, February 27, 2019 3:58 PM
To: airship-discuss at lists.airshipit.org
Subject: Airship-discuss Digest, Vol 9, Issue 14

Send Airship-discuss mailing list submissions to
	airship-discuss at lists.airshipit.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
or, via email, send a message with subject or body 'help' to
	airship-discuss-request at lists.airshipit.org

You can reach the person managing the list at
	airship-discuss-owner at lists.airshipit.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Airship-discuss digest..."


Today's Topics:

   1. Re: Nomating Drew Walters for Airship Core (EAGAN, SEAN)
   2. Re: Nomating Evgeny Li for Airship Core (EAGAN, SEAN)
   3. Re: Nomating Evgeny Li for Airship Core (MEADOWS, ALAN)
   4. Re: [all] [forum] Forum Submissions are open! (Kendall Nelson)


----------------------------------------------------------------------

Message: 1
Date: Wed, 27 Feb 2019 16:44:33 +0000
From: "EAGAN, SEAN" <se136c at att.com>
To: "MCEUEN, MATT" <MM9745 at att.com>,
	"airship-discuss at lists.airshipit.org"
	<airship-discuss at lists.airshipit.org>
Subject: Re: [Airship-discuss] Nomating Drew Walters for Airship Core
Message-ID:
	<5B9C5644A0B2414E90A7F40249CF6A9555374A98 at MOSTLS1MSGUSRFA.ITServices.sbc.com>
	
Content-Type: text/plain; charset="utf-8"

+1

Sean Eagan

From: MCEUEN, MATT
Sent: Tuesday, February 26, 2019 6:24 PM
To: airship-discuss at lists.airshipit.org
Subject: [Airship-discuss] Nomating Drew Walters for Airship Core

***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Airship team,

I'd like to nominate Drew Walters (dwalt) to become an Airship core reviewer.  Drew has significant experience with Armada, and has more recently developed a focus on the reference manifests and CI infrastructure in the Treasuremap project.  Drew has shown the quality and quantity of code reviews that demonstrate the value that he'll add as an Airship core, and he has also shown eagerness and leadership in growing the Airship community as a whole.

Following OpenStack norms, current Airship core reviewers have 7 days (till EOD 3/5) to respond to this email with a +1 or -1 vote.  Please consider this my +1.

Thanks,
Matt McEuen


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20190227/bab4adf4/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 27 Feb 2019 16:44:59 +0000
From: "EAGAN, SEAN" <se136c at att.com>
To: "MCEUEN, MATT" <MM9745 at att.com>,
	"airship-discuss at lists.airshipit.org"
	<airship-discuss at lists.airshipit.org>
Subject: Re: [Airship-discuss] Nomating Evgeny Li for Airship Core
Message-ID:
	<5B9C5644A0B2414E90A7F40249CF6A9555375AA8 at MOSTLS1MSGUSRFA.ITServices.sbc.com>
	
Content-Type: text/plain; charset="utf-8"

+1

Sean Eagan

From: MCEUEN, MATT
Sent: Tuesday, February 26, 2019 6:24 PM
To: airship-discuss at lists.airshipit.org
Subject: [Airship-discuss] Nomating Evgeny Li for Airship Core

***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Airship team,

I'd like to nominate Evgeny Li (evgenyl) to become an Airship core reviewer.  Evgeny has dug deep into Airship automation and CI in the Treasuremap and Airship-in-a-Bottle projects, with an eye toward improving our documentation and config overrides.  Evgeny has also provided a large number of high quality code reviews, and has proven his value as a reviewer.  In addition, he has demonstrated an eagerness to welcome folks into and grow the Airship community - he has previous experience ushering a project into the OpenStack community, and I welcome his help in applying what he's learned to making Airship successful.

Following OpenStack norms, current Airship core reviewers have 7 days (till EOD 3/5) to respond to this email with a +1 or -1 vote.  Please consider this my +1.

Thanks,
Matt McEuen



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20190227/a48d88ba/attachment-0001.html>

------------------------------

Message: 3
Date: Wed, 27 Feb 2019 21:44:09 +0000
From: "MEADOWS, ALAN" <am240k at att.com>
To: "EAGAN, SEAN" <se136c at att.com>, "MCEUEN, MATT" <MM9745 at att.com>,
	"airship-discuss at lists.airshipit.org"
	<airship-discuss at lists.airshipit.org>
Subject: Re: [Airship-discuss] Nomating Evgeny Li for Airship Core
Message-ID:
	<15C64B16127ACA46A5BD581D320C78816ACE6973 at MISOUT7MSGUSRCE.ITServices.sbc.com>
	
Content-Type: text/plain; charset="utf-8"

+1

From: EAGAN, SEAN
Sent: Wednesday, February 27, 2019 8:45 AM
To: MCEUEN, MATT <MM9745 at att.com>; airship-discuss at lists.airshipit.org
Subject: Re: [Airship-discuss] Nomating Evgeny Li for Airship Core

+1

Sean Eagan

From: MCEUEN, MATT
Sent: Tuesday, February 26, 2019 6:24 PM
To: airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>
Subject: [Airship-discuss] Nomating Evgeny Li for Airship Core

Airship team,

I'd like to nominate Evgeny Li (evgenyl) to become an Airship core reviewer.  Evgeny has dug deep into Airship automation and CI in the Treasuremap and Airship-in-a-Bottle projects, with an eye toward improving our documentation and config overrides.  Evgeny has also provided a large number of high quality code reviews, and has proven his value as a reviewer.  In addition, he has demonstrated an eagerness to welcome folks into and grow the Airship community - he has previous experience ushering a project into the OpenStack community, and I welcome his help in applying what he's learned to making Airship successful.

Following OpenStack norms, current Airship core reviewers have 7 days (till EOD 3/5) to respond to this email with a +1 or -1 vote.  Please consider this my +1.

Thanks,
Matt McEuen



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20190227/fccac18e/attachment-0001.html>

------------------------------

Message: 4
Date: Wed, 27 Feb 2019 13:57:42 -0800
From: Kendall Nelson <kennelson11 at gmail.com>
To: Chris Morgan <mihalis68 at gmail.com>
Cc: Jimmy McArthur <jimmy at openstack.org>, Erik McCormick
	<emccormick at cirrusseven.com>,  openstack-discuss at lists.openstack.org,
	"kata-dev at lists.katacontainers.io" <kata-dev at lists.katacontainers.io>,
	"starlingx-discuss at lists.starlingx.io"
	<starlingx-discuss at lists.starlingx.io>,
	"airship-discuss at lists.airshipit.org"
	<airship-discuss at lists.airshipit.org>,
	"zuul-discuss at lists.zuul-ci.org" <zuul-discuss at lists.zuul-ci.org>
Subject: Re: [Airship-discuss] [all] [forum] Forum Submissions are
	open!
Message-ID:
	<CAJ6yrQjV8=LyU5K3g3JpnDV1BC+s11U+UVmzG3ijJR5kG1A10Q at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello :)

On Wed, Feb 27, 2019 at 1:26 PM Chris Morgan <mihalis68 at 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 at 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 at gmail.com>
>> wrote:
>>
>>> Hello :)
>>>
>>> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur 
>>> <jimmy at 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 at 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 at 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 at lists.airshipit.org
>>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>>>>
>>>> Erik McCormick <emccormick at 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 at 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 at 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 at gmail.com>
>

- Kendall Nelson (diablo_rojo)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20190227/981f1b42/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Airship-discuss mailing list
Airship-discuss at lists.airshipit.org
http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss

------------------------------

End of Airship-discuss Digest, Vol 9, Issue 14
**********************************************


More information about the Airship-discuss mailing list