Open Stack

On 09/08/2014 11:12 AM, Mike Bayer wrote:
> 
> On Sep 7, 2014, at 9:27 PM, Anita Kuno <anteaya at anteaya.info> wrote:
> 
>> On 09/07/2014 09:12 PM, Angus Salkeld wrote:
>>> Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
>>> users happy.
>> I don't understand why you would encourage writers of blog posts you
>> disagree with by sending them traffic.
> 
> silencing users who have issues with your project is a really bad idea.    If you want to create something great you absolutely need to be obsessed with your detractors and the weight of what they have to say.  Because unless they are a competitor engaged in outright slander, there will be some truth in it.   Ignore criticism at your peril.    Someone who takes the time to write out an even somewhat well reasoned criticism is doing your project a service.
> 
> I found the above blog post very interesting as I’d like to get more data on what the large, perceived issues are.
> 
Wow, we are really taking liberties with my question today.

What part of any of my actions current or previous have led you to
believe that I want to now or ever have silenced anyone? I am curious
what led you to believe that silencing users was the motivation for my
question of Angus.

I now see, through asking Angus for clarity which he did provide (not
silencing him, you will notice), that Angus' motivation was prevention
of poor user experience through better attention.

I am highly aware, particularly in the area in which I work - the third
party space- of the leading nature of behavioural training that takes
place particularly of new contributors and contributors who don't have
English as a first language of anything we ask or expect them to do.
Many times what seems to be a reasonable comment or expectation can be
taken completely out of context by folks who don't have English as a
first language and don't have the cultural context and filters that
English speakers have.

Actually my question was motivated from a user experience point of view,
the third party user, since I am only too aware of what kind of
questions and confusion many comments cause because the commenter
doesn't take the non-English speaker point of view into account.

By clarifying Angus' motivation with Angus, hopefully his meaning -
create better user experiences, and better relationships with users -
has come through.

And I agree with all of your points, which is why I take such pains to
create clarity on the mailing lists and other communication.

Thanks,
Anita.
> 
> 
> 
>>
>> Anita.
>>>
>>> 1) Consistent/easy upgrading.
>>>     all projects should follow a consistent model to the way they approach
>>> upgrading.
>>>     it should actually work.
>>>     - REST versioning
>>>     - RPC versioning
>>>     - db (data) migrations
>>>     - ordering of procedures and clear documentation of it.
>>>    [this has been begged for by operators, but not sure how we have
>>> delivered]
>>>
>>> 2) HA
>>>  - ability to continue operations after been restated
>>>  - functional tests to prove the above?
>>>
>>> 3) Make it easier for small business to "give OpenStack a go"
>>>  - produce standard docker images as part of ci with super simple
>>> instructions on running them.
>>>
>>> -Angus
>>>
>>>
>>>
>>> On Thu, Sep 4, 2014 at 1:37 AM, Joe Gordon <joe.gordon0 at gmail.com> wrote:
>>>
>>>> As you all know, there has recently been several very active discussions
>>>> around how to improve assorted aspects of our development process. One idea
>>>> that was brought up is to come up with a list of cycle goals/project
>>>> priorities for Kilo [0].
>>>>
>>>> To that end, I would like to propose an exercise as discussed in the TC
>>>> meeting yesterday [1]:
>>>> Have anyone interested (especially TC members) come up with a list of what
>>>> they think the project wide Kilo cycle goals should be and post them on
>>>> this thread by end of day Wednesday, September 10th. After which time we
>>>> can begin discussing the results.
>>>> The goal of this exercise is to help us see if our individual world views
>>>> align with the greater community, and to get the ball rolling on a larger
>>>> discussion of where as a project we should be focusing more time.
>>>>
>>>>
>>>> best,
>>>> Joe Gordon
>>>>
>>>> [0]
>>>> http://lists.openstack.org/pipermail/openstack-dev/2014-August/041929.html
>>>> [1]
>>>> http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-09-02-20.04.log.html
>>>>
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>