In the last week I've been dealing with two [1][2] cross project efforts that I believe would have been great candidates for the cross-project goals process. I think the cross project goals process is lightweight, and it is a closed-loop process which ensures that we don't have escapes. The use of the mailing list to communicate these has proved to be problematic in the past given the sheer volume of mail on the mailing list and the fact that it is hard to establish server side filters, or for that matter client side filters to try and only see the emails that are likely of interest without any possibility that emails that are important get filtered out.
So, what's my request . If you see something like this which you believe is a cross-project, OpenStack wide effort being discussed on the mailing list, please: (a) Add [all] to the subject line if it isn't already there, and (b) Suggest to the sender that they should consider using the cross-project release goals process. Thanks, -amrith [1] http://lists.openstack.org/pipermail/openstack-dev/2016-November/106906.html [2] http://lists.openstack.org/pipermail/openstack-dev/2016-February/086272.html
smime.p7s
Description: S/MIME cryptographic signature
__________________________________________________________________________ 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