 Hello, hi. Oh, yeah, the mic is working. Hi, good morning. Wow. There's quite a crowd given we have daylight savings So thank you all for making the journey an hour earlier I've been really honored to Give the art to be asked to give the keynote here at scale and First of all, I'd like to wish OSI and open source A happy 20th anniversary as many of you know, it's it was 20 years ago that the term open source was coined and What we've been doing and what we see People that have been in the community for a long time doing is storytelling So what I'm going to do this morning is is storytelling and and talk about Some of the things we did in the early days that really Help kind of put together the building blocks to enable our success and a lot of the things that we take for granted and Looking at some of the popular projects and some of the key people that were involved So Yeah, one of so at 20 years on You know open source is one. That's what we're being told right and Linux is everywhere and Open source is also everywhere in the cloud We have one how many people here thinks we've won Okay, that's a lot fewer than hands and I thought So look at these numbers now these came from the Linux Foundation, you know, 23 million over 23 million developers 41 billion lines of code 64 million repos on github and 1100 new projects a day and So this is significant amount of growth. We're also seeing that, you know software is disrupting markets But it's really open source that has been the biggest disruption in the software industry We didn't do it overnight. It took us 20 years or more to get here and You know, it's open source. It's the 20th anniversary of food softwares also been around for a lot longer than that. So We've got a lot of people consuming open source and When I ask an audience how many people typically When I ask a non-technical audience, how many people here are using open source very few hands go up because they really don't understand That behind, you know, every device that they use And everything uses open source even the phone. So And we're we're gonna see a bigger group of developers joining our community from companies that are consumers and They're not yet contributors and they want to learn From kind of what we've been doing over the years. So I can see there's a lot of very Seasoned people within this community. I know this community has been Active for a very long time and scale has been going on for a long time as well. So it's gonna be important to tell our stories and not have folks Feel that this is like, you know, just a given this is like how it was handed to us and The work that went into getting to this place that we're at now And we have as a community a lot of sharing to do. I know that there's been some great talks This week here as well and really really packed rooms So in the beginning I'm gonna tell my story and that's what's happening this morning and You know Being asked to share my story I knew that I always wanted to travel the world and work with different cultures and learn about them And then I did a computer science degree and then this happened as my career so the various projects the companies that I worked with and some really like interesting Milestones for example, you know getting the UK government to select a standard for Open technologies so that all government software would it would enable open source to work alongside other software As well. So, you know, I guess the stars have really I feel very blessed very aligned within my career That I had some of these opportunities including summer of code setting that up and running that for the first two years and It's really taken me around the world and working with really brilliant minds in the industry and As a student, I guess most kids at all, you know, you can do programming Or do systems analysis and I guess back then that's those were the two options And I wanted to do both and I wanted to do more. So it wasn't until much later 1999 when I found open source and that just really felt like a calling and The journey with open source open office Started when it was announced in 99 The project, I don't know how many of you use open office or Libra office Fantastic, wow, that's pretty much the whole room. Awesome. So You know the journey started the code base was seven and a half million lines of code so for the time it was a really really large code base and It was interesting because the the company that was acquired by Sun Star division was based in Germany. So most of the developers were German English was not their native language They all sat next to each other working in an office where they've been They've been collaboratively developing the software for 12 years and and we then had to release that code base and Engage and build a community around that code base and evolve it as well We had some incredible help from Brian Belendorf who is one of the Apache founders and Also, he ran a company called collab net and we had You know all the things that you would expect in say an Apache project now with mailing lists all the right mailing list dev lists projects structured in a way that It was easy for newcomers to come and go and Figure out which of the pieces that they wanted to work on And they represented the various modules that was available in the software and We kind of learned from Some of the folks that had come before us, but there weren't too many of those back in 1999 and 2000 so For me open office was a really incredible journey after that I went to work on the net beans project and I had the chance to travel to China when we were releasing net beans 3.6 the localized version and and you'll probably recognize this gentleman on the screen James Gosling father of Java and James came along on this trip to release a local language version and Talk to kids in the university Talk to developers across China and we also got to travel Along the Great Wall walk along the Great Wall of China together as well At Google I was fortunate enough to Be part of the Well, actually, I was the only one that traveled with Vince surf through Germany and Austria visiting a whole bunch of Universities and taking long-trained journeys and part of that was trying to understand what would the universities teaching kids? and how much open source was included in that education and along with that having Vince on the journey we got to meet the commissioner of the European Union and Influenced at that higher level as well about the need for Open source in education You know on a trip to Kenya, I spoke in Nairobi and working sitting alongside the ICT ministers Minister for Kenya and The audience is really a government education group and We talked about I talked about Google Summer of Code and how it was easy for students all over the world to participate in that and and Mark shuttle with was also there as part of canonical Ubuntu and I got to travel back mark and the Canonical crew on a private jet back to London. So, you know some some fun things It wasn't all work and here's here's another opportunity where traveling to other countries and this was in 2006 so In the early days really kind of helping spread our message to lots of different Geographies and Individuals that were working within the community. So here we had, you know, my friend here Denise Cooper who's sitting at the front She actually took a lot of these pictures But Jim Zemlin who heads up the Linux Foundation. He was just starting up the Linux Foundation at the time Brian Belendorf David Axe mark from my SQL so it kind of felt like a now it feels like a who's who of open source But above all of this, you know, we kind of travel two conferences and Tell our stories and when you look at the 200 or so talks here, you know It's storytelling or teaching your craft and that's a really really key part of what we do It's, you know, not just the mentoring within projects, but it's also Sharing sharing what you know sharing and collaborating. So it's essential part of growing your community and Then events and conferences the open office community was very creative and There were community hosted conferences in different parts of the world. The last one was in Barcelona this one is in Copa and again all organized by volunteers on a very tight budget and You know, it's so great to come to community conferences like this and See kind of the networking and the collaboration that goes on so my first lesson is that our communities are global and seek out every opportunity To connect and in connecting you will also be recruiting for your projects as well And that's a really important thing to do. What a friend of mine who works at AWS and he was at Apache con last year and He said that we were all recruiters and I kind of I guess I kind of squirmed at that thought but you know Later realized no, actually, it's a big part of our job to go out and we engage with the community And when we make that connection That's when we get Individuals collaborating and coming and working with us. So it's a big part of what we do The next story is about finding your tribe How do you play now? How many here are new to open source? Wow, okay, one hand. Okay. Wow. So this is not the norm and I was expecting this to be a very seasoned Community and community of developers and contributors. So I Guess for the gentleman in the back, you can come and see me afterwards I am not going to spend too much time on Actually finding your tribe, but it sounds like those of you that have been contributing for a while have actually made a connection and Found and connected to your tribe, which is really really key. So with open office as well, you know again, very early days of open source it was really important to make sure that the values of your community were articulated well and You welcomed people that came to your community and you shared and you actually shared not just the information but You know your craft as well So so here's for I Guess I don't need to ask the question now. How many of you have been doing this for a long time But how many have been doing it for more than 10 years working in open source? Okay, fantastic. Wow, that's over still over half the room So, you know finding your tribe, I mean tribes are in different forms Some kind of I know for open office it started off mostly Initially was the German contributors and the community already working around the code, but it didn't take long for it to spread Globally particularly because it was an end user Application we were developing which mattered to many people Because they were looking for something to run on Linux. They were looking for it to run on operating systems that Current office productivity suites were not available in so and part of it is not just Contributing but also for the new people in the community is finding your mentor and You know in open office it was and this was taken in Beijing at one of our events but Mentoring was very very key early on and you know, you will hear this in many many talks now, but it's really The this is the reason why the community one of the reasons the community really grew and was successful that we were able to Mentor the first set of folks that joined the community and then they in turn did the same and we kind of had this like huge kind of like branch of a tree spreading out and Supporting the rest of the community that showed up remember people didn't know what open source was or how to even engage at that time I Felt we did a really good job in open office You know, I mean summer of code was a really good example of how mentors can engage with developers and help Bring people up to speed very quickly so they can be productive and this is the Apache tribe and I was very honored to actually take this photograph Of the Giants on his shoulders we stand so a lot of the lessons that I've learned From the early days of open source have come from a lot of the Apache community members people like Brian Bellendorf and Greg Stein and Given you know, so many hands were up in the audience The key to success in your project is also about leadership and building and using your leadership skills and I'm working on organizational development And it's not just about the code that you're involved in or the key activity But kind of looking around and looking at the whole community and even now going Okay, what's other communities doing that are? That are growing those communities, how can we change and improve on what we're doing and in the early days We did a lot of that so there was some conversations with the GNOME foundation with Mozilla We were trying to kind of also learn from each other so mentoring sharing collaboration and Also learning Just the key they're the key to learning and development and You know these lessons seem like yeah, of course duh, but really this these are the lessons from the early days that have kind of come forward and Enabled us to be successful in what we're doing today so This story is as kind of an entertaining one I don't know how many of you remember this ad on TV I wanted to play it but No, it's It's an Audi ad and I kind of grew up with this tagline, you know, war spring Duke technique now It really stands for Precision in engineering and and German engineering was kind of considered a Almost like, you know, what everyone else was striving to achieve and So I with the open-office community and the developers it was interesting because the developers really prided themselves in perfectionism and really building something that was going to go out and actually be perfect so in open office you know It was it was interesting because Yeah, we kind of needed to teach people how to do peer reviews how to let others look at their work and Putting putting out code that Wasn't complete because we would building we're doing developer releases and and they weren't complete But every build that went out the first couple of builds there was absolutely nothing wrong Like everything was fixed everyone was just hunkering down because it was their work that was being Displayed and nobody You know this they were used to working on a product, but they were releasing for end users and We had an incident where this build build 613 Was released and suddenly and it was broken It was broken, but What happened was up until that point the the engineers were struggling To really get engagement from the community we had We just had Like people lurking there were just a lot of lurkers. There was one guy who started working on the Linux PC port and he was a academic from Canada and He was working on this port, but there were very few because the code base wasn't very modular You know there was engagement and porting and in localization but the core part of the code was really really hard to get into and So many people just lurking and watching and then all of a sudden with the 613 build it went out and there was this hive of activity going on in the mailing list and the engineers were just mortified that they actually released something that was broken and But it was the best thing that could have happened to the community and to the project so What happened was a lot of people got involved in the conversation and we ended up Really kind of having a collaborative effort in fixing it and there was a there was a big lesson for for both the Sun engineering teams are active in the project and the rest of the community to learn as well so here, you know perfectionism is not always your friend and Leaves things for the community and of course we know that you know release early and often It doesn't have to be It's it's fine for it to go out with bugs because that's where you get a lot of engagement in the community But these were hard lessons learned by Teams that were releasing code and it wasn't just the open office community This was happening in many other projects and you know a lot of the time at the time There were a lot of companies that were pushing And releasing their code and making that available as open off open source Nowadays with GitHub a lot of the code already starts out as open source but there are still instances where companies are releasing code and Some of those lessons still need to be repeated so that people can actually learn from them now this next story is about being the change and You know whether it's an open source project or a program and like Google Summer of Code or like Outreachy You're working with people. I'm just checking time. Okay. Yeah, and we you know Linus is Is known for saying many people are known for saying that really it's about the people The technology is the easy part of what we do It's actually working with the people and getting that part of it right is the is the biggest challenge, right? So You get not just community but you also get you know the good the bad and the ugly that comes with it and I think it's important and from the very outset You know one of the things we did was show kindness to everybody that showed up and really understand and listen be transparent in what we were doing and show some compassion The other things we did was we displayed our Mission statement and our values very very clearly. There were no codes of conduct back then now every site has one You can just go grab one put that in with your project so these were all these are all things that were developed as a result of some of these projects and As well as you know stating your mission very clearly and that helped our project really a lot because you know When people come into the community and they want to do something different you can all go back to your Mission statement and say hey, this is what we're about That is not what we're about and having that clarity really really helped us So these are two of my mentors Brian Belendorf and Greg Stein again. I mentioned them earlier from They're both part of the early Apache project Brian was instrumental in helping with open office From from his work with collab net and Greg Stein as well the other person is Denise Cooper and Denise was instrumental also at Sun not just in mentoring Me and our project but in mentoring a lot of the Sun projects and she was pretty key in Really kind of the success of open source at Sun there's a lot of innovation that happened in the community and For example, we had a small team in Hungary and innovation happened on the fringes because the Main core part of the code base Really needed to be refactored and it needed to be much more modular So that was the work that was going on While the rest of the community kind of like gathered around the fringes and here we had a small team in Hungary that fed pizza and Coke Coca-Cola to students all weekend for three days and they translated the whole of the office suite into Hungarian office by you know by the Sunday night and Actually, there's somebody from the Guinness world's records there who captured it and they they had an entry in the Guinness Book of Records for the fastest translation The other innovation was the downloads for open office just grew like crazy, you know We started off with like tens of thousands and before we knew it. We're into hundreds of thousands and Our Sun budget was running out. So we were paying for Akamai servers and for the downloads and Because the money was running out. We didn't know what to do We just didn't hadn't factored that in and we ended up asking the community If there was anyone who could help with this and within literally You know two months two to three months. We had 45 mirror sites set up all over the world that helped us with our downloads and really the fact that we had Little money for it Wasn't really a problem. So there was a ton of innovation there and then See innovation Doesn't just happen on its own. You have to also set up an environment as well For the community to innovate. So in the early days You know, we had a lot of pushback from the community that it wasn't so easy to engage and one of the problems was a copyright Agreement and the Sun lawyers had written a copyright agreement that really required all the contributions to be assigned to Sun under this license and A few community members in the early open office Who took the time really to explain to us that this was a barrier to community engagement so they were not happy about it and of course there were lots of heated conversations and they wanted to really work collaboratively with us and Explain explain to sign explain to Sun lawyers You know why it didn't work for them and especially in Europe, you know There's something called moral rights and you can't transfer your moral rights over to a company either So this was a problem for European law as well You probably know this gentleman here Josh Burkus So there was Josh. There was an Italian lawyer on the key in the community John Luca Tocconi and and someone in France Geek apra and three of them. I remember were really instrumental in helping us understand the importance of changing this and Denise was also instrumental in this in working with our legal system into in Sun and making sure that we We actually got the Sun lawyers to Work on this and and not dismiss it. This was a key part of our success Right, so it took about a year to change so you can imagine the conversations the meetings But we did change it and we changed it to something called the joint copyright agreement Which meant but the individual also retained all the rights as well as providing those to the project and Yeah, it was quite it was quite a job convincing Sun to change it and It wasn't just changed for open office, but it was also changed for all of Sun's projects and everybody benefited So just in the same way that some of these things some of these Ways of working that have been tried and tested in these communities Getting shared and getting shared at conferences like this. They're the ones that actually help You know other projects and on a much broader scale so the lesson here, you know is really it's about people and communication It's about listening that's a really big part of it and really being open to change and You know, I was very blessed that we did have lawyers in Sun who were who were open to change and the community that really had the patients to learn and Help us fix this and that's what really led to a lot of that innovation so I Had to put in trolls in here, but unfortunately, I'm gonna disappoint you because we were very lucky as a community We had a lot of people He showed up in the community with a huge passion to help us and help us bring about change We don't recall any bad incidents. Yes, he took conversations and there were there were discussions. Absolutely You know, we formed a community council because a community wanted to have a bigger voice Across everything and typically when you have a project that's released by a company most of the developers tend to come from that Corporation initially because they have that knowledge base but over time that should change and It should change to have a much more inclusive voice and so as part of the change It requires some interesting conversations see one of the community members did fall out with a few people and He had some ideas and it wasn't around code. It was around documentation and he wanted he wanted to present the information in a very different way and Attribute it in a very different way as well and He fell out with some of the community members because they didn't Understand what he was trying to do because it wasn't the way they had selected to do this You know, there wasn't anything wrong with that But so they kind of dismissed him Maybe they thought he was a troll and they just kind of dismissed him and he went away This is what typically happens in projects if people ignore if it's not something that's invented here. They ignore the individuals and here what happened was he went away and he built a website and he Demonstrated what he really wanted us to do and then when I looked at it and others looked at it It just felt like yes, this is the kind of thing we should be doing within our community But our current infrastructure did not allow it and that was a limiting factor you know the the service that we had through collab net did not allow us to do that and But it was it was a really great example of a community member going away and actually doing the work somewhere else And he created this website called 000 docs And of course there are people unhappy about that, but there was also an overwhelming support of yeah This is something we should be evolving to to doing We knew that the infrastructure wasn't going to change at any time soon So we provided links to that site and we kind of embraced him And gave him access to a whole bunch of webpages. So he couldn't he could actually be a webmaster on the project as well and It kind of ended up being a really positive results for the whole community. So again, you know Innovation doesn't always happen within the frame of what you know It happens elsewhere and this is a great quote from Bill Joy So, you know, let people help and Understand if somebody is passionate and they're having a heated conversation they care about what you're doing and If they didn't care they would just go away So in this next tail, I'm gonna present I Guess I had I had depicted Companies and benevolent dictators for life of projects As kind of the dragons, you know, they contribute code They provide the sponsorship, which is much needed. They provide resources they provide support developers lawyers money And it's a great ecosystem when all of this works well and It's for the companies. It's really and the bdfl's It's a whole dance between control and support And I don't know I don't know how many of you work in large corporations here Releasing open source projects and and have worked on open source projects Where the code was contributed by a large company or a by bdfl You're kind of It's a really really fine balance, right? So for example in in open office We had we had son donated the code for the Mac port for open office to the community and often what happens is The code is donated and at some point the developers are moved on to another project and This happened with the Mac port the six developers that are working on the open office Mac port were moved to another project now Now We had one of the community engineers Developers we had we had an individual in the community who was proactively working on the Mac port once it was released and He created something called at near office I don't know whether any of you on the Mac have used that but he added an additional clause To his contributions for new office so he could take basically some financial donations to keep his work going and That really freaked out the Sun lawyers They were trying to break that he thought that he was trying to break open office and That it would reflect really badly on them the press really loved the Mac port because most of the press were Mac users and We got some really really great reviews and write-ups because of that But the company's reaction was really not to embrace this new office port So and meanwhile The former lead for the Mac OS project, you know the guy who was running this team of six developers His heart was still in that Mac port and even though he's moved to another project He actually came he actually left to the company and he joined the Ed or who had actually created a new office and he started working full-time with Ed on that project So the company lost, you know a really really good developer now It's it's a symbiotic relationship between the organization and Living as part of that community and it was in this story it kind of shows that that basically you can take your skills you can take your talents and Choose to go to the projects and the work that you want to do You know, it's companies are starting to realize they can't just move open-source developers off of a project Onto another one because you know that project kind of lives on and The control and support There were a lot of lessons learned by corporations and and still do and I think as we have more and more enterprises participating in open-source and Releasing their code as well. There's a lot of lessons here to learn In actually letting go when you're releasing it to the community provide the support But the whole need for control companies are going to find that The earlier they let go The more rewarding it will be as well as as a community relationship Okay, so The next story is on superpowers now You've worked with others that have excelled with superpowers and you see them you see them in your community, right? and So what are your superpowers, you know, maybe some of these I don't know But in reality right You're just brilliant at what you do as whether you're a coder where your creator whether you're a leader You know whether you're Great at creating and collecting people You may be a good listener You may be great in your community as a mediator when issues come up and that may be the best time That's when you really shine You may be the warm friendly person who greets everybody and that is your superpower But you all have superpowers and it's important not just to recognize your own but to recognize that in other people so You know, we looked at the Giants some of the Giants earlier and You know look at the people in your community that you feel are the ones that are The the leaders that are the Giants and why why what you're doing is successful And what can you learn from them because the one thing or open source affords a lot of great input into our careers But also it's learning from your peer network and if you're working in company, you're not going to have Necessarily the people with the same skills that you look up to as you will in your community as well so You know, how can you learn from others in the community? And the other thing that's really important I think really important for the I guess the kind of generation of Developers and community members that are coming into the projects is that it's actually really really hard work. We have all been doing this work for a long time and It's not something that You can transform overnight that people want to come into a community and It's like six months work. No, we've been doing this for you know 20 years and some of these projects have as well So recognizing that it's not something that you can just kind of speed through and it's an important It's an important lesson for companies as well. So here like yeah, everyone's got superpowers and You know, none of anything that's been accomplished in open source has happened with speed Okay, I just wanted to leave this page intentionally blank just a pause So the last story is on the reward. What why do we all? Working in open source and I think everyone has a different reason for Contributing and participating So the open office story here is that you know, as I said earlier natural gravitation Towards languages in the community just because you know, it was something that would sit on everybody's machine and It could be used globally by a large consumer base so typically with an office productivity switch or something like a Browser or some of the kind of the basic software you need on a machine To run your like your operating system as well and back then GNOME was very actively involved in this work but with languages typically company will only translate into maybe 25 languages maximum any any kind of users any user software and That was a big problem because when you look at India India alone has 200 languages so we look at how many people are not getting the opportunity to work with technology and the barrier to learn English is way way bigger than The barrier to actually learn technology That was a huge insight. I had at a conference. Actually. It was at the Copa conference When I had somebody from Cambodia saying, you know In our country people can't actually do very much of technology because there's such a big part of the population that just doesn't speak English, so Libra office was translated open office and Libra office now is available in over a hundred languages and We really supported the language community and we had this thriving Engaging group doing translation So that's my father on the Screen he's 87 this year and he came from a village in India in Gujarat and He really understood the value of education over 25 years He raised enough funds to buy some land a group of them had a high school built and then a junior school and And Now there are over 1500 kids that go to that school that would not have had an education Because the schools were too far away and for most parents in the villages. It really wasn't Important to send their kids because they wanted them to work in the fields. It really wasn't important to send them to school. So, I am I It's about my my my folks are from the Gujarat both my parents and With open office, I was given a CD of Open office in Gujarati Which I actually took to the school and installed on their donated computers So that the kids and the teachers could actually start to learn and use the technology and use the computers ahead of learning English really well and You know for me, it was a really huge reward to be able to be in service and support the education of this school and and support the work that my dad was doing and These are the kinds of moments that matter to me In the work that we do now those this kid who did that translation in open office and He and I got to know each other over the years and especially because he mentioned I kind of looked up Gujarati and he was doing the work so we connected and He did the work for Firefox. He did the work for many other applications as well and the really cool story here is that He got through his work in open office and through his reference he is now he did his engineering degree and Because everyone could also see his work He was hired as a release engineer for Wikimedia foundation and it's the kind of opportunity like he was in this small college in this remote village in India and it's a kind of opportunities that these kids like really only just dream about So open office has not only just and the work has helped, you know improve kind of the technology skills of People all over the world. So when I travel from Nepal in the south of India to sorry in the north of India To Tamil which is spoken in the south I've been given off open office translations or CDs back in the day For all of these languages and in Africa as well. So We're really as a community doing open source have Engaged a very kind of large global force out there that is passionate And we may not see this in the US But as you travel the world you really start to see how much support and Engagement there is for the work that we're all doing and so You know the rewards might be that you just love being in your community And you love the work you do the people that you work with But a lot of the TED talks that I've watched when they talk about like humanity and what is it we want to? What is our purpose what we what really sparks us a lot of it goes back to belonging and connecting to people that are share your passions and that you that you actually Collaborate with and enjoy It's a big part of learning as well which sparks people or in my case. It's also the being in service and the bonus for this kid and so many I mean there are just So many stories of people that have got careers in open source or careers in technology Because of the voluntary work or the work they did in open source So it really is your reference and the community is your reference So I want you to kind of leave you with a couple of things to think about one is you know What are your superpowers and how do you use them? What are your stories and I'd really like you to share them I am Zahid to be on Twitter So he to be at Amazon. I'd love to hear them Our work isn't done, you know, we have much more to do and it's not the end I'd like a few acknowledgements here for the folks that have Contributed to the storytelling and the book Yeah, so those are my that's my information if you want to connect with me I'd love to hear more from this community as well and one of my co-workers is speaking right after this So I said that I would give her a quick plug. Thank you I don't have them. I don't think we've got much time for questions Yeah, okay. No problem. Cool. So thanks everybody for for joining us this morning Zahid as is our as our custom. We'd like to welcome you to the scale family with a personalized jersey Oh, thank you everyone. Thanks for joining us and being part of the team Again a couple just a couple quick updates as I mentioned as Zahid I mentioned dear Joe be speaking in Room 103 at 1130 about marketing your open source projects Again, Ty shipman who is going to speaking about credentials and passwords and access control after death has Unfortunately, and is unable to join us, but Kyle Rankin has graciously joined graciously volunteered to give his sex sex God and Passwords his brief history of bad passwords at 1130. It's a longer version of his upscale talk That was that was given last night. So he'll be in room room 106 Other than that, please don't forget to pick up your scale t-shirts on the expo floor There's still quite a few of them in booth 431 and we look forward to seeing you throughout the rest of the day Thanks for joining us at scale and see you in 2019