<div dir="ltr"><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Mike Perez</b> <span dir="ltr"><<a href="mailto:thingee@gmail.com">thingee@gmail.com</a>></span><br>Date: Mon, Mar 5, 2018 at 5:15 PM<br>Subject: [Openstack-sigs] [forum] Brainstorming Topics for Vancouver 2018<br>To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>Cc: <a href="mailto:openstack-sigs@lists.openstack.org">openstack-sigs@lists.openstack.org</a>, <a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>, <a href="mailto:user-committee@list.openstack.org">user-committee@list.openstack.org</a><br><br><br>Hi all,<br>
<br>
Welcome to the topic selection process for our Forum in Vancouver. Note that<br>
this is not a classic conference track with speakers and presentations.<br>
OpenStack community members (participants in development teams, SIGS, working<br>
groups, and other interested individuals) discuss the topics they want to cover<br>
and get alignment on and we welcome your participation.<br>
<br>
The Forum is for the entire community to come together, to create a<br>
neutral space rather than having separate "ops" and "dev" days. Users should<br>
should aim to come with ideas for for the next release, gather feedback on the<br>
past version and have strategic discussions that go beyond just one release<br>
cycle. We aim to ensure the broadest coverage of topics that will allow for<br>
multiple parts of the community getting together to discuss key areas within<br>
our community/projects.<br>
<br>
There are two stages to the brainstorming:<br>
<br>
1. Starting today, set up an etherpad with your team and start<br>
discussing ideas you'd like to talk about at the Forum and work out<br>
which ones to submit - just like you did prior to the design summit.<br>
<br>
2. Then, in a couple of weeks, we will open up a more formal web-based<br>
tool for you to submit abstracts for the most popular sessions that came<br>
out of your brainstorming.<br>
<br>
Make an etherpad and add it to the list at:<br>
<a href="https://wiki.openstack.org/wiki/Forum/Vancouver2018" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/Forum/Vancouver2018</a><br>
<br>
One key thing we'd like to see (as always?) is cross-project<br>
collaboration, and discussion between every area of the community. Try<br>
to see if there is an interested working group on the user side to add<br>
to your ideas.<br>
<br>
Examples of typical discussions that include multiple parts of the<br>
community getting together to discuss:<br>
<br>
* Strategic, whole-of-community discussions, to think about the big<br>
picture, including beyond just one release cycle and new technologies<br>
o eg Making OpenStack One Platform for containers/VMs/Bare Metal<br>
(Strategic session) the entire community congregates to share<br>
opinions on how to make OpenStack achieve its integration engine<br>
goal<br>
* Cross-project sessions, in a similar vein to what has happened at<br>
past design summits, but with increased emphasis on issues that are<br>
of relevant to all areas of the community<br>
o eg Rolling Upgrades at Scale (Cross-Project session) -- the<br>
Large Deployments Team collaborates with Nova, Cinder and<br>
Keystone to tackle issues that come up with rolling upgrades<br>
when there's a large number of machines.<br>
* Project-specific sessions, where developers can ask users specific<br>
questions about their experience, users can provide feedback from<br>
the last release and cross-community collaboration on the priorities<br>
and 'blue sky' ideas for the next release.<br>
o eg Neutron Pain Points (Project-Specific session) --<br>
Co-organized by neutron developers and users. Neutron developers<br>
bring some specific questions they want answered, Neutron users<br>
bring feedback from the latest release and ideas about the future.<br>
<br>
Think about what kind of session ideas might end up as:<br>
Project-specific, cross-project or strategic/whole-of-community<br>
discussions. There'll be more slots for the latter two, so do try and<br>
think outside the box!<br>
<br>
This part of the process is where we gather broad community consensus -<br>
in theory the second part is just about fitting in as many of the good<br>
ideas into the schedule as we can.<br>
<br>
Further details about the forum can be found at:<br>
<a href="https://wiki.openstack.org/wiki/Forum" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/Forum</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Mike Perez (thingee)<br>
</font></span><br>______________________________<wbr>_________________<br>
openstack-sigs mailing list<br>
<a href="mailto:openstack-sigs@lists.openstack.org">openstack-sigs@lists.<wbr>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-sigs</a><br>
<br></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-size:small"><div dir="ltr"><div dir="ltr">Kind regards,<br><br>Melvin Hillsman</div><div dir="ltr"><a href="mailto:mrhillsman@gmail.com" style="color:rgb(17,85,204)" target="_blank">mrhillsman@gmail.com</a><br>mobile: (832) 264-2646<br></div></div></div></div></div></div></div></div></div>
</div>