<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"></head><body
alink="#EE0000" bgcolor="#FFFFFF" link="#2057EF" text="#000000"
vlink="#551A8B">
Hi all,<br>
<br>
Welcome to the topic selection process for our Forum in Sydney. If
you've participated in the design summit before, this should seem pretty
comfortable. If not, note that this is not a classic conference track
with speakers and presentations. OpenStack community members
(participants in development teams, working groups, and other interested
individuals) discuss the topics they want to cover and get alignment on
and we welcome your participation.<br>
<br>
The Forum is for the entire community to come together, to create a
neutral space rather than having separate “ops” and “dev” days. Sydney
marks the start of Rocky's release cycle, where ideas and requirements
will be gathered. Users should aim to come armed with feedback from
Augusts's Pike release if at all possible. We aim to ensure the broadest
coverage of topics that will allow for multiple parts of the community
getting together to discuss key areas within our community/projects.<br>
<br>
<span style="font-weight: bold;">There are two stages to the
brainstorming:</span><br>
<br>
<div style="margin-left: 40px;">1. Starting today, set up an etherpad
with your team and start discussing ideas you'd like to talk about at
the Forum and work out which ones to submit - just like you did prior to
the design summit.<br>
</div>
<br>
<div style="margin-left: 40px;">2. Then, in a couple of weeks, we will
open up a more formal web-based tool for you to submit abstracts for
the most popular sessions that came out of your brainstorming.<br>
</div>
<br>
Make an etherpad and add it to the list at: <a
href="https://wiki.openstack.org/wiki/Forum/Sydney2017">https://wiki.openstack.org/wiki/Forum/Sydney2017</a><br>
<br>
One key thing we'd like to see (as always?) is cross-project
collaboration, and discussion between every area of the community. Try
to see if there is an interested working group on the user side to add
to your ideas.<br>
<br>
<span style="font-weight: bold;">Examples of typical discussions that
include multiple parts of the community getting together to discuss:</span><br>
<ul>
<li><span style="font-weight: bold;">Strategic, whole-of-community
discussions</span>, to think about the big picture, including beyond
just one release cycle and new technologies</li>
<ul>
<li><span style="font-style: italic;">eg Making OpenStack One
Platform for containers/VMs/Bare Metal</span> (Strategic session) the
entire community congregates to share opinions on how to make OpenStack
achieve its integration engine goal</li>
</ul>
<li><span style="font-weight: bold;">Cross-project sessions</span>,
in a similar vein to what has happened at past design summits, but with
increased emphasis on issues that are of relevant to all areas of the
community</li>
<ul>
<li><span style="font-style: italic;">eg Rolling Upgrades at Scale
(Cross-Project session) </span>– the Large Deployments Team
collaborates with Nova, Cinder and Keystone to tackle issues that come
up with rolling upgrades when there’s a large number of machines.</li>
</ul>
<li><span style="font-weight: bold;">Project-specific sessions</span>,
where developers can ask users specific questions about their
experience, users can provide feedback from the last release and
cross-community collaboration on the priorities and ‘blue sky’ ideas for
the next release.</li>
<ul>
<li><span style="font-style: italic;">eg Neutron Pain Points
(Project-Specific session)</span> – Co-organized by neutron developers
and users. Neutron developers bring some specific questions they want
answered, Neutron users bring feedback from the latest release and ideas
about the future.</li>
</ul>
</ul>
Think about what kind of session ideas might end up as:
Project-specific, cross-project or strategic/whole-of-community
discussions. There'll be more slots for the latter two, so do try and
think outside the box!<br>
<br>
This part of the process is where we gather broad community consensus -
in theory the second part is just about fitting in as many of the good
ideas into the schedule as we can.<br>
<br>
Further details about the forum can be found at: <a
href="https://wiki.openstack.org/wiki/Forum">https://wiki.openstack.org/wiki/Forum</a><br>
<br>
Thanks all!<br>
Jimmy McArthur, on behalf of the OpenStack Foundation and Technical
Committee
</body>
</html>