From doug at doughellmann.com  Fri Aug 17 17:31:41 2018
From: doug at doughellmann.com (Doug Hellmann)
Date: Fri, 17 Aug 2018 13:31:41 -0400
Subject: [openstack-tc] Fwd: Calendar placeholder for the OpenStack Board
 and Joint Leadership meetings, Berlin November 12 -All Day
References: <CY4PR18MB1637B6E5A5071AB2560E9B8DB33D0@CY4PR18MB1637.namprd18.prod.outlook.com>
Message-ID: <660E0300-C373-4D31-A16B-63B0F312CEB4@doughellmann.com>

TC members, if you are planning to attend the summit in Berlin please include this meeting on 12 November (the Monday before the summit) in your travel schedule.

Doug

> Begin forwarded message:
> 
> From: Alan Clark <ACLARK at suse.com>
> Subject: Calendar placeholder for the OpenStack Board and Joint Leadership meetings, Berlin November 12 -All Day 
> Date: August 17, 2018 at 1:03:46 PM EDT
> To: Allison Randal <allison at lohutok.net>, Anni Lai <anni.lai at huawei.com>, "Arkady_Kanevsky at DELL.com" <Arkady_Kanevsky at DELL.com>, Boris Renski <brenski at mirantis.com>, Brian Stein <Brian.Stein at rackspace.com>, ChangBo Guo <eric.guo at easystack.cn>, Egle Sigler <ushnishtha at hotmail.com>, Imad Sousou <imad.sousou at intel.com>, Johan Christenson <johan at citynetwork.se>, "Jonathan Bryce" <jonathan at openstack.org>, Joseph WANG <joseph.w at inwinstack.com>, "Julia Dechance (jbarbosa)" <jbarbosa at cisco.com>, Kandan Kathirvel <kk0563 at att.com>, Kenji Kaneshige <kaneshige.kenji at jp.fujitsu.com>, "Kurt Garloff (t-systems at garloff.de)" <t-systems at garloff.de>, Lauren Sell <lauren at openstack.org>, Lew Tucker <letucker at cisco.com>, Liana Greenberg <liana.greenberg at RACKSPACE.COM>, Mark Collier <mark at openstack.org>, "Mark McLoughlin" <Markmc at redhat.com>, Mark Radcliffe <Mark.Radcliffe at dlapiper.com>, "Prakash Ramchandran (pramchan at yahoo.com)" <pramchan at yahoo.com>, "Price, Christopher" <christopher.price at ericsson.com>, Rob Esker <esker at netapp.com>, "'ruanhe(Ruan HE)'" <ruanhe at tencent.com>, Shane Wang <shane.wang at intel.com>, Steven Dake <stdake at cisco.com>, "Taylor, Monty" <mordred at inaugust.com>, "Tim Bell" <tim.bell at cern.ch>, Doug Hellmann <doug at doughellmann.com>, "Mohammed Naser" <mnaser at vexxhost.com>
> 
> This is a placeholder for the OpenStack Board and Joint Leadership meetings at the Berlin OpenStack Summit on November 12.
>  
> Please block your calendar for 9am – 5pm Berlin timezone
>  
> This appointment will be updated at a later time with meeting location, agenda and additional information.
>  
> Thanks,
> AlanClark
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180817/acc7ec4e/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Mail Attachment.ics
Type: text/calendar
Size: 5541 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180817/acc7ec4e/attachment-0001.ics>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180817/acc7ec4e/attachment-0003.html>

From thierry at openstack.org  Wed Aug 22 09:40:03 2018
From: thierry at openstack.org (Thierry Carrez)
Date: Wed, 22 Aug 2018 11:40:03 +0200
Subject: [openstack-tc] Proposed PTG post-lunch presentation schedule
Message-ID: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>

Hi,

As mentioned on channel, we need to decide ASAP the content of 
post-lunch presentations at the PTG, if only to let the volunteers there 
know that they need to work on their content :) Based on the submissions 
on the etherpad, the current proposal is as follows:

Monday: Welcome to the PTG
Welcome / Ops meetup intro / Housekeeping / Community update / Set stage 
for the week / Present Stein goals (ttx, mnaser, kendallW)

Tuesday: Two presentation on tools
Storyboard demo (diablo_rojo), Simplifying backports with git-deps and 
git-explode (aspiers). Each will get 10min + 5min Q&A

Wednesday: Three general talks: Release management (smcginnis), Project 
navigator (jimmymcarthur), Tech vision statement intro (zaneb, cdent). 
Each will get 10min including Q&A.

Thursday: PTG : present and future
Future of PTGs in 2019 + feedback session on this PTG (jbryce, ttx)

Friday: Lightning talks
Sphinx in OpenStack (stephenfin) / Team updates... / Anything... Each 
will get 5min.

Let me know ASAP if there is any issue with this. Otherwise I'll post to 
the -dev list and communicate with the various speakers later this week.

-- 
Thierry


From doug at doughellmann.com  Wed Aug 22 12:45:04 2018
From: doug at doughellmann.com (Doug Hellmann)
Date: Wed, 22 Aug 2018 08:45:04 -0400
Subject: [openstack-tc] Proposed PTG post-lunch presentation schedule
In-Reply-To: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
References: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
Message-ID: <CB1D5679-BC28-47AA-B867-F245FE9D9092@doughellmann.com>



> On Aug 22, 2018, at 5:40 AM, Thierry Carrez <thierry at openstack.org> wrote:
> 
> Hi,
> 
> As mentioned on channel, we need to decide ASAP the content of post-lunch presentations at the PTG, if only to let the volunteers there know that they need to work on their content :) Based on the submissions on the etherpad, the current proposal is as follows:
> 
> Monday: Welcome to the PTG
> Welcome / Ops meetup intro / Housekeeping / Community update / Set stage for the week / Present Stein goals (ttx, mnaser, kendallW)
> 
> Tuesday: Two presentation on tools
> Storyboard demo (diablo_rojo), Simplifying backports with git-deps and git-explode (aspiers). Each will get 10min + 5min Q&A
> 
> Wednesday: Three general talks: Release management (smcginnis), Project navigator (jimmymcarthur), Tech vision statement intro (zaneb, cdent). Each will get 10min including Q&A.
> 
> Thursday: PTG : present and future
> Future of PTGs in 2019 + feedback session on this PTG (jbryce, ttx)
> 
> Friday: Lightning talks
> Sphinx in OpenStack (stephenfin) / Team updates... / Anything... Each will get 5min.
> 
> Let me know ASAP if there is any issue with this. Otherwise I'll post to the -dev list and communicate with the various speakers later this week.
> 
> -- 
> Thierry
> 
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc

This seems like a good program with plenty of variety and useful topics. +1



From fungi at yuggoth.org  Wed Aug 22 14:43:48 2018
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Wed, 22 Aug 2018 14:43:48 +0000
Subject: [openstack-tc] Proposed PTG post-lunch presentation schedule
In-Reply-To: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
References: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
Message-ID: <20180822144348.4xa2nipj77q3b372@yuggoth.org>

On 2018-08-22 11:40:03 +0200 (+0200), Thierry Carrez wrote:
[...]
> Friday: Lightning talks
> Sphinx in OpenStack (stephenfin) / Team updates... / Anything... Each will
> get 5min.
[...]

I like there's the possibility for teams to do an unconference sort
of agenda for these and just get up and talk about/present what they
worked on throughout the week.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180822/7afc0f75/attachment.sig>

From tony at bakeyournoodle.com  Thu Aug 23 00:00:44 2018
From: tony at bakeyournoodle.com (Tony Breeds)
Date: Thu, 23 Aug 2018 10:00:44 +1000
Subject: [openstack-tc] Proposed PTG post-lunch presentation schedule
In-Reply-To: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
References: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
Message-ID: <20180823000043.GI26778@thor.bakeyournoodle.com>

On Wed, Aug 22, 2018 at 11:40:03AM +0200, Thierry Carrez wrote:
> Hi,
> 
> As mentioned on channel, we need to decide ASAP the content of post-lunch
> presentations at the PTG, if only to let the volunteers there know that they
> need to work on their content :) Based on the submissions on the etherpad,
> the current proposal is as follows:
> 
> Monday: Welcome to the PTG
> Welcome / Ops meetup intro / Housekeeping / Community update / Set stage for
> the week / Present Stein goals (ttx, mnaser, kendallW)
> 
> Tuesday: Two presentation on tools
> Storyboard demo (diablo_rojo), Simplifying backports with git-deps and
> git-explode (aspiers). Each will get 10min + 5min Q&A
> 
> Wednesday: Three general talks: Release management (smcginnis), Project
> navigator (jimmymcarthur), Tech vision statement intro (zaneb, cdent). Each
> will get 10min including Q&A.
> 
> Thursday: PTG : present and future
> Future of PTGs in 2019 + feedback session on this PTG (jbryce, ttx)
> 
> Friday: Lightning talks
> Sphinx in OpenStack (stephenfin) / Team updates... / Anything... Each will
> get 5min.

Any chance one of these sessions can be replaced with a TC candidates
Q&A?  It seems like a great opportunity to me.

Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180823/db0f6fa6/attachment.sig>

From thierry at openstack.org  Thu Aug 23 08:04:42 2018
From: thierry at openstack.org (Thierry Carrez)
Date: Thu, 23 Aug 2018 10:04:42 +0200
Subject: [openstack-tc] Proposed PTG post-lunch presentation schedule
In-Reply-To: <20180823000043.GI26778@thor.bakeyournoodle.com>
References: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
 <20180823000043.GI26778@thor.bakeyournoodle.com>
Message-ID: <ca2b8c5c-fd11-13cd-b9e8-2a9bd563fb95@openstack.org>

Tony Breeds wrote:
> Any chance one of these sessions can be replaced with a TC candidates
> Q&A?  It seems like a great opportunity to me.

I'd say it's a bit late to add (it was not proposed on the etherpad), 
and it would need a full 30-min slot (if not more) to yield any 
interesting result... and I don't see which of the scheduled days we can 
really free up for that.

I think we should schedule that at another time (like at the end of one 
of the days, before some happy hour). Let me see what our options are...

-- 
Thierry Carrez (ttx)


From doug at doughellmann.com  Thu Aug 23 12:52:44 2018
From: doug at doughellmann.com (Doug Hellmann)
Date: Thu, 23 Aug 2018 08:52:44 -0400
Subject: [openstack-tc] Create Stein PTL election tag on
 openstack/governance
In-Reply-To: <20180726035938.GI30070@thor.bakeyournoodle.com>
References: <20180726035938.GI30070@thor.bakeyournoodle.com>
Message-ID: <924614F2-F94C-45A2-B849-CD9AC948A188@doughellmann.com>



> On Jul 25, 2018, at 11:59 PM, Tony Breeds <tony at bakeyournoodle.com> wrote:
> 
> Hello TC,
>    I'd like to request the creation of a tag on the
> openstack/governance repo for essentially freezing the repo and
> therefore defining the per-project deliverables and extra-ATCs.
> 
> Please create the tag aug-2018-elections[1]

We already have a tag with that name. The YAML file says sept-2018-elections, so I assume that’s just a typo.

> The following open changes: could potentially impact the election:
> https://review.openstack.org/#/q/status:open+project:openstack/governance+topic:project-update
> as each of these changes adds a repo to a project team, however given
> neither of them passes CI and has no Rollcall-Vote I think it's
> appropriate to exclude them from consideration for the Stein PTL
> election.

I approved https://review.openstack.org/#/c/592293/ <https://review.openstack.org/#/c/592293/> which should not have any effect since it retires a repo.

After that patch merged I tagged the new HEAD of master 0aa4de942ade7bda5667add0a57c62d578c709db with sept-2018-elections.

Doug

> 
> Yours Tony.
> [1] To match http://git.openstack.org/cgit/openstack/election/tree/configuration.yaml#n5
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180823/c1e1d7bc/attachment.html>

From doug at doughellmann.com  Thu Aug 23 13:03:40 2018
From: doug at doughellmann.com (Doug Hellmann)
Date: Thu, 23 Aug 2018 09:03:40 -0400
Subject: [openstack-tc] 2018 Denver PTG TC meetings
Message-ID: <11468203-E958-4070-B5ED-F06C1AD717A3@doughellmann.com>

Since the earlier thread was revived when Thierry flushed the moderation queue, and the only other place I think I mentioned it was in the weekly TC updates, I thought I should formally mention that the TC has set up 2 meetings during the week of the PTG.

Sunday from 13:00-17:00 we’ll meet to discuss some internal, reflective topics. This meeting is open (as usual), but the room we were able to find is small so please check the agenda before deciding to drop in.

Friday we will meet all day (or at least as long as our stamina allows by then) and the agenda includes a list of topics I thought would be more obviously interesting to a wider audience.

The location, time, and agenda details are in the etherpad: https://etherpad.openstack.org/p/tc-stein-ptg

Doug



From sean.mcginnis at gmx.com  Thu Aug 23 14:30:24 2018
From: sean.mcginnis at gmx.com (Sean McGinnis)
Date: Thu, 23 Aug 2018 09:30:24 -0500
Subject: [openstack-tc] Proposed PTG post-lunch presentation schedule
In-Reply-To: <ca2b8c5c-fd11-13cd-b9e8-2a9bd563fb95@openstack.org>
References: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
 <20180823000043.GI26778@thor.bakeyournoodle.com>
 <ca2b8c5c-fd11-13cd-b9e8-2a9bd563fb95@openstack.org>
Message-ID: <20180823143024.GA23060@sm-workstation>

On Thu, Aug 23, 2018 at 10:04:42AM +0200, Thierry Carrez wrote:
> Tony Breeds wrote:
> > Any chance one of these sessions can be replaced with a TC candidates
> > Q&A?  It seems like a great opportunity to me.
> 
> I'd say it's a bit late to add (it was not proposed on the etherpad), and it
> would need a full 30-min slot (if not more) to yield any interesting
> result... and I don't see which of the scheduled days we can really free up
> for that.
> 
> I think we should schedule that at another time (like at the end of one of
> the days, before some happy hour). Let me see what our options are...
> 

There was also a concern raised that doing something like this would give an
unfair advantage if any potential candidates were not able to attend the PTG in
person.


From fungi at yuggoth.org  Thu Aug 23 16:20:23 2018
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Thu, 23 Aug 2018 16:20:23 +0000
Subject: [openstack-tc] Create Stein PTL election tag on
 openstack/governance
In-Reply-To: <924614F2-F94C-45A2-B849-CD9AC948A188@doughellmann.com>
References: <20180726035938.GI30070@thor.bakeyournoodle.com>
 <924614F2-F94C-45A2-B849-CD9AC948A188@doughellmann.com>
Message-ID: <20180823162022.oalqrkcnllw7qdc3@yuggoth.org>

On 2018-08-23 08:52:44 -0400 (-0400), Doug Hellmann wrote:
> > On Jul 25, 2018, at 11:59 PM, Tony Breeds <tony at bakeyournoodle.com> wrote:
> > 
> > Hello TC,
> >    I'd like to request the creation of a tag on the
> > openstack/governance repo for essentially freezing the repo and
> > therefore defining the per-project deliverables and extra-ATCs.
> > 
> > Please create the tag aug-2018-elections[1]
> 
> We already have a tag with that name. The YAML file says
> sept-2018-elections, so I assume that’s just a typo.
[...]

Note the date on the original message. This spent a month in the
moderation queue. It was for the PTL elections not the TC election.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180823/60fe4c06/attachment-0001.sig>

From doug at doughellmann.com  Thu Aug 23 16:34:20 2018
From: doug at doughellmann.com (Doug Hellmann)
Date: Thu, 23 Aug 2018 12:34:20 -0400
Subject: [openstack-tc] Create Stein PTL election tag on
 openstack/governance
In-Reply-To: <20180823162022.oalqrkcnllw7qdc3@yuggoth.org>
References: <20180726035938.GI30070@thor.bakeyournoodle.com>
 <924614F2-F94C-45A2-B849-CD9AC948A188@doughellmann.com>
 <20180823162022.oalqrkcnllw7qdc3@yuggoth.org>
Message-ID: <6229D698-754A-457E-92EA-79BAD28EBA8F@doughellmann.com>



> On Aug 23, 2018, at 12:20 PM, Jeremy Stanley <fungi at yuggoth.org> wrote:
> 
> On 2018-08-23 08:52:44 -0400 (-0400), Doug Hellmann wrote:
>>> On Jul 25, 2018, at 11:59 PM, Tony Breeds <tony at bakeyournoodle.com> wrote:
>>> 
>>> Hello TC,
>>>   I'd like to request the creation of a tag on the
>>> openstack/governance repo for essentially freezing the repo and
>>> therefore defining the per-project deliverables and extra-ATCs.
>>> 
>>> Please create the tag aug-2018-elections[1]
>> 
>> We already have a tag with that name. The YAML file says
>> sept-2018-elections, so I assume that’s just a typo.
> [...]
> 
> Note the date on the original message. This spent a month in the
> moderation queue. It was for the PTL elections not the TC election.

D’oh.

Well, the September tag exists, but I suppose we can change that if we need to.

Doug




From fungi at yuggoth.org  Thu Aug 23 17:26:35 2018
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Thu, 23 Aug 2018 17:26:35 +0000
Subject: [openstack-tc] Create Stein PTL election tag on
 openstack/governance
In-Reply-To: <6229D698-754A-457E-92EA-79BAD28EBA8F@doughellmann.com>
References: <20180726035938.GI30070@thor.bakeyournoodle.com>
 <924614F2-F94C-45A2-B849-CD9AC948A188@doughellmann.com>
 <20180823162022.oalqrkcnllw7qdc3@yuggoth.org>
 <6229D698-754A-457E-92EA-79BAD28EBA8F@doughellmann.com>
Message-ID: <20180823172634.olylfoybpuhmzc6f@yuggoth.org>

On 2018-08-23 12:34:20 -0400 (-0400), Doug Hellmann wrote:
[...]
> Well, the September tag exists, but I suppose we can change that
> if we need to.

The election tags for PTL (aug-2018-elections) and TC
(sept-2018-elections) were subsequently created by placing the
request through other channels.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20180823/758ea0b3/attachment.sig>

From zbitter at redhat.com  Thu Aug 23 20:44:25 2018
From: zbitter at redhat.com (Zane Bitter)
Date: Thu, 23 Aug 2018 16:44:25 -0400
Subject: [openstack-tc] Proposed PTG post-lunch presentation schedule
In-Reply-To: <20180823143024.GA23060@sm-workstation>
References: <ee41c0d0-7cf4-c49d-196d-ac36ffc58881@openstack.org>
 <20180823000043.GI26778@thor.bakeyournoodle.com>
 <ca2b8c5c-fd11-13cd-b9e8-2a9bd563fb95@openstack.org>
 <20180823143024.GA23060@sm-workstation>
Message-ID: <c10bb0df-e9d5-f440-41bd-a87604ff65fc@redhat.com>

On 23/08/18 10:30, Sean McGinnis wrote:
> On Thu, Aug 23, 2018 at 10:04:42AM +0200, Thierry Carrez wrote:
>> Tony Breeds wrote:
>>> Any chance one of these sessions can be replaced with a TC candidates
>>> Q&A?  It seems like a great opportunity to me.
>>
>> I'd say it's a bit late to add (it was not proposed on the etherpad), and it
>> would need a full 30-min slot (if not more) to yield any interesting
>> result... and I don't see which of the scheduled days we can really free up
>> for that.
>>
>> I think we should schedule that at another time (like at the end of one of
>> the days, before some happy hour). Let me see what our options are...
>>
> 
> There was also a concern raised that doing something like this would give an
> unfair advantage if any potential candidates were not able to attend the PTG in
> person.

I haven't said anything up to this point, but TBH I have even more 
concerns than that.

Obviously on one level it would be really interesting to hear from the 
candidates, and if I were up for re-election I'd be interested in taking 
part. Just the fact that we'd have potentially a large fraction of the 
community engaged with the election process instead of only that subset 
who have time to seek it out on the -dev list is pretty exciting.

OTOH this is *not* representative of the duties of being a TC member. 
We've never done an event like this before and we're never going to one 
again. So we're just going to subject this one group of candidates to a 
one-off hazing in the form of an in-person real-time Q&A session (in 
English) with a live audience?

That doesn't seem conducive to getting a diversity of candidates.


From mnaser at vexxhost.com  Thu Aug 30 14:04:50 2018
From: mnaser at vexxhost.com (Mohammed Naser)
Date: Thu, 30 Aug 2018 07:04:50 -0700
Subject: [openstack-tc] Fwd: [OpenStack Foundation] OSF Open Infrastructure
	Projects
In-Reply-To: <7D737DDE-CB49-43DE-9181-686FB0E83AF5@openstack.org>
References: <7D737DDE-CB49-43DE-9181-686FB0E83AF5@openstack.org>
Message-ID: <CAEs876iQfgXnWCEf04rggvHWXTa=iqPxtdz4k71Qr6DJZ+CgtQ@mail.gmail.com>

Hi everyone:

In case you missed this email, this is an update from the foundation
regarding the current state of things.

Thanks!
Mohammed

---------- Forwarded message ---------
From: Jonathan Bryce <jonathan at openstack.org>
Date: Thu, Aug 30, 2018 at 6:48 AM
Subject: [OpenStack Foundation] OSF Open Infrastructure Projects
To: <foundation at lists.openstack.org>


Hi everyone,

I wanted to provide an update on how things have been progressing with
the strategic planning for the OpenStack Foundation (OSF) that we
kicked off in 2017 among the TC, UC and Board. Through the course of
those discussions last year, we identified several opportunities for
the Foundation and community. After the joint meeting in November of
2017, the Board of Directors authorized Foundation staff to start
organizing some activities around strategic focus areas and to pilot
new open infrastructure projects. At OpenStack Summit Sydney, we
announced a new integration strategy, shifting our focus from being
solely about the production of the OpenStack software, to more broadly
helping organizations embrace open infrastructure: using and combining
open source solutions to fill their needs in terms of IT
infrastructure. This involves finding common use cases, collaborating
across communities, building the required new technology and testing
everything end to end[1].

In December 2017, we launched our Kata Containers, our first pilot
project [2]. In the first half of 2018, we worked to get Kata off the
ground and set up Zuul as a standalone project, and more recently
started piloting 2 additional projects, Airship and StarlingX. Through
these pilots, we have learned a lot and are now ready to put more
structure around the future of our work with additional open
infrastructure projects. In June, the Board formed a working group to
develop a plan and the policies for this more formal structure. The
Board will be reviewing the output of the working group at upcoming
meetings, including in September, so now we are looking to get
feedback on some of the initial thoughts ahead of the next working
group and Board meetings.

As laid out at the end of last year, there are two main concepts that
will guide the efforts of the Foundation: strategic focus areas (SFAs)
and projects.

Strategic focus areas (SFA)

"Open infrastructure" is an ever-evolving construct, as the computing
needs of organizations evolve with the technology. SFAs are driven by
usage scenarios and help direct the OSF action to specific segments of
the open infrastructure market. The intent is to provide focus and
content for use cases without trying to shove every possible type of
cloud or deployment scenario into a single bucket. SFAs include all of
the activities to achieve a specific strategic outcome (e.g. hosting
projects, throwing events, building and managing community activities,
education, marketing.)

Defining SFAs is part of the regular strategic planning activities of
the OSF Board of Directors. Focus areas may be proposed, discussed,
approved or abandoned during strategic reviews. Those strategic
reviews should happen as-needed, but at least annually.

Current SFAs include datacenter cloud, container infrastructure, edge and CI/CD.

Projects

Projects address the need to build the required new technology to fill
the goals of our strategic focus areas.  The OSF enables those
projects to be successfully set up as open collaborations, by
providing IP management, a set of base collaboration rules (the 4
Opens) and upstream and downstream community support services. Open
source projects that do not wish to be set up as open collaborations
can still be included and integrated in open infrastructure solutions,
however they will see little benefit in being hosted by the OSF.

SFAs and projects do not form a hierarchy. A project does not "belong"
to an SFA, however all projects supported by the OSF help achieve the
goals of one or more of our defined SFAs, and all projects supported
by the OSF follow the 4 Opens. Projects may be composed of several
components or deliverables, as long as they are under a common defined
scope and governance. Projects go through several recognition stages
which define the level of engagement of OSF resources.

Open development hosting

OSF members already maintain a community-operated set of development
and CI services enabling open collaboration at a massive scale. As we
believe that open source software should be developed using open
source tools, these services use only free and open source software.
This project infrastructure embodies the 4 Opens and enables projects
to follow them. The infra team is working to provide these services
more broadly and in a non-OpenStack branded way to avoid the confusion
that sometimes happens now when all hosted code resides in OpenStack
namespaces.

Any open source project may be hosted here and does not involve any
recognition by the OSF.  For projects that are candidates to become
OSF-supported projects, we believe that they should start with code,
so hosting them on community infrastructure is a recommended prepatory
step.

Stage 1: Pilot projects

As part of meeting the goals of our strategic focus areas, the OSF
staff will evaluate projects that fill gaps in open infrastructure
adoption or enable specific use cases for OpenStack technologies. The
OSF staff (as represented by its Executive Director) can select pilot
projects where it identifies promising new technology pieces and
encourage them to be set up as an open collaboration following the 4
Opens.

The OSF staff then helps the pilot projects by establishing initial
branding, setting up project websites, guiding them to set up proper
governance, and understanding and adopting the 4 Opens. Such pilot
projects may call themselves "a project supported by the OSF". Current
pilot projects are Kata containers, Zuul, Airship, and StarlingX.

Stage 2: Confirmed projects

Within 18 months, a pilot project will be reviewed by the Board, in
order to decide on long-term investment of OSF resources to support
it.

The Board will review the strategic alignment of the project with the
Foundation's SFAs, but also their progress in setting up an effective
open collaboration. To that effect, the project first needs to have
set up a governance model and have produced at least one release since
it was selected as a pilot. The Board will take community input in
order to inform its decision, in particular, from the technical
leadership of existing OSF projects, in terms of complementarity, and
4 Opens adoption. It should also seek the input from open
infrastructure users in terms of SFA alignment.

At that point the Board may decide to confirm the project as a
long-term OSF investment, abandon the pilot or defer its decision.

Confirmed projects may call themselves "a top-level project under the
OSF". Currently, only the OpenStack project has been recognized by the
OSF board (under the bylaws) as a long-term investement for the OSF
and therefore belongs to that category.

This represents the basic structure of our current thinking after a
few iterations. The next Board meeting will be September 18 and we
will review this at that meeting so we can move to fleshing out the
detailed work that needs to be done to finalize this around the
OpenStack Summit Berlin (potential bylaws changes for instance).

Thanks,

Jonathan

1. http://lists.openstack.org/pipermail/foundation/2017-November/002532.html
2. http://lists.openstack.org/pipermail/foundation/2017-December/002541.html
_______________________________________________
Foundation mailing list
Foundation at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation


-- 
Mohammed Naser — vexxhost
-----------------------------------------------------
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mnaser at vexxhost.com
W. http://vexxhost.com