<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Rereading your question, Gord, the tl;dr of my message is that current roadmap is not intended to dictate work or what future features should be—just captures and communicates work already in motion. <div class=""><br class=""></div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Anne Bertucio</div><div class="">Marketing and Certification, OpenStack Foundation</div><div class=""><a href="mailto:anne@openstack.org" class="">anne@openstack.org</a> | 206-992-7961</div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Nov 29, 2017, at 9:27 AM, Anne Bertucio <<a href="mailto:anne@openstack.org" class="">anne@openstack.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The community does have an existing Roadmap, albeit this cycle we decided we need to change how we design the Roadmap and its final form. We have a small community Roadmap team (anyone want to join?!) who compiles this information. <div class=""><br class=""></div><div class="">In the past, the Roadmap aimed to be a document for both project teams, end users, and anyone in between. It tried to capture what was coming in the next release as well as predict up to 3 releases forward. We decided this was biting off far too much—trying to be all things to all people. </div><div class=""><br class=""></div><div class="">What we’re trying to do now is be a user-focused document that communicates critical changes and exciting features coming in the next release. We want to help people who are evaluating OpenStack see future features, and help people who are less privy to the day-to-day dev channels be aware of features that may affect them. </div><div class=""><br class=""></div><div class="">The Roadmap that was presented in Sydney lives here: <a href="https://www.openstack.org/software/roadmap" class="">https://www.openstack.org/software/roadmap</a></div><div class=""><br class=""></div><div class=""> </div><div class=""><div class="">
<div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Anne Bertucio</div><div class="">OpenStack Foundation</div><div class=""><a href="mailto:anne@openstack.org" class="">anne@openstack.org</a> </div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Nov 29, 2017, at 9:10 AM, gordon chung <<a href="mailto:gord@live.ca" class="">gord@live.ca</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><br class="">On 2017-11-28 11:36 AM, Chris Dent wrote:<br class=""><blockquote type="cite" class="">* A somewhat bizarre presentation suggesting the Board and the TC<br class=""> manage the OpenStack roadmap. There wasn't time to actually discuss<br class=""> this as previous topics ran _way_ over, but at a superficial glance<br class=""> it appeared to involve a complete misunderstanding of not just how<br class=""> open source works in OpenStack, but how open source works in<br class=""> general.<br class=""></blockquote><br class="">was this topic to discuss how to implement an existing roadmap or how <br class="">the board/tc should build a roadmap or something else completely? if the <br class="">first, is there a link to this 'roadmap'?<br class=""><br class="">cheers,<br class=""><br class="">-- <br class="">gord<br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></div></blockquote></div><br class=""></div></div>__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>