Open Stack

Inline.

On Thu, Nov 8, 2012 at 11:47 AM, Matt Joyce <matt at nycresistor.com> wrote:

> I think it's a great idea to develop a process for operators to go
> through in suggesting work for dev teams.  One that alleviates a lot
> of the burden of having to know what is and is not a valid bug or blue
> print.  If the operations contributors can work together to self solve
> problems and promote real issues that's a win for everyone.  Low
> barrier of entry for operators of the stack, plus quality bug reports
> and blue prints.
>
> I really like the idea.
>
>
Me too. An advantage of this wiki approach is understanding
and visualization of the pain points, from different perspectives. If an
issue is clearly a feature request or bug it probably doesn't need a wiki
entry and should go straight to the bug tracker. However, if a specific
requirement is undefined, requires code refactoring or the objective of a
functionality varies from site to site; then a better understanding is
needed before a solution can be executed. Wiki seems ideal to establish
resolve before formalizing into a specific issue, at which point, the bug
tracker is exquisitely engineered for the task :)

-George


>
>
-- 
George Georgalis, (415) 894-2710, http://www.galis.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20121108/0aae86e8/attachment.html>