- Original Message -
> From: "John Garbutt"
> To: maishsk+openst...@maishsk.com
[SNIP]
> On 14 May 2015 at 19:52, Maish Saidel-Keesing wrote:
> > Can we please have this as a default template and the default way to allow
> > Operators to submit a feature request for EVERY and ALL the Op
Sean,
Adding most features to most projects requires a reasonable conversation
> about how that impacts other parts of that project, and other projects
> in OpenStack, and how it impacts existing deploys of OpenStack, and
> compatibility between OpenStack implementations in the field, especially
>
On 05/15/2015 07:20 AM, Boris Pavlovic wrote:
> John,
>
>
> So, you can have all details in the spec, or you can have only the
> problem statement complete. Its up to you as a submitter how much
> detail you want to provide. I would recommend adding rough ideas into
> the alternat
John,
So, you can have all details in the spec, or you can have only the
> problem statement complete. Its up to you as a submitter how much
> detail you want to provide. I would recommend adding rough ideas into
> the alternatives section, and leaving everything else blank except the
> problem s
> On 05/14/15 21:04, Boris Pavlovic wrote:
> I believe that backlog should be different much simpler then specs.
Agreed. And they are.
> Imho Operators don't have time / don't want to write long long specs and
> analyze how they are aligned with specs
> or moreover how they should be implemented
On 05/14/15 21:04, Boris Pavlovic wrote:
John,
I believe that backlog should be different much simpler then specs.
Imho Operators don't have time / don't want to write long long specs
and analyze how they are aligned with specs
or moreover how they should be implemented and how they impact
pe
Kyle Mestery recently merged a governance change in Neutron that introduces
the idea of request for enhancement bug. Anyone can file a bug against Neutron
and tag it with 'rfe'. The bug should include the problem statement and use
cases,
and any developer can later come in write a spec should it r
John,
I believe that backlog should be different much simpler then specs.
Imho Operators don't have time / don't want to write long long specs and
analyze how they are aligned with specs
or moreover how they should be implemented and how they impact
performance/security/scalability. They want
jus
Hi,
I was talking with Matt (VW) about how best some large deployment
working sessions could send their requirements to Nova.
As an operator, if you have a problem that needs fixing or use case
that needs addressing, a great way of raising that issue with the
developer community is a "Backlog" no
