<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 28, 2016, at 1:59 PM, Chris Dent <<a href="mailto:cdent+os@anticdent.org" class="">cdent+os@anticdent.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Wed, 28 Sep 2016, Jim Rollenhagen wrote:<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">+1 to release notes or something of that like. i was asked to give an<br class="">update on the TC internally and it seems the only information out there<br class="">is to read through backlog of meeting logs or track the items that do<br class="">get raised to ML. even then, it's hard to define what deliverables were<br class="">achieved in the cycle.<br class=""><br class=""></blockquote><br class="">FWIW, the resolutions that passed are listed here:<br class=""><a href="https://governance.openstack.org/" class="">https://governance.openstack.org/</a><br class=""></blockquote><br class="">And the git tree, with a changelog, is here:<br class=""><a href="http://git.openstack.org/cgit/openstack/governance/" class="">http://git.openstack.org/cgit/openstack/governance/</a><br class=""></blockquote><br class="">I assume, but I'd prefer if he confirm, that the point gordc was<br class="">trying to make was that there's more to what the TC gets up to than<br class="">merging changes to governance. That's certainly a major aspect and<br class="">one can track those changes by tracking both of those resources.<br class=""><br class="">Part of the point I was trying to make in the message to which gordc was<br class="">responding is that whereas a git tree can allow someone to dig through<br class="">and acquire details, a thing that is more like release notes[1] is far<br class="">more human oriented and more likely to operate as a consumable digest of<br class=""></div></div></blockquote><div><br class=""></div><div>The minutes and logs exist.</div><div><br class=""></div><div><a href="http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-09-27-20.01.html" class="">http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-09-27-20.01.html</a></div><div><br class=""></div><div><a href="http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-09-27-20.01.log.html" class="">http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-09-27-20.01.log.html</a></div><div><br class=""></div><div><a href="http://eavesdrop.openstack.org/meetings/tc/2016/" class="">http://eavesdrop.openstack.org/meetings/tc/2016/</a></div><div><br class=""></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class="">what has happened. Notably a git log will not reflect important<br class="">conversations that did not result in a governance change nor activity<br class="">that could have led to a governance change but was rejected. Certainly<br class="">where a community says "no" is just as important as where it says "yes"?<br class="">Further, merged changes are changes that have already been decided. We<br class="">need more engagement, more broadly, while decisions are being<br class="">considered. That means being more verbose, sooner.<br class=""><br class="">[1] Note that I don't actually think that release notes is the proper<br class="">form for some extra communication from the TC. Rather the justifications<br class="">that lead some projects to add release notes, in addition to the git<br class="">log, are something to consider for TC activity.<br class=""><br class="">-- <br class="">Chris Dent ┬─┬ノ( º _ ºノ) <a href="https://anticdent.org/" class="">https://anticdent.org/</a><br class="">freenode: cdent tw: @anticdent__________________________________________________________________________<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=""></body></html>