 Hello My name is Antonio here I'm going to to try to initiate a travel so we can understand how the Ecosystem the open source ecosystem Evolve it we were going to look to the history and understand the economic and the social Events that were able to create this big open source projects like open stack and Kubernetes so If we look at the history at the history at the glance we can we can see that everything started when people Realized it how to create computers how to program them so the computers can do what We wanted them to do That's how I try to spray my kids how they and so work and the computers work so at the beginning in the 50s and 60s Almost all the software was produced is in producing the academic and the Corporate researcher so it was only in the reach of some privileged people that were able to to develop so what and At that moment there were any problem. They share the all the code all the experiences but everything changed when in the I Think that was in the 74 the the US government Decided that the software can be copyright so and let me try to Go deeper into this is to understand the copyright We need to understand that How it works so the copyright is automatically attached to every novel expression of an idea whether through Test sounds or imaginary so the creator has the right to commercial exploit that Expression of the idea also is there a derivative work There is an exception that when you are working for hire these copyrights belong to the companies doesn't belong to the person so at that time in the In In the 70s people started to realize that they can take a competitive advantages of Of these copyrights and they start to exploit this if you can see it in 75 and in 77 Microsoft and Apple were founded so that they I don't know these companies are 40 years old so And they is there is the reason why it started they started to take up in touch of the Copyrights of the software licenses they created the software licenses to be able to monetize the software writing by all because Because of this This way of treating the software some people like Richard Stalman initiated the New project so they wanted to Create software for free. They were promoting the freedom in the software. So everybody should be able to To write code to redistribute code and nobody can take or exploit the the software okay What happened at that time to at the beginning of the 80s there was the The computer industry started to commercialize the The personal computers like the sinker CX 80 or the IBM personal computers So this means that more people was starting to develop to work at home with their computers to hack and To get interested in software development During that time Richard Stalman started to create the new project. He wanted to create a Free operating system for the people. He wanted to create software For free that everybody we should be able to use and to redistribute without any economic exploitation in that in that decade in the 80s at the end of the decade is when Internet has started to connect all this home. So the community started to get connected and and And Richard Stalman was missing one of the most important pieces for for his project that was the camera So it was back in 1991 when Lino Stalman is to release his free camera and It wasn't only the the free camera what he released because you let me you Read the cathedral on the basalt by Eric Raimon he he made a great points because he studied the This particular event in the open circle and he was very clear about That Linus Krebler hack was not the construction of the Linus currently says but rather his innovative Linus development model So you just check to some of the lessons that he learned from studying that model was First is the importance of users and second is that this early release often and listen to your customers That are pretty similar to the other principles to so he Achieved to to engage with a lot of people a lot of community working for free creating an operating system that was in Was able to catch up with other proprietary software in in less years with other Companies developing other operating systems and in some aspect it had improved the inhibited the competition it was then when People started to realize that The open source Let's put this way. So the open source started to have an Ideology part represented by the new foundation with Richard Stalman that There were other more pragmatic pragmatic trend in the open source community some of them can be represented for Linus turbo team or really other people like The Python creator that they were thinking more that okay, the software should be free Nobody should be able to spread but people has to Be able to achieve money to to to live on that so There I think that the One of the most important Decision was taken in 1998 when Timor really hosted the what it was called the free world summit and Later on was called the open source summit then is when they voted to to decide on one name. They will put to this to this moving and Defund them after that the open source with the also needed Richard Stalman continued with his free software foundation and is clear and is Going on and ongoing debate into the open source communities about the different ideologies and the different ways of understand open source Let me step back for a moment sorry So the thing is During that time in the in this from the 94 to the 2004 other events were was happening and one of the most important event was that the World the worldwide way the worldwide way so the first graphical browser was created in 1993 and some companies started to commercialize products and and to use the world way to to do business and one of the most important Wars during that year was the the so-called browser war between net escape and Microsoft Internet Explorer because Microsoft Internet Microsoft was using his monopoly to introduce his browser and net escape started to To lose the button in the in the in that economic ecosystem What they decided after checking and reading the Cathedral on the Bazaar and seeing the open source moment is what less open source our product It worked for the other guys why it's not going to work for for us But the problem that they had is the licenses this they were creating an private software with a lot of contacts a lot of ties and a lot of and and a lot of warrants that the current open source licensing was when they were to to fulfill so They started to create the Mozilla license and the Mozilla Foundation and they created the Mozilla project So you can see that it's still going on and it was a very clever and a very good movement on the side after the browser war it started the so-called dot-com bubble and a lot of money went out of the of the ecosystem of the software ecosystem, but other other Movement started that was the virtualization So people started to have a lot of hardware and being where it started to commercialize his first level virtualization product and Amazon started to see an advantage and commercializing his resources that they were not using and the crowd started Amazon Google and Microsoft created their own public cloud offers and in 2010 track space With an ass an ASA join it and launch of the open-style project in 2015 after the crowd This I IAS movement the Google from the Google Google and Linux Foundation created the Kubernetes project so basically what they created is a Phenomenon based on the on the Linux experience the and the bizarre model The open stack foundation created an ecosystem where the companies were able to obtain indirect value from the project and The product the value was zero because it was open source Nobody's going to pay for because the license doesn't allow it So but the people and the companies were competing with to take the Revenue from complimentary service for a complimentary so our complimentary hardware distribution and support and other companies tried to build public cloud services in that space you can see some examples as red hat and canonical rack space HP So What the open-stack foundation was able to do is to create This is a great study. I really recommend to read the study is linked in the in the line It was able to recreate the Linux kernel the Linux success creating the bizarre model but in this case they didn't get Did they didn't get contributed directly they get companies if you can see from The federal races that are the relationship between the companies. So in ice house The number of companies working in the project Was so big that the project has beaten all the Competence you can see that when they are started they started competing against crowdstack they can start to go competing against up open Nebula and Eucalyptus and the moment that they started to get this critical mass of companies of Contributors sponsored by the companies Companies wanted to put money or to get revenue from from the this movement. They started to to get a pace and in innovation in Delivering that nobody could compete. So the other produce. I think that they are still alive, but you can see that open-stack Was the only one that Succeed in the II II is Ecosystem and to understand that we need to understand what they were what they had to do to do that so first of all is the companies Needed a neutral ecosystem. So nobody can own the project because if somebody owns the project The other companies are not going to invest because they are in clearly disadvantage. So the open-stack foundation is the Entity that manage all these Contribution all the all the technical resources all the technical infrastructures so it was founded in 2012 and His main goal is to provide an independent home So all the all the people in the project can be sure that is neutral that nobody has any favor for me The most important thing that is changing these days is that at the beginning the open-stack Foundation one was hosting only the open-stack project, but now and This we had a talk one hours ago about this in this room They are opening the the foundation to the open infrastructure The open infrastructure Community and they are including new projects that are outside of the open-stack all project so what's happening the Kubernetes people started with a goal of and creating a What is the name an orchestration for containers and in that ecosystem there were two other companies Like same as open-stack had eucalyptus and the other eucalyptus open ebola Kubernetes was competing against messengers and docker swam but Kubernetes was able to do the same that the Open-stack Foundation did at the open-stack project He was able to attract the massive mass of companies of people bringing so many Developers to the project that they are innovating as such a fast pace that nobody can catch up with them And as you can see they started more or less messes was a Big pleasure on the ecosystem But messes was owned only by one company since same as Docker So I think that from here we can infer that the neutrality of the All the project is important is important for the companies be And to do that what Kubernetes did is is when he released the When he released the first version he partnered with the Linux Foundation to create a cloud native computing foundation So he provided to the other companies in this neutral Referee to control the ecosystem and the project Could be could not have any favor with any company at least If you see the the evolution of the consistent you can see that at the beginning Google was more than the 70% of the other project and With the newer latest releases more companies are starting to take over the project So I think that that from this we can we can understand that this important Hold this how do the open-source projects grow is because they need a driver in the case of Linux the driver was the all this hacker community that wanted a free software wanted to have a Operate a free operating system and he was able to engage with all of them and to create this bizarre ecosystem that was able to To innovate and to create better arm software and faster than the others and everything that these Two foundation were able to do the same. He provided the ecosystem so the companies can but in this case This open-source projects are not attracting people are attracting companies that are Adding people to the project and this is how it's how the produce are growing because Of this they are providing the neutral Ecosystems so everybody can take their part of this take so nobody is Reluctant to invest on it But there are difference between Kubernetes and open stack both We can see that more or less they Were working on different products different ecosystem one ready to contain this order to the virtual clouds but They achieved this in the same results with different ways. So to understand that we need to understand how the projects are government in the case on open stack Open stack is governed by three separate governance bodies the board of directors the technical committee and the user committee the board of directors is What as I told you is who oversight the press the open-stack foundation the asset who sponsors who Deals with the Sorry who deals with the who manage the IP who manage The infrastructure is Okay and This this board of directors compose of the protein in a sponsor so the companies come Can feel that they are not investing in the blind? No, so they have a voice on the project But the board of directors is Not who leads the project. So there is a technical committee that is oversighting the technical matters in the project and This committee is selected by meritocracy. So the members is all the all the absolute project electing the committee and The technical committee had authority to determine Who can be part of the project and who will not? But there is one session for the core open-stack project that Technical committee has to recommend to the board of directors the modules the module for addition combination is pretty To the region from the core of the project This is important because we are going to see how the Kubernetes and the cloud native foundation is handling this in this case the board of directors has a war on the on the technical side This there is also other user committee that represented the downstream users but I think that it's not important for for Dispresentation the role of this committee If we go to the technical part the technique the way that open stack is organized So open stack as we told before this one opens our core projects And there is this new project that were differently This analyzed open cycle project that were the ones that Created this this big project like it's called open stack today so for each of the projects the community or The people contributing to the project choose a ptl the ptl is the People that manage the day-a-day operation that drive the team that that is all the technical dispute dispute he's in charge of managing the the the project is the project inside of one stack and Above him is the technical committee. This is the way that more or less Open stack handles the technical issues It defines a project the project defines a ptl and the ptl Handles the project if there are some cross Relations that need help the technical committee change in and try to organize and and deal with the problems and and oversight that everybody is is fulfilling the Four opens and the open stack way and now that we talk about the four opens. This is important because this is something Interesting regarding the open start project so to be able to be part of the open start project You need to follow the open stack way with the four open so one of of this One of the Important things here is what these four opens means so one is that the project has to be open sure that's important because as we say before is the The the call has to be open. You cannot have licenses or or Any copyrights that made the product the project? Closet or that can deal with liabilities So the other is that it has to have an open community But here I highlighted one word is the open community statement impose that this should be public and in IRC So this is something interested that we are going to see after that is we one of the Four opens is imposing one tool that this is going to be funny for developers for sure All that is that the open development and Here we have I highlighted two other things is here isn't posting to Other two conditions. So the project has to have code reviews in the open stack infrastructure and It has to be test driving by the gate in the open stack infrastructure And the last of the four open is the open design so the open design has other condition that Everything has to be discussed in the open stack that made in this Okay, so far so good The four opens rule look really nice to me and I really think that they're able to to achieve What open stack ones but what I want to highlight is now the difference with how Kubernetes is handling this I don't want to to make An impression that I'm in favor of one or the other thing I just stating what open stack is Is what are the open start requirements to have a project in the open stack code? So let's go to the to the other project to the Kubernetes project So as I said is the Kubernetes project get released with the version version 1 1.0 in 2015 and for that what Google this did is to partner with the Linux foundation to for the cloud native computing foundation So they saw the mother we have a foundation the foundation handle handle everything so the companies can put their money and We can create community we create community we create We accelerate the development and the open True project can Cancellate But this is one of the main difference so the claim native native the claim a cloud native foundation is Totally different to the open a staff foundation. It's only an Administrative entity they are only focusing in organization marketing and strategy. They are focusing on Only an oversight in the projects, but they don't impose any rule to the projects just that they have to be related to the cloud native guidelines and The governance models in Kubernetes is different. So you have a foundation and you have a project inside the foundation don't need In open stack, we have a foundation. We have Projects in the foundation, but the technical committee has to report some technical things to the foundation This is one of the important details that they want to highlight in the as the difference between both models But let's see how the the Kubernetes governance model work what we see is that in open stack we have World directors technical committee projects and ptr per project What the current is governance model has is he has a stealing committee and this is important Because it's all an important difference with the open-style model the stealing committee Requires discretion and Committees sorry committees don't have open membership. I don't always I don't know talk with operating the open. That's a important difference with the Open-style model, so we have a committee that can operate That cannot operate in the open and this is the committee that rule all the Kubernetes project they have and to be a member of the committee you have to To go to election and you have to be elected only by members of the project and I want to explain after that how the members are elected in the in the Kubernetes project and Why so difficult so different with open-style model, so Okay, so the committee is the The entity that rules the the project but he has this especially interested group that are the ones that rules the The technical parts of the project and this is a totally different approach at an important in open-style in open-style you have projects per functionality per Network per storage and in Kubernetes you have one project and you have this special interested group that organize the basic organize the project Based it in different aspects for example this one see for Scalability that is one see for network All the code is in the same repository But different six manage the different the different goals or scopes in open stack is Every scope is managed by a different repository by different project all the interesting difference between both projects well the six can Problems of communication and for that they create these working groups that are communities that are able to create and to deprecate that are organizing this these to handle this load and this Topics that doesn't require a sick and this is what they wanted to spray to spray this for the stealing committee There is no There is no Criteria writing so the committee can change the criteria right now in the last election Everybody that was member of the project could vote but the contributors with The contributors with some requirements more than 50 contributions or people that were helping the project that could request to vote Could be eligible to vote What that is mean? so if we check today to the Together some numbers to the presentation I Suggest you to use these two tools so one thing of both projects is that they are really Want to do the thing right and there are a lot of a lot of tools and a lot of analysis and a And a lot of statistics to analyze here But the important thing that they want to highlight. Let me step back. Okay, it's Okay How can you be a member of the community? How can you have a vote so? Independence that community to have a vote you only need to be to be a foundation member You are a foundation member you come both For that I think that you only need to request a form I don't know a sign An agreement or a license agreement. That's it So is you we see the graph? I don't see the openness that community The data that I could gather from the annual report of the foundation is about 80,000 Members so that's impressive. So I think that I don't know if this is right. I get this in this data from the So if everybody can Know that I'm committing some mistake. That's pretty. Let me know but If this data is accurate we can say that for the to elect the foundation board to vote You only need to be a foundation member and right now there are 80,000 person that can vote for the foundation What's happening the Kubernetes Kubernetes doesn't vote for the foundation they are Total independent of the foundation they vote for the steering community the steering committee is there is the entity that rules the project and What do you need to vote first you need to be a member and To be a member what does it means to be a member you need to be an active contributor in the community and For that you need in addition to commit to the project you need to be sponsored by two reviewers and The two reviewers cannot be part of the same company, so they are creating this This kind of chain of truth like in when you are signing your GPG case I'm creating a meritocracy based on relationships and code That's totally different to the open-stack approach. So that means that if I'm right if I write the current number of members in the Kubernetes project is 372 Compared to the 80,000 that are in the open-stack project So these people can vote and can check can change the elections with their vote The other main difference and I added this as mighty is what most of the developers like is They represent a totally different approach to the problem. So open-stack is more. Let's say all the school in the sense that The main tools are great IRC mailman As well You can see this one common common denominator here is all these tools are open source open stack is very very Proud of open sure and it demonstrates is trying to demonstrate it every day They are using open source tool for creating open source over In the other side kubernetes is a cloud cloud native project and they are very cloud native So all the tools are cloud tools you see for chat They use a slack for mainly least Google groups collaborative Google docs super for support forums stack overflow so this is The the profiles of the people is totally different to if you go to one event or to the other you can you can notice these things and now what we can see is that The fight between the foundation is about to what I explained before is about to gather people gather Generate expectation and one of the main tab is to do to do this is the summit So open stack was able to you just see the graph Open stack is started the extinct that was in Paris or in Austin the first summit was able to bring more than 4,000 people to the summit and was able to keep the same page during a long time with a with a big Big spike in 2016 But in 2015 Kubikon started to create His own sub they started. I don't know. I think that is about five hundred person since six months later More or less about the same people, but if you see the train You can see the Despectations so What this graph means is that? something is doing the marketing people at least in the in the cloud native or Foundation something is doing great because it's able to go from 500 in 500 person in 2015 to 5000 same as open stack in 2018 and this week these two events are competing so I will be really Looking forward to seeing those results the other competition that we can do is the About the contributors we were talking about people that is member member can be anybody but the project needs needs code needs people calling and This graph is interesting Open stack was able to to gather such amount of developers that were able to to have In 2016 more than 3000 contributors committing call to the project. It started with about 500 and in 2016 they reached the top with more than 3000 Contributors right now. You can see that the number of contributors is decreasing, but Still is higher than the Kubernetes one And you see the Kubernetes one they start in in 2015 but the project was initiated before I don't remember I don't recover the Saturday the year so they have more Put request creators and put request reviewers in 2015 But you see how the trend is similar to the could become they are they are getting momentum and they are able to match the open stack numbers, but currently Open stack is still has more man power or more Contributors than Kubernetes So what I try to highlight is the difference in the project not in technical differences how The projects are Governor how the communities are format what the question why That most people is doing is why How is the project manager who is the community who manage the community and That was my intention and hope that this could clarify some of your doubts. So if you have any question Hello, I work in a bank and so Very often we have the question internally. Should we involve ourselves in an open source community as We can see that the major contributors are always technical companies like technical providers and not business companies like bank or other kind of companies well, I'm trying to Explain how the these projects are so big. So you can see that they They are big because the company sees that they can obtain one benefit Investing in open source is always good because You are not you are always going to have a revenue if you create open source over Doesn't matter if the company sleep. You are always going to have this over so for me if I have a company of I Will always recommend to invest in open source You can invest in the foundation. You can invest adding developers is the good thing It's up to you how do you want to invest the important is that you are called will be Licensed it so you cannot distribute the code and you cannot impose any copyright so nobody else can use it I don't know if this answer your question Excuse me, sir. Just one one one question Can you please go back to the page which is showing the platinum members and the projects if you don't mind What what's the friend the platinum members of open stack and the projects the projects? Yeah What do you mean this? Maybe before This no towards a friend Yeah, this no Yeah Again back it seems like Yeah, just But this isn't in this isn't the way page of open stack You can you can this is the open stack dot or web page so you can get it from there Yeah, I have to reference in the bottom These are truly open source projects that every everything is published, but what they wanted to highlight is There are entities that are managing the project and they are organizing everything and they are pretty good in doing what they are doing and Thanks to that. We have the summit. We have the seven so we have this open source project that are sustainable and that can I Ask you something like here if you see the platinum members list most of them like red hat Susie and Ubuntu is not there Like they they are the the Linux people they are more into into this so Why is that because they accept the open? Open source well, or that they are good in doing the developments. I mean what is the reason for that? Okay, let me let me go back. I explain this So I have some Slice to spend this this is the the software revenue model No, I see this is how the company work when you have proprietary software What do you have you have a license is you have contracts? So you tell the people you buy my lances my licenses and your model is about new engagement You need to engage and you need to maintain That's the what is the problem is the company is go out the project is deprecated the customer doesn't have anything What the open source bring to the to this market you the project is free You can take the code and you can compile yourself, but Who's able to compile everything who's able so that's why Susie red hat and this company grow is We are going to do this stuff for you So you give us a subscription or you want a new feature we can develop it. It's a new service this is how the The software revenue model changes This is why open Susie Susie's in and red hat and all these companies are in all the open source projects because we build open source and we We we have business around the open source. You mean to say that they were doing the same model before in in terms of operating system like Yeah, that's just for it's not only for open stock is for all open source Software, you know, we create open source over because our business model is about subscription So you want to use open source over, but you want that open source software have is compatible with your With your operating system, you have the right kind of version You have a back you got somebody to fix it this kind of things anyone else Okay, thank you