On 28/09/2016 12:41 PM, Chris Dent wrote: > > * Information is not always clear nor clearly available, despite > valiant efforts to maintain a transparent environment for the > discussion of policy and process. There is more that can be done > to improve engagement and communication. Maybe the TC needs > release notes?
+1 to release notes or something of that like. i was asked to give an update on the TC internally and it seems the only information out there is to read through backlog of meeting logs or track the items that do get raised to ML. even then, it's hard to define what deliverables were achieved in the cycle. i found this updates page but it seemed a little sparse so i imagine other stuff happened. i think more of this would help explain what the TC does and where it hopes to go because to be frank, i'm not sure what is in the scope of TC and what is not and i've been following the list and meetings for a while.  http://www.openstack.org/blog/category/technical-committee-updates/ cheers, -- gord __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev