Just to offer some closure, it seems like the voting idea was shot down with the energy of a trillion stars, yet the general idea of offering an easy way for users to request features makes sense. Expect to see ideas of how to implement this soon...
----- Original Message ----- > > > On Apr 10, 2015, at 11:04 AM, Boris Pavlovic <bo...@pavlovic.me> wrote: > > > > Hi, > > > > I believe that specs are too detailed and too dev oriented for managers, > > operators and devops. > > They actually don't want/have time to write/read all the stuff in specs and > > that's why the communication between dev & operators community is a > > broken. > > > > I would recommend to think about simpler approaches like making mechanism > > for proposing features/changes in projects. > > Like we have in Rally: > > https://rally.readthedocs.org/en/latest/feature_requests.html > > > > This is similar to specs but more concentrate on WHAT rather than HOW. > > +1 > > I think the line between HOW and WHAT are too often blurred in Neutron. > Unless we’re able to improve our ability to communicate at an appropriate > level of abstraction with non-dev stakeholders, meeting their needs will > continue to be a struggle. > > > Maru > __________________________________________________________________________ > 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 > __________________________________________________________________________ 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
