Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

2015-04-21 Thread Miguel Angel Ajo Pelayo
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 wrote: > > Just to offer some closure, it seems like the voting idea wa

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

2015-04-21 Thread Assaf Muller
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, 2

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

2015-04-13 Thread Maru Newby
> On Apr 10, 2015, at 11:04 AM, Boris Pavlovic 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 & opera

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

2015-04-10 Thread Kevin Benton
I like this idea. It leaves specs and implementation details to people familiar with the code base while providing a good place for users and devs to discuss feature requests. On Apr 10, 2015 2:04 PM, "John Kasperski" wrote: > On 04/10/2015 01:04 PM, Boris Pavlovic wrote: > > Hi, > > I believe

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

2015-04-10 Thread John Kasperski
On 04/10/2015 01:04 PM, Boris Pavlovic 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

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

2015-04-09 Thread Salvatore Orlando
On 9 April 2015 at 17:04, Kyle Mestery wrote: > On Thu, Apr 9, 2015 at 9:52 AM, Assaf Muller wrote: > >> The Neutron specs process was introduced during the Juno timecycle. At >> the time it >> was mostly a bureaucratic bottleneck (The ability to say no) to ease the >> pain of cores >> and manag

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

2015-04-09 Thread Kyle Mestery
On Thu, Apr 9, 2015 at 9:52 AM, Assaf Muller wrote: > The Neutron specs process was introduced during the Juno timecycle. At the > time it > was mostly a bureaucratic bottleneck (The ability to say no) to ease the > pain of cores > and manage workloads throughout a cycle. Perhaps this is a somewh