{"id":8166,"date":"2017-09-29T18:46:47","date_gmt":"2017-09-29T23:46:47","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=8166"},"modified":"2017-09-29T18:54:31","modified_gmt":"2017-09-29T23:54:31","slug":"developer-mailing-list-digest-september-23-29-2017","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/developer-mailing-list-digest-september-23-29-2017\/","title":{"rendered":"Developer Mailing List Digest September 23-29 2017"},"content":{"rendered":"<p class=\"lead\"><b>Summaries<\/b><\/p>\n<ul>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/122679.html\">TC Report 39<\/a><\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/122819.html\">Release countdown for week R-21, September 29 &#8211; October 6<\/a><\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/122879.html\">Technical committee status update, September 29<\/a><\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/122883.html\">Placement\/resource providers update 36<\/a><\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/122805.html\">POST \/api-sig\/news<\/a><\/li>\n<\/ul>\n<p><b>Sydney Forum<\/b><\/p>\n<p><b>General Links<\/b><\/p>\n<ul>\n<li><a href=\"https:\/\/wiki.openstack.org\/wiki\/Forum\">What the heck is the form?<\/a><\/li>\n<li>When: November 6-8, 2017<\/li>\n<li>Where: OpenStack Summit in Sydney Australia<\/li>\n<li>Register for <a href=\"https:\/\/www.openstack.org\/summit\/sydney-2017\/\">The OpenStack Sydney Summit<\/a> and show up!<\/li>\n<li>Deadline for topic sessions was September 29th UTC by this <a href=\"http:\/\/forumtopics.openstack.org\/\">submission form<\/a>.<\/li>\n<li><a href=\"https:\/\/wiki.openstack.org\/wiki\/Forum\/Sydney2017\">All Sydney Forum etherpads<\/a><\/li>\n<\/ul>\n<p><b>Etherpads (copied from Sydney Forum wiki)<\/b><\/p>\n<p><b>Catch-alls<\/b><\/p>\n<p>If you want to post an idea, but aren\u2019t working with a specific team or working group, you can use these:<\/p>\n<ul>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/SYD-TC-brainstorming\">Technical Committee Catch-all<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/SYD-UC-brainstorming\">User Committee Catch-all<\/a><\/li>\n<\/ul>\n<p><b>Etherpads from Teams and Working Groups<\/b><\/p>\n<ul>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/SYD-nova-brainstorming\">Nova<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/cinder-sydney-forum-topics\">Cinder<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/SYD-ops-session-ideas\">Ops Meetups Team<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/osa-sydney-summit-planning\">OpenStack Ansible<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/self-healing-rocky-forum\">Self-healing SIG<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/qos-talk-sydney\">Neutron Quality-Of-Service Discussion<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/qa-sydney-forum-topics\">QA Team<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/watcher-Sydney-meetings\">Watcher<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/sig-k8s-sydney-forum-topics\">SIG K8s<\/a><\/li>\n<li><a href=\"https:\/\/etherpad.openstack.org\/p\/kolla-sydney-forum-topics\">Kolla<\/a><\/li>\n<\/ul>\n<p><b>Garbage Patches for Simple Typos Fixes<\/b><\/p>\n<ul>\n<li>There is some agreement that we as a community have to do something beyond mentoring new developers.\n<ul>\n<li>Others have mentioned that some companies are doing this to game the system in other communities besides OpenStack.\n<ul>\n<li>Gain: show a high contribution level was \u201clow quality\u201d patches.<\/li>\n<\/ul>\n<\/li>\n<li>Some people in the community want to put a stop to this figuratively with a stop sign, otherwise, things will never improve. If we don&#8217;t do something now we are hurting everyone, including those developers who could have done more meaningful contributions.<\/li>\n<li>Others would like before we go into creating harsh processes, we need to collect the data to show other times to provide guidance I Have not worked.<\/li>\n<li>We have a lot of anecdotal information right now that we need to collect and summarize.<\/li>\n<li>If the results show that there are clear abuses, rather than misunderstandings, then we can use that data to design effective blocks without hurting other contributors or creating a reputation that our community is not welcoming.<\/li>\n<\/ul>\n<\/li>\n<li>Some are unclear why there is so much outrage about these patches, to begin with. They are fixing real things.\n<ul>\n<li>Maybe there is a CI cost, but the faster they are merged the less likely someone is to propose it in the future which keeps the CI cost down.<\/li>\n<li>If people are deeply concerned about CI resources, step one is to give us a better accounting into their existing system to see where resources are currently spent.<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/thread.html#122472\">Thread<\/a><\/li>\n<\/ul>\n<p><b>Status of the Stewardship Working Group<\/b><\/p>\n<ul>\n<li>The stewardship working group was created after the first session of leadership training that the Technical Committee, User Committee, Board and other community members were invited to participate in 2016.<\/li>\n<li>Follow-up on what we learned at ZingTrain and push adoption of the tools we discovered there.<\/li>\n<li>While we did (and continue)\n<ul>\n<li>The activity of the workgroup mostly died when we decided to experiment getting rid of weekly meetings for greater inclusion.<\/li>\n<li>Lost original leadership.<\/li>\n<\/ul>\n<\/li>\n<li>The workgroup is dormant until someone steps up and leads it again.<\/li>\n<li>Join us on IRC Freenode in channel openstack-swg if interested.<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/122868.html\">Message<\/a><\/li>\n<\/ul>\n<p><b>Improving the Process for Release Marketing<\/b><\/p>\n<ul>\n<li>Release marketing is a critical heart for sharing what&#8217;s new with each release.<\/li>\n<li>Let&#8217;s work together on reworking how the marketing community and projects work together to make the release communications happen.<\/li>\n<li>Having multiple, repetitive demands to summarize&#8221; top features&#8221; during release time can be a pester, and having to recollect the information each time isn&#8217;t an effective use of time.\n<ul>\n<li>Being asked to make a polished, &#8220;Press\u2013Friendly&#8221; message out of release can feel far outside of the PTL\u2019s Focus areas or skills.<\/li>\n<li>Technical content marketers, attempting to find the key features from release notes, mailing lists, specifications, roadmaps, whatever means interesting features are sometimes overlooked.<\/li>\n<\/ul>\n<\/li>\n<li>To address this gap, the release team and foundation marketing team proposed collecting information as part of the release tagging process.\n<ul>\n<li>We will collect from deliverable files to provide highlights for the series (about three items).<\/li>\n<li>The text will be used to build a landing page on <a href=\"http:\/\/release.openstack.org\">release.openstack.org<\/a> that shows the&#8221;Key features&#8221; flagged by PTL\u2019s that the marketing teams should be looking at during release communication times.\n<ul>\n<li>This page will link to the <a href=\"https:\/\/release.openstack.org\">release notes<\/a> so marketers can gather additional information.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/122678.html\">Message<\/a><\/li>\n<\/ul>\n<p><b>Simplification in OpenStack<\/b><\/p>\n<ul>\n<li>Two camps appear: people that want to see OpenStack as a product with a way of doing deployments and the people who want to focus on configuration management tools.\n<ul>\n<li>One person gives an example of using both Ubuntu MAAS and Puppet. The puppet solution allowed for using existing deployment methodologies unlike the former.<\/li>\n<\/ul>\n<\/li>\n<li>We should start promoting and using a single solution for the bulk of the community efforts. Right now we do that with Devstack as a reference implementation that nobody should use for anything but dev\/test.\n<ul>\n<li>This sort of idea could make other deployment efforts relevant.<\/li>\n<\/ul>\n<\/li>\n<li>Kolla came up at the PTG: scenario-based testing and documentation based on different\u00a0 \u201cconstellations&#8221; or use cases.\n<ul>\n<li>Puppet has been doing <a href=\"https:\/\/github.com\/openstack\/puppet-openstack-integration\">this<\/a> and Triple-o has been doing <a href=\"https:\/\/docs.openstack.org\/tripleo-quickstart\/latest\/feature-configuration.html\">this<\/a>.<\/li>\n<li>If you break down actual use cases, most people want nova (qemu+KVM), neutron (vxlan, potentially VLAN), Cinder (ceph).\n<ul>\n<li>If we agreed to cover 90% of users, that&#8217;ll boil down to 4 to 5 different \u201cconstellations.\u201d<\/li>\n<\/ul>\n<\/li>\n<li>Someone has been working on a local testing environment, and it boils down to <a href=\"https:\/\/github.com\/test-kitchen\/test-kitchen\/issues\/873\">this<\/a>.<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-September\/thread.html#122075\">Thread<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Summaries TC Report 39 Release countdown for week R-21, September 29 &#8211; October 6 Technical committee status update, September 29 Placement\/resource providers update 36 POST \/api-sig\/news Sydney Forum General Links What the heck is the form? When: November 6-8, 2017 Where: OpenStack Summit in Sydney Australia Register for The OpenStack Sydney Summit and show up!&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/developer-mailing-list-digest-september-23-29-2017\/\" class=\"more-link\" title=\"Read Developer Mailing List Digest September 23-29 2017\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":82,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8166"}],"collection":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/users\/82"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=8166"}],"version-history":[{"count":5,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8166\/revisions"}],"predecessor-version":[{"id":8171,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8166\/revisions\/8171"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=8166"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=8166"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=8166"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}