{"id":2331,"date":"2016-08-05T16:55:09","date_gmt":"2016-08-05T14:55:09","guid":{"rendered":"https:\/\/blog-alexis.monville.com\/en\/?p=2331"},"modified":"2016-08-05T16:55:09","modified_gmt":"2016-08-05T14:55:09","slug":"contribute-to-the-success-of-openstack","status":"publish","type":"post","link":"https:\/\/blog-alexis.monville.com\/en\/2016\/08\/05\/contribute-to-the-success-of-openstack\/","title":{"rendered":"Contribute to the Success of OpenStack"},"content":{"rendered":"

During the OpenStack Summit in Austin<\/a>, Mark McLoughlin and I delivered a talk titled: “Contribute to the Success of OpenStack”.<\/p>\n

Our talk was meant to explain how we were inspired by agile values and principles to improve our internal organization, and how we thought it could impact our ability to contribute more effectively to the OpenStack project.<\/p>\n

One of the idea that is often used to describe the way companies are contributing to open source project is that you need at some point to wear your company hat to represent what your company needs, and some times you need to wear your upstream hat to represent what the project needs. We speak some time of the need to balance between upstream and downstream.<\/p>\n

Our point was to say that this idea represents the reality perfectly well in projects were the developers are the users of the projects. In this case they are solving problems they are facing on a regular basis.<\/p>\n

The OpenStack project is more complex in this sense that the developers are rarely the main users of the project. They don’t have to operate a large scale cloud on a day to day basis.<\/p>\n

So, to be able to understand the needs, and to propose effective solutions, the developers of the project need to hear from the real users. That’s were they need to wear at the same time their corporate and upstream hats, because the customers and partners of their company represents the needs of the real users, and wearing those hats they are bringing a lot of value to the project by proxying the real users.<\/p>\n

We also explored the fact that when the reaction toward one of the idea that we were bringing on the table was really hostile, there was probably good reason for that, and that was great value for our company that the project was bringing to us. This obvioulsy can only be achieved when the maturity of the project is high enough, especially on the corporate diversity aspect.<\/p>\n

We covered after that how we were organizing the teams that are contributing to OpenStack by giving them a clear focus to solve some real user’s needs, and end to end responibility to solve this. Those teams are primary responsible for contributing to some of the components, but the components are not driving the structure of the organization.<\/p>\n

For each team, we want the team members to understand their mission, their goals, and to drive their contribution in the value flow.<\/p>\n

Here is the recording of the session:<\/p>\n