cloudchat

IRC ;-)

(IRC == Internet Relay Chat)

Mind melds :-)

Stop. Collaborate. And...listen. = )

seriously, you want to enable effective communication between the devs working across timezones and around the globe

open communication - mailing lists, IRC, GitHub. Avoid back channel discussions.

@mjfork totally agree, you want complete transparency

Git / GitHub ?

trust and efficiency

Really though, I think the key for OpenStack has been letting the community develop organically

@Christo4Ferris Is complete transparency a challenge to achieve? Is it possible?

@NoamShen interestingly enough, the #cloudfoundry project encourages pair programming; which is as close as we can get to the vulcan mind meld;-)

When people have a say in the direction, engagement skyrockets

@jbryce that is key for all communities - let them find their own way

Yes, community inspired standards that are codified into relatively "official" standards is certainly important.

@kellycapo Trust is also very important, completely agree

is transparency a challenge? not necessarily, but when you notice backchannel discussions, you try to tease them out into the open

avoiding drama at all costs :)

Complexity is one of the enemies of *effective* transparency, so we should strive to reduce the complexity of OpenStack and similar technology suites.

Speaking selflishly - storage that is both "cloudy" and supports enterprise applications (performance, QoS, HA, etc.)

Building diverse communities with strong, open governance models. And that is why both are starting Foundations to address them.

one is a good oe to have, how to deal with all of the contributions from the community

@mjfork totally agree!

@mjfork +1

Relatively speaking, these implementations are still a fairly heavy lift for most organization.

Why is that, @ebravick?

There are lots of players on the scene hoping to address this. Like http://www.pistonclo...

@mjfork your tweet was only .02 ms ahead of mine. we have been working together too much as you are reading my minde

This is a major shift in how IT is managed, and it requires a cultural shift in many organizations

There are lots of reasons, this is still fairly young, the problem set is complicated, the world is moving fast.

yes, the change in behavior within large enterprise accounts will also be a key challenge

@jbryce — How dramatic of a cultural shift do you think is needed? Or does it depend on the organization?

#openstack and #cloudfoundry are each dealing with contributions in their own way; trying to find effective approaches to ensuring quality contributions and enabling strong innovation

It also requires a shift from a CapEx mentality to a service mentality. Even on-premise, the model will shift to services (e.g., an OpenStack service like MetaCloud)

Another challenge that I think they are finding more difficult to address - getting operators involved earlier. Ops are not typically as community minded as devs.

@ebravick no question; but so is Linux; most don't get the Linux kernel and build their own distro; you work with a partner

@mjfork operators and users

it depends on the industry. some industries are somewhat stagnant from an innovation standpoint and need more radical cultural shifts than others

@Christo4Ferris ...oh yes, absolutely. We see lots of players coming on line to address the issue. The early Linux days are in many ways a good analogy for where open cloud tech is today.

see also stuff like https://www.nebula.c...

people like to maintain control - sometimes to a fault - with technology moving at "cloud speed" you have to be able to adapt quickly to change. Larger the organization the more difficult the transition

I think that there are similarities between these open cloud movements and the early days of the web (e.g. Apache Foundation and Eclipse)

i do believe that one difference in the open cloud movements vs the open movements of the past is the size of the community participating. Cloud delivered services have lowered the participation bar. Small companies can have a great impact

Certainly Linux, Apache, Eclipse are were "training grounds" for what we are seeing today with OpenStack and CloudFoundry

Another benefit for open is agility. By using Open APIs you can adapt to new technology when it becomes available without changing your application architecture

experimentation is key. Do not be afraid of making mistakes but be very afraid of not learning from those mistakes and incorporating that learning into the next iteration of the service

also believe that experimentation is not only important on the technical side but also on the business side. Being able to experiment with new business models in an open way can lead to rapid success

Certainly some industries are more open and therefore have an easier transition to open cloud technologies. Over time Government and industry regulations will be more favorable

the more collaborative/social the industry is the more it benefits from an open ecosystem

industries with a large partner ecosystem (e.g. supply chain) also benefits because open cloud technologies provide a "center of gravity" for that partner ecosystem

Been seeing lots of Big Data oriented Research consortiums within colleges/Universities using both

I believe that openness means spontaneous innovation can occur and the only way to survive at cloud speed to enable "someone you never trained to create a solution that you never envisioned"

@ebravick Exactly, those with proprietary approach are in "The Land of the Lost" :)