Académique Documents
Professionnel Documents
Culture Documents
org/user-stories/)
Documentation (http://docs.openstack.org/)
Hi all,
Nothing, but working with these assumptions is really the blocker. That
is exactly why many people in their feedback say we have a "people
problem" in OpenStack. But it's not really the people problem, it is the
assumption problem.
With 'n' problems in a domain and 'm' people working on all those
problems, individually, we have the assumption problem of the order of
O((m*e)^n) where you can think of 'e' as the convergence factor.
Convergence factor being the ability of a group to come to an agreement
of the order of 'agree to agree', 'agree to disagree' (add percentages
to each for more granularity). There is also another assumption (for the
convergence factor) that everyone wants to work in the best interest of
solving the problems in that domain.
I think the first and foremost step is understanding the 'intent' behind
every step -- whether it is a proposal, code, email, etc.
I think people prefer to use ML a lot and I am not a great fan of the
same. It is a multi-cast way of communication and it has assumptions
around time, space, intent of the audience & intent to actually read
them. Same is for gerrit/etherpad.
Same applies to the broadcast media too but to a smaller extent as that
content is static and focuses on one thing.
Team bonding, one to one feedback etc. processes are adopted as well.
But OpenStack is one team and you can potentially have a significantly
high dynamism in the flexibility of the team so all that is relatively
less important.
* I find it is very important for people who actually have a strong say
in things to focus less on code or even individual reviews and focus
more on awareness, collaboration and establishing convergence factor.
Leave the nitty gritty details to those who have more bandwidth in hand
for it.
* I think if someone has a very strong say then they need to keep a
(near to) synchronous communication to the development process. We need
to keep the context, keep our convergence intact and move forward with a
common understanding. Otherwise it is VERY disruptive for someone
investing their time, money, energy and interest in OpenStack.
* Also, one very important thing that I keep hearing: "I do not like
that" without any other information, as an argument to disregard
technical proposals. I think it is very disruptive and irrational way to
express arguments. We are not buying flowers in OpenStack, we need to
keep rationality in check when we express our opinions. It reduces
convergence factor and increases dubiety among the developers &
reviewers. Then we have a ecosystem where people do not understand why
we do things the way we do it. We should not stop businesses just
because someone doesn't like something, please no. Lack of rationale can
actually do that.
I think the most important thing is to have belief on our practices. For
that we need to enforce our standards and ensure people follow it. Once
we have more strictness on less disruption, we will have more confidence
in moving forward faster. We only have a governance today that is merely
a guideline (Constitution), what we really need is a judiciary.
Rest of the discussion, I leave upto you -- whether you think this is
important or you don't. At least, I will have a good night sleep
considering that I raised some serious concerns!
Yours sincerely,
--
Nikhil Komawar
More
information
about
the
OpenStack-dev
mailing
list
(http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev)
OpenStack
Projects
(http://openstack.org/projects/)
OpenStack
Security
(http://openstack.org/openstack-security/)
Common
Questions
(http://openstack.org/projects/openstack-faq/)
Blog
(http://openstack.org/blog/)
Community
User
Groups
(http://openstack.org/community/)
Events
(http://openstack.org/events/)
Jobs
(http://openstack.org/jobs/)
Companies
(http://openstack.org/companies/)
Contribute
(http://wiki.openstack.org/HowToContribute)
Documentation
OpenStack
Manuals
(http://docs.openstack.org/)
Getting
Started
(http://docs.openstack.org/diablo/openstack-compute/starter/content/)
Wiki
(http://wiki.openstack.org/)