On Fri, Jan 10, 2014 at 5:16 AM, Flavio Percoco <[email protected]> wrote:
> On 10/01/14 11:28 +0100, Thierry Carrez wrote: > >> Personally I think we should (and we can) say NO more often. As we get >> > stronger as a dev community it becomes easier, and I think we see more >> "opinionated" choices in younger projects. That said, it's just harder >> for old projects which already have a lot of options to suddenly start >> denying someone's feature instead of just adding another option... > > +1 > I've seen NOs flying around, which is a good sign. I think one of the > issues right now is that we already have many configuration options in > some projects and we should try to shrink them, if possible. > +1 or maybe +1000 after looking at how to test all of those options... The trend of attempting to accommodate all possible options in configuration has led us down the slippery slope of complexity that is extremely hard to recover from. dt -- Dean Troyer [email protected]
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
