{"id":8235,"date":"2017-12-16T13:48:49","date_gmt":"2017-12-16T19:48:49","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=8235"},"modified":"2017-12-16T13:48:49","modified_gmt":"2017-12-16T19:48:49","slug":"developer-mailing-list-digest-december-9-15th","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/developer-mailing-list-digest-december-9-15th\/","title":{"rendered":"Developer Mailing List Digest December 9-15th"},"content":{"rendered":"<div id=\"magicdomid7508\" class=\"ace-line\">\n<h2>Success Bot Says<\/h2>\n<\/div>\n<div id=\"magicdomid635\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">mordred on #openstack-sdks: &#8220;Finished the shade transition to pure REST away from client libs&#8221; [0]<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid630\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Tell us yours in OpenStack IRC channels using the command &#8220;#success &lt;comment&gt;&#8221;<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid631\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">More: <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"https:\/\/wiki.openstack.org\/wiki\/Successes\">https:\/\/wiki.openstack.org\/wiki\/Successes<\/a><\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid453\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid4709\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[0] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/eavesdrop.openstack.org\/irclogs\/%23openstack-sdks\/%23openstack-sdks.2017-12-04.log.html\">http:\/\/eavesdrop.openstack.org\/irclogs\/%23openstack-sdks\/%23openstack-sdks.2017-12-04.log.html<\/a><\/span><\/div>\n<div id=\"magicdomid4711\" class=\"ace-line\"><\/div>\n<h2 id=\"magicdomid4743\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Community Summaries<\/span><\/h2>\n<div id=\"magicdomid5014\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">TC report 50 [0]<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid5015\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">POST \/api-sig\/news [1]<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid5016\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Release countdown [2]<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid5017\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Technical Committee Status Update [3]<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid5037\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Resource Providers Update 45 [4]<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid4736\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid4806\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[0] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125434.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125434.html<\/a><\/span><\/div>\n<div id=\"magicdomid4881\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[1] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125605.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125605.html<\/a><\/span><\/div>\n<div id=\"magicdomid4961\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[2] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125610.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125610.html<\/a><\/span><\/div>\n<div id=\"magicdomid5038\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[3] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125610.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125610.html<\/a><\/span><\/div>\n<div id=\"magicdomid5043\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[4] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125643.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125643.html<\/a><\/span><\/div>\n<div id=\"magicdomid640\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid690\" class=\"ace-line\">\n<h2><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Switching to Longer Development Cycles<\/span><\/h2>\n<\/div>\n<div id=\"magicdomid1122\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Our self-imposed rhythm no longer matches our natural pace. Our elections, feature freezes feel like they&#8217;re around the corner, and due to that, we&#8217;re losing time from them, as multiple people have stated. The pace was designed around more people contributing full time to OpenStack, but lately, we have composite jobs, or were participating in multiple communities (which is great!).<\/span><\/div>\n<div id=\"magicdomid1124\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid1133\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">It means:<\/span><\/div>\n<div id=\"magicdomid1610\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">One OpenStack coordinated release per year.<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid1611\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Maintain one stable branch per year.<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid1612\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Elect PTLs once a year.<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid1613\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">One set of community goals per year.<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid1614\" class=\"ace-line\">\n<ul class=\"list-bullet1\">\n<li><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">One PTG per year.<\/span><\/li>\n<\/ul>\n<\/div>\n<div id=\"magicdomid1404\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid1910\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Any project that still wants to release often can use the cycle-with-intermediary release model [0]. At a minimum, we&#8217;ll release once a year. Teams can choose to revive midcycle if they need to meet more than the one PTG each year. We&#8217;ll have more time for community-wide goals, so we will have more time to complete or even set more ambitious goals.<\/span><\/div>\n<div id=\"magicdomid1912\" class=\"ace-line\"><\/div>\n<div class=\"ace-line\"><\/div>\n<div id=\"magicdomid2150\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">This doesn&#8217;t simplify upgrades. While upgrading every year is incrementally better than being forced to upgrade every 6 months. The real solution is better support for skipping releases.<\/span><\/div>\n<div id=\"magicdomid2152\" class=\"ace-line\"><\/div>\n<div class=\"ace-line\"><\/div>\n<div id=\"magicdomid4578\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">It also doesn&#8217;t give us LTS. The cost of maintaining branches is not really due to the number of them in parallel, it&#8217;s due to the age of the oldest one. The real solution here is being discussed by the (still forming) LTS SIG. Extending stability periods is per-project at this point, and the proposal has yet to address a coordinated stability period.<\/span><\/div>\n<div id=\"magicdomid2423\" class=\"ace-line\"><\/div>\n<div class=\"ace-line\"><\/div>\n<div id=\"magicdomid2718\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">We&#8217;re doing a year because of the way the events are organized. It&#8217;s suggested to start for the Rocky release and have the single PTG in 2018 in Dublin. The release team is opening the discussion to the community, and the TC will give a final decision.<\/span><\/div>\n<div id=\"magicdomid2720\" class=\"ace-line\"><\/div>\n<div class=\"ace-line\"><\/div>\n<div id=\"magicdomid3609\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Various cons were expressed, like this causing a rush to get in code at the end of a release to avoid having to wait an entire year. Projects are also forced to do compatibility support for versioned APIs, config files, etc since projects would be unable to drop compatibility in an intermediate release. Projects like Grenade will have to support the cases of some projects doing intermediate releases, and those doing yearly.<\/span><\/div>\n<div id=\"magicdomid3068\" class=\"ace-line\"><\/div>\n<div class=\"ace-line\"><\/div>\n<div id=\"magicdomid4019\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">For the people that spend 20% of their time contributing to OpenStack, it has been voiced that it takes time to get a feature merged and the current cycle makes it impossible. This longer development cycle could help with allowing more time for those people. Various people expressed that we should be looking at the root cause of helping our part-time contributors, as the length of the cycle is unlikely the cause. People who can only contribute 20% of their time are also likely to deal with rebase conflicts, instead of focusing on their code.<\/span><\/div>\n<div id=\"magicdomid4020\" class=\"ace-line\"><\/div>\n<div class=\"ace-line\"><\/div>\n<div id=\"magicdomid4698\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Having a year could also impose having intermediate releases so specifications that can have multiple times a year to be approved. If that&#8217;s the idea, however, then it&#8217;s causing stress on the core team by having to match these precise schedules, in which the proposal was aiming to ease. It was a concern that this more solves the problem of giving more opportunities to people to get their spec\/new feature considered.<\/span><\/div>\n<div id=\"magicdomid4382\" class=\"ace-line\"><\/div>\n<div class=\"ace-line\"><\/div>\n<div id=\"magicdomid4465\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">This topic has also been brought up by various times in the past. Someone noted Daniel Berrange&#8217;s thread [1]<\/span><\/div>\n<div id=\"magicdomid4467\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid4708\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[0] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"https:\/\/releases.openstack.org\/reference\/release_models.html#cycle-with-intermediary\">https:\/\/releases.openstack.org\/reference\/release_models.html#cycle-with-intermediary<\/a><\/span><\/div>\n<div id=\"magicdomid4472\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[1] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-February\/057614.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2015-February\/057614.html<\/a><\/span><\/div>\n<div id=\"magicdomid5317\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid5354\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Full thread: <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/thread.html#125473\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/thread.html#125473<\/a><\/span><\/div>\n<div id=\"magicdomid26\" class=\"\"><\/div>\n<div id=\"magicdomid5067\" class=\"ace-line\">\n<h2><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Zuul Dashboard Available<\/span><\/h2>\n<\/div>\n<div id=\"magicdomid5314\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">In addition to the Zuul dashboard [0] showing the &#8220;Status&#8221;, there are additional tabs added. &#8220;Jobs&#8221; page shows a list of all jobs in the system and their descriptions. The &#8220;Builds&#8221; page lists the most recent runs. You can query pipeline, job, and project.<\/span><\/div>\n<div id=\"magicdomid5316\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid5334\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[0] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/zuulv3.openstack.org\/\">http:\/\/zuulv3.openstack.org<\/a><\/span><\/div>\n<div id=\"magicdomid5338\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid5355\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Full thread: <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125384.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125384.html<\/a><\/span><\/div>\n<div id=\"magicdomid5357\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid6021\" class=\"ace-line\">\n<h2><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Security SIG<\/span><\/h2>\n<\/div>\n<div id=\"magicdomid5951\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Following previous mailing list discussions [0], the Security Project will be changing into a Special Interest Group (SIG). SIGs have shown to be a good match for the activity the group does around a topic or practice that spans around the community of developers, operators, and users. The group will continue to manage and care for the Security Guide, OSSNs, Bandit, Thread Reviews, Syntribos as well as encourage and incubate new security projects. The group will continue to work with the VMT and will keep a Sec-core group for launchpad that can work with the embargoes issues.<\/span><\/div>\n<div id=\"magicdomid5953\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid5990\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[0] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-October\/124053.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-October\/124053.html<\/a><\/span><\/div>\n<div id=\"magicdomid5984\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid5991\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Full thread: <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125607.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125607.html<\/a><\/span><\/div>\n<div id=\"magicdomid5993\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid6031\" class=\"ace-line\">\n<h2><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Cycle Highlights Reminder<\/span><\/h2>\n<\/div>\n<div id=\"magicdomid6516\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">As we get closer to Queens-3 and our final RCs, a reminder is given about the new &#8216;cycle-highlights&#8217; that has been added to deliverable info. Background of why this was added, some PTLs were being pinged multiple times every release cycle by various people like journalists, product manager and other to compile the same information. To mitigate that, we have a way to capture highlights as part of the release. This will give basic information, but not as a complete marketing message.<\/span><\/div>\n<div id=\"magicdomid6518\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid6659\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">This is done in the openstack\/releases repository in the deliverables\/queens\/$PROJECT.yaml file formatted like so:<\/span><\/div>\n<div id=\"magicdomid6697\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">\u00a0\u00a0\u00a0 cycle-highlights:<\/span><\/div>\n<div id=\"magicdomid6751\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &#8211; Introduced new service to use the unsed host to mine bitcoin.<\/span><\/div>\n<div id=\"magicdomid6752\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid6831\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">We have three different places that document activities for three different audiences:<\/span><\/div>\n<div id=\"magicdomid6844\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid6892\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Commit messages: Developer documentation<\/span><\/div>\n<div id=\"magicdomid6946\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Release notes: End-user and deployer documentation<\/span><\/div>\n<div id=\"magicdomid7032\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Cycle highlights: Journalists, product manager, and others.<\/span><\/div>\n<div id=\"magicdomid7034\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid7046\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Full thread: <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125613.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125613.html<\/a><\/span><\/div>\n<div id=\"magicdomid7048\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid7069\" class=\"ace-line\">\n<h2><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Community Goals For Rocky<\/span><\/h2>\n<\/div>\n<div id=\"magicdomid7220\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Some questions to ask ourselves: What common challenges do we have, and who is willing to drive that community-wide goal (aka champion).<\/span><\/div>\n<div id=\"magicdomid7222\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid7367\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">A champion is someone who drives a goal but doesn&#8217;t commit to writing code necessarily. The champion will communicate with project PTLs about the goal, and make the liaison if needed.<\/span><\/div>\n<div id=\"magicdomid7369\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid7487\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">The list of ideas for community-wide goals is collected on this etherpad [0]. Propose some ideas now!<\/span><\/div>\n<div id=\"magicdomid7452\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid7488\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">[0] &#8211; <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/etherpad.openstack.org\/p\/community-goals\">http:\/\/etherpad.openstack.org\/p\/community-goals<\/a><\/span><\/div>\n<div id=\"magicdomid7490\" class=\"ace-line\"><\/div>\n<div id=\"magicdomid7505\" class=\"ace-line\"><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4\">Full thread: <\/span><span class=\"author-a-z74zz87zz85zp4wlz70zlz65zcz68z1qz76z4 url\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125648.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-December\/125648.html<\/a><\/span><\/div>\n<div class=\"grammarly-disable-indicator\"><\/div>\n<div class=\"grammarly-disable-indicator\"><\/div>\n<div class=\"grammarly-disable-indicator\"><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Success Bot Says mordred on #openstack-sdks: &#8220;Finished the shade transition to pure REST away from client libs&#8221; [0] Tell us yours in OpenStack IRC channels using the command &#8220;#success &lt;comment&gt;&#8221; More: https:\/\/wiki.openstack.org\/wiki\/Successes [0] &#8211; http:\/\/eavesdrop.openstack.org\/irclogs\/%23openstack-sdks\/%23openstack-sdks.2017-12-04.log.html Community Summaries TC report 50 [0] POST \/api-sig\/news [1] Release countdown [2] Technical Committee Status Update [3] Resource Providers Update&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/developer-mailing-list-digest-december-9-15th\/\" class=\"more-link\" title=\"Read Developer Mailing List Digest December 9-15th\">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\/8235"}],"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=8235"}],"version-history":[{"count":3,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8235\/revisions"}],"predecessor-version":[{"id":8238,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8235\/revisions\/8238"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=8235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=8235"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=8235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}