Hi everyone, Earlier this year we discussed areas we could collectively come together as a community and be better. One area identified was getting unanswered requirements simply put, answered[1]. After some small and larger conversations the goal of adopting the SIG model, as touted by other OpenSource communities like k8s and Fedora for example, was introduced at the Forum[2].
With this goal in mind we understand that it is not the only single perfect solution but it is one step in the right direction. Rather than wait for ideas and implementation details to coalesce delaying the opportunity to learn we decided to take to a couple actions: 1. Start the openstack-sigs mailing list 1. Propose creation of Meta SIG ( http://lists.openstack.org/pipermail/openstack-sigs/2017-July/000000.html ) *be sure to read this* An initial thread[3] surrounding the effectiveness and implementation of SIGs had been started and folks should continue the conversation by using the [meta] tag on the openstack-sigs mailing list. We look forward to lively and above all practical and applicable discussions taking place within SIGs which result in unanswered requirements being answered. Also we would like to encourage current folks to use the [meta] tag in your emails to the mailing list to discuss any successes, failures, advantages, disadvantages, improvements, suggestions, etc. [1] http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/ [2] https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements [3] http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html -- Melvin Hillsman and Thierry Carrez
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
