On 2018-09-06 15:03:52 -0500 (-0500), Matt Riedemann wrote:

On 9/6/2018 2:56 PM, Jeremy Stanley wrote:

...

On 2018-09-06 14:31:01 -0500 (-0500), Matt Riedemann wrote:

...

On 8/29/2018 1:08 PM, Jim Rollenhagen wrote:

...

On Wed, Aug 29, 2018 at 12:51 PM, Jimmy McArthur <jimmy@openstack.org <mailto:jimmy@openstack.org>> wrote: <snip>

Examples of typical sessions that make for a great Forum:

Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies

e.g. OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal

Just to clarify some speculation going on in IRC: this is an example, right? Not a new thing being announced?

// jim FYI for those that didn't see this on the other ML:

http://lists.openstack.org/pipermail/foundation/2018-August/002617.html [...]

While I agree that's a great post to point out to all corners of the community, I don't see what it has to do with whether "OpenStack One Platform for containers/VMs/Bare Metal" was an example forum topic.

Because if I'm not mistaken it was the impetus for the hullabaloo in the tc channel that was related to the foundation ML post.

It would be more accurate to say that community surprise over the StarlingX mention in Vancouver keynotes caused some people to (either actually or merely in half-jest) start looking for subtext everywhere indicating the next big surprise announcement. The discussion[*] in #openstack-tc readily acknowledged that most of its participants didn't think "OpenStack One Platform for containers/VMs/Bare Metal" was an actual proposal for a forum discussion much less announcement of a new project, but were just looking for an opportunity to show feigned alarm and sarcasm. The most recent discussion[**] leading up to the foundation ML "OSF Open Infrastructure Projects" update occurred the previous week. That E-mail did go out the day after the forum topic brainstorming example discussion, but was unrelated (and already in the process of being put together by then). [*] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-... [**] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-... -- Jeremy Stanley