Flavio Percoco wrote:
On 21/01/16 11:55 +0100, Thierry Carrez wrote:
As you said, projects can already decide to restrict feature
development in a given cycle, so this is nothing new. We only need to
communicate more aggressively that it is perfectly fine (and even
encouraged) to define the amount of feature work that is acceptable
for a project for a given cycle.
++
Precisely my point. If there's a way, from a governance perspective, to help
communicate and encourage folks to do this, I wan't to take it. It was mentioned
that some teams didn't know this was possible others that felt it was going to
be really hard w/o any support from the governance team, hence this email and
effort.
The light approach would be to document the possibility in the project
team guide. The heavy approach would be to take a TC resolution. Both
solutions would have to be mentioned on openstack-dev and the weekly
digest to get extra publicity.
--
Thierry Carrez (ttx)
__________________________________________________________________________
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
