{"id":7881,"date":"2016-07-25T11:26:44","date_gmt":"2016-07-25T16:26:44","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7881"},"modified":"2016-07-25T11:26:44","modified_gmt":"2016-07-25T16:26:44","slug":"openstack-developer-mailing-list-digest-20160722","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160722\/","title":{"rendered":"OpenStack Developer Mailing List Digest July 2-22"},"content":{"rendered":"<h1 class=\"western\">SuccessBot Says<\/h1>\n<ul>\n<li>Notmyname: the 1.5 year long effort to get at-rest encryption in openstack swift has been finished. at-rest crypto has landed in master<\/li>\n<li>stevemar: API reference documentation now shows keystone&#8217;s in-tree APIs!<\/li>\n<li>Samueldemq: Keystone now supports Python 3.5<\/li>\n<li><a href=\"https:\/\/wiki.openstack.org\/wiki\/Successes\">All<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Troubleshooting and ask.openstack.org<\/h1>\n<ul>\n<li>Keystone team wants to do troubleshooting documents.<\/li>\n<li>Ask.openstack.org might be the right forum for this, but help is needed:\n<ul>\n<li>Keystone core should be able to moderate.<\/li>\n<li>A top level interface than just tags. The page should have a series of questions and links to the discussions for that question.<\/li>\n<\/ul>\n<\/li>\n<li>There could also be a keystone-docs repo that would have:\n<ul>\n<li>FAQ troubleshooting<\/li>\n<li>Install guides<\/li>\n<li>Unofficial blog posts<\/li>\n<li>How-to guides<\/li>\n<\/ul>\n<\/li>\n<li>We don&#8217;t want a static troubleshooting guide. We want people to be able to ask questions and link them to answers.<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-July\/thread.html#98598http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-July\/thread.html#98598\">Full thread<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Leadership Training Recap and Steps Forward<\/h1>\n<ul>\n<li>Colette Alexander has successfully organized leadership training in Ann Arbor, Michigan.<\/li>\n<li>17 people from the community attended. 8 of them from the TC.<\/li>\n<li>Subjects:\n<ul>\n<li>servant leadership<\/li>\n<li>Visioning<\/li>\n<li>Stages of learning<\/li>\n<li>Good practices for leading organizational change.<\/li>\n<\/ul>\n<\/li>\n<li>Reviews and reflections from the training have been overwhelmingly positive and some blogs started to pop up <a href=\"http:\/\/www.tesora.com\/openstack-tc-will-not-opening-deli\/\">[1]<\/a>.<\/li>\n<li>A smaller group of the 17 people after training met to discuss how some ideas presented might help the OpenStack community.\n<ul>\n<li>To more clearly define and accomplish that work, a stewardship working group has been proposed <a href=\"https:\/\/review.openstack.org\/#\/c\/337895\/\">[2]<\/a>.<\/li>\n<\/ul>\n<\/li>\n<li>Because of the success, and 5 TC members weren&#8217;t able to attend, Colette is working to arrange a repeating offer.<\/li>\n<li>Thanks to all who attended and the OpenStack Foundation who sponsored the training for everyone.<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-July\/thread.html#98875\">Full thread<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Release Countdown For Week R-12, July 11-15<\/h1>\n<ul>\n<li>Focus:\n<ul>\n<li>Major feature work should be well under way as we approach the second milestone.<\/li>\n<\/ul>\n<\/li>\n<li>General notes:\n<ul>\n<li>We freeze release libraries between the third milestone and final release.\n<ul>\n<li>Only emergency bug fix updates are allowed during that period.<\/li>\n<li>Prioritize any feature work that includes work in libraries.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Release actions:\n<ul>\n<li>Official projects following any of the cycle-based release models should propose beta 2 tags for their deliverables by July 14.<\/li>\n<li>Review stable\/liberty stable\/mitaka branches for needed releases.<\/li>\n<\/ul>\n<\/li>\n<li>Important dates:\n<ul>\n<li>Newton 2 milestone: July 14<\/li>\n<li>Library release freeze date starting R-6, Aug 25<\/li>\n<li>Newton 3 milestone: September 1<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-July\/098944.html\">Full thread<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">The Future of OpenStack Documentation<\/h1>\n<ul>\n<li>Current central documentation\n<ul>\n<li>Consistent structure<\/li>\n<li>For operators and users<\/li>\n<li>Some less technical audience use this to evaluate with various other cloud infrastructure offerings.<\/li>\n<\/ul>\n<\/li>\n<li>Project documentation trends today:\n<ul>\n<li>Few are contributing to central documentation<\/li>\n<li>More are becoming independent with their own repository documentation.<\/li>\n<li>An alarming number just don&#8217;t do any.<\/li>\n<\/ul>\n<\/li>\n<li>A potential solution: Move operator and user documentation into individual project repositories:\n<ul>\n<li>Project developers can contribute code and documentation in the same patch.<\/li>\n<li>Project developers can work directly or with a liaison documentation team members to improve documentation during development.<\/li>\n<li>The documentation team primarily focuses on organization\/presentation of documentation and assisting projects.<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-July\/thread.html#99012\">Full thread<\/a><\/li>\n<\/ul>\n<p class=\"lead\">&nbsp;<\/p>\n<p>[1] &#8211; <a href=\"http:\/\/www.tesora.com\/openstack-tc-will-not-opening-deli\/\">http:\/\/www.tesora.com\/openstack-tc-will-not-opening-deli\/<\/a><\/p>\n<p>[2] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/337895\/\">https:\/\/review.openstack.org\/#\/c\/337895\/<\/a><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SuccessBot Says Notmyname: the 1.5 year long effort to get at-rest encryption in openstack swift has been finished. at-rest crypto has landed in master stevemar: API reference documentation now shows keystone&#8217;s in-tree APIs! Samueldemq: Keystone now supports Python 3.5 All Troubleshooting and ask.openstack.org Keystone team wants to do troubleshooting documents. Ask.openstack.org might be the right&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160722\/\" class=\"more-link\" title=\"Read OpenStack Developer Mailing List Digest July 2-22\">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\/7881"}],"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=7881"}],"version-history":[{"count":2,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7881\/revisions"}],"predecessor-version":[{"id":7883,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7881\/revisions\/7883"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=7881"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=7881"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=7881"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}