[openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management
Miguel Angel Ajo Pelayo
mangelajo at redhat.com
Wed Apr 22 06:29:15 UTC 2015
The rally process (email based) doesn’t seem scalable enough for the neutron case
IMHO, but I agree that a voting system doesn’t differ too much from launchpad
and that it can be gamed.
> On 22/4/2015, at 1:21, Assaf Muller <amuller at redhat.com> wrote:
> 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 <boris at pavlovic.me> wrote:
>>> 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
>>> I would recommend to think about simpler approaches like making mechanism
>>> for proposing features/changes in projects.
>>> Like we have in Rally:
>>> This is similar to specs but more concentrate on WHAT rather than HOW.
>> 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.
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Miguel Angel Ajo
More information about the OpenStack-dev