 Well, um, hello and welcome everyone, um, very much appreciated everyone who, uh, appreciate everyone who showed up Friday afternoon after lunch, hopefully also after coffee or a big amount of water. So you will not snore here and, um, in order to also try to facilitate no one, uh, getting sleepy. I'm hoping that maybe the audience will have, um, the, uh, remaining energy to participate. Let's make this a conversation if we can. Uh, so I'm not just the only one talking here. All right. So what is open source without collaboration? I'm asking before, uh, we go into trying to answer that, uh, a little bit about myself. So you know who to blame for hopefully not boring talk. My name is really co venture. I work as director of community at the open infrastructure foundation. I do a lot of things, um, but I'm trying to focus a lot on really community, uh, involvement, participation. I'm a community manager for one of our projects called starting X and I will not talk about that project today, but, uh, we will talk about really, um, the importance of, um, not just using and consuming and appreciating open source, but also participating and help building and maintaining whatever open artifacts that we are talking about. So let's start with the first half of the question. What is open source today? Because open source is not a new third, not a new term. Uh, it's been existing for a long, long time now, but what does this mean? What does this term mean? And what does this term mean to you all? Question is this a marketing term? Who thinks it is? Raise hands. There's one. Everyone else thinks it's a no. Who thinks it's a no? There's, there's roughly three. All right. And we have more people who abstain, um, they are not participating in yet, uh, forming an opinion. So, um, do we all kind of accept that there are people and organizations who are using open source in a marketing context as a marketing term? Who says yes to that? Yeah. All right. People are nodding and raising their hands. Um, that is a good thing and a bad thing at the same time. It means that open source really means something. It is something that catches people attention for many, many very good reasons, but it is also something that has a huge effect on the open source ecosystem. It kind of creates a little bit of a hype curve for open source itself. And I think we are kind of navigating this hype right now and, uh, I will get back to that a little bit later. So is open source just free software free in the, in the sense of you don't have to pay for it? Who says yes? Nobody. I will not, not ask who says no. Hopefully everybody says no. Um, although, um, would you agree if I said that there are still people and organizations who think about open source, particularly that way, a lot of nodding and a little bit of maybe, um, I do personally have experience with, uh, with people kind of not really saying it out loud that open source is free software, but, um, they look at it as something that, that they consume and through consuming open source, they kind of think about it as something that they didn't have to develop. They don't have to maintain. It's not their problem. They kind of getting it for free, which is again, something that becomes a challenging thing. Is there anything that, that you would, any of you say, if I asked what open source is to you, what is open source in your context? Anyone want to chime in? I have another microphone. If we have rave people around anyone? Not yet. All right. We can talk later because we have to capture what you say. Thank you. I think I turned it on. I think open source is that format, I guess, um, which helps solve the perennial build versus by problem in a lot of places. So that would be, um, my two cents there. I like that. I really like that. There's one more. I am a community manager, Deverell from GoDaddy in the WordPress space. Open source is our earned community. It is our customers. It is what our customers are. Not just that our customers are using WordPress, the software, but also all of that extender community as well. So it's also our, the partner organizations that are not us, but their software is also on our, within the WordPress community, on our things too. Great. Nice. I love it. Any other takes? All right. I really like how we are going into the things that we share, more towards the ecosystem and community. So, um, let's say what the definitions have to say about open source. So recognizing the term because open source was not the, the first term, uh, that we, that we used in this space, uh, it was rather free software, but it was turned around to be open source 25 years ago by Christine Peterson, who was, um, the person who suggested to use this term. And it was actually kind of sort of an inclusion type of, uh, effort, uh, to move away from using free software that kind of suggests the free in the monetary way as opposed to freedom and access. And, um, in that way, they kind of included anyone who thought about open source software or open source artifacts as something that they could use as part of their business. So if you're looking for definitions of open source, uh, you find an open source definition from OSI. I added the link to the slide if anyone wants to check it out. Um, what this one talks about, I will not go into the details, not the point of this talk today. Um, but what the takeaway from this one is that it goes beyond just the access of the source code. So not a built artifact, but the source code itself, uh, that it also talks about and looks into distribution licenses, what you're doing, uh, with that source code. And um, this is very important. This is kind of the foundation of, uh, why we are all here today. Uh, we all need boundaries and, uh, and a way to, to know what we can do and what we cannot do and to be able to respect each other and each other's work. So, um, if you're looking for more definitions, um, one from Wikipedia, it also talks about, um, the access to source code licenses. However, if you, if you look into the, the Wikipedia page, you will see that it also says that open source software may be developed in a collaborative and public manner. And more importantly, it is a prominent example of open collaboration. I myself like to go there that by today open source cannot exist without collaboration and that is what we'll make and should make. And we all need to, uh, participate in making this ecosystem sustainable. So how does the landscape look like? Oh, coffee. Um, I did a very brief Google search. Oh, and I got coffee. I love Friday afternoons. Thank you. And this is community people. This is community, uh, met the gentlemen through community and, uh, have a lot of work friends and we never worked at the same place. All right. So if you do a quick Google search, I did this yesterday. Fresh off the boat data, fresh out of the oven, uh, however you want to call it, you will find numbers like just in 2022 alone, there were 20, no, 52 million new open source projects just on GitHub because GitHub is not the only place to put an open source project into. I marked the, the sources on the slide. None of this is my, uh, data, um, again, quick Google search, first three, uh, matches, um, 52 million as a large number. And it also says, uh, 413 million contributions. I mean, I'm from a country, Hungary, that has less than 10 million people as a population in the whole place. Like, you know, I can't even count this far. And, uh, that's just 2022 GitHub alone, JavaScript space. They say 25 million JavaScript project versions. World wild, another huge number. And something that, um, a gentleman here from Mercedes also mentioned in his presentation, uh, I think yesterday or the day before it doesn't matter day before, um, that is really interesting. Um, and nice to see that we have this number that, um, 70 to 90% of any given piece of modern software solution, um, has thoughts in it. So, uh, that kind of shows that whether or not you're aware, you're probably already consuming open source code. Um, and that is really, really important. But when it comes to open source again, just that landscape, that number, there are a lot of challenges that came with something that's that large. One thing is rapid growth. Um, my personal experience, I see a lot of new projects, new repos, new activities, new ideas popping up on a daily basis. There are just a lot of them. And, um, when it comes to rapid growth, everybody's trying to do something because it became really, really popular. It became popular for a very good reason, but it is still something that you have to learn, understand. Um, and, uh, you know, be a good community citizen. It's not something that just happens from, uh, just happens overnight. So, um, don't try to run before you know how to walk. And just because crawling seems faster than walking, um, maybe it's still not the right thing to do. Fragmentation, um, again, an example that I, that I personally seen, um, there has been an effort that at least I've been following. And then another really, really similar one popped up on another continent. And, uh, it's also almost the same scope or big overlapping companies who are supporting the two efforts, and it will be probably almost the same people from those overlapping companies, uh, who will actually participate in both doing almost the same thing. So, um, do you really have to have your own way? Or maybe there is more room to actually collaborate and do something together. Food for thought. By the way, if anyone disagrees with me, has a question, things that I said something stupid, raise your hand. I have another microphone. There you go. So, um, please. Consumer challenge. So there was the, uh, the 72, uh, to 90% number out there before we all love data and, um, that is the, um, something that we kind of not mistaken, um, as open source, but. Consuming is one thing, but if everyone thinks that, oh, I'm just consuming it, it's not my responsibility. Uh, why would I maintain it? Why would I do anything? Why would I even talk about that, uh, that I'm using open source software? Then the whole thing, the whole ecosystem will eventually just collapse. Um, there was a conversation at a conference where I, where I participated where the term free loaders came up, which is practically anyone who consumes open source without participating, you know, you're just watching from the sidelines. Yeah, not my problem. Well, it hurts me too, but someone else will, you know, solve it. And I don't agree with using the term freeloader, but it sounded an interesting one to share because it really points out the problem that if we just keep treating open source software as somebody else's problem when it comes to maintenance, we are all in trouble collectively. The maintainer challenge. So, um, freeloaders that, that, that applies for both new and existing projects. But when it comes to, um, well-established, uh, not new, you know, running in production, it actually works stable. And then you're kind of starting to lose contributors. Why is that? Where did the maintainers go? There are companies who, whose core business is relying on that software piece, and they're still over at the next hype booth. Why is that? How is that that piece of open source software down to the level of maintenance is not part of the product development and maintenance cycle internally to that, to those companies who are relying strongly on that software. So what now? Tell me what now? What, what do your phones say? And the laptops, what now? So, um, the steps towards open collaboration is actually something that you have to realize that is something that you need to do. And there are so many things that we just don't know. I don't know. I've been in here for 10 years and I still don't know. There are so many things that are, I knew how it was, I don't know, five to 10 years ago, but it keeps constantly changing. So we need to observe the ecosystem. We need to observe and, and see what the challenges are, how we, how we can start to participate, how we can start to improve what's not working well. We have to learn, we have to learn about each other. We have to learn about the technology. We have to learn about communities, how they work, how they operate internally, how communities are collaborating together. Um, and if they don't, uh, we have to share what we know, what information we have, what feedback we have. Um, many people think that, um, collaboration and no person's good contribution. That's just code. I'm not a developer. What could I do here? Possibly, um, share your feedback. Are you using that software? Do you like it? Do you not like it? I want to know. I've been working on it so hard, worked on it for years. There's a feature. It took me three years to get into one of the open source projects, big victory. But after three years of almost literally sweating blood by the end, I mean, it was a long process for various reasons, but please tell me, does it actually work? Do you like it? Or did I just do it for nothing? I don't like doing things for nothing. And if we implemented something over the course of three years that you actually totally hate, please tell me so we can fix it. Um, so share what you know and educate. This is something that is every single person's responsibility in this room and overall everywhere on the planet and around the planet who are floating in the space. Um, it is a collective responsibility. You all are here. You already figured something out. Go and educate those who are not here. So many empty seats. I know it's Friday afternoon, but still so many empty seats. Where are the other people? Where are they? So I rolled up the abstract and I said that there will be solutions. So here I would like to introduce you a new initiative. We call it, um, community blueprint. And this is something that, um, that is built on experience, your stories. Are you new? Have you been here for, I don't know, 25, 30 years, 10? What is your experience? What is your story? Share what you experienced. Um, what you have to say about open source, the open source ecosystem, the tools, um, language, spoken language, coding language, and help changing someone else's experience for the better. Yeah, we have, we have books out there about open source and I do read books, but sometimes at least personally, a lot of personal experiences here. Um, the textbook doesn't always translate, um, to your everyday life. Just because someone tells you how something works, it doesn't mean that you can apply that process to how you're doing things in your own context, uh, at your company, in your home, wherever this example applies. Um, you don't always know how to do it yourself in your environment. And then we already made the assumption that someone actually read the book. Sometimes we don't read the book. And the other thing is, um, there are a lot of people in the open source ecosystem already. So if this is something that you're thinking about doing, you're not alone. We are, a lot of us are here already to do this. And at the same time, um, you are not alone in the sense of there's someone else out there who faced similar challenges as you did, who had similar experience, good or bad, something that they learned. Uh, and you also learned, um, or if not, then maybe you're the first person and, uh, when the next one joins, they will feel like they are not alone in this. But again, for that, we all have to act as a community, collaborate, talk to each other and share. Um, and this is what the community blueprint initiative is all about. So we all can share our stories and with that, we might have someone to get started, maybe we will raise awareness of something that we are just, maybe we're afraid of talking about it. Um, someone just raised the example of, we're talking about hospitals, but we're not talking about the money challenge. You build up the Ospo and sometimes company leadership, your board will ask, okay, how we are financing this, how does it fit in here? Where does the money come from? Where it goes? How will this all work? If you don't talk about this, how, how will they be able to figure it out? Is it in the book already? But if it's not, if we don't talk about it, we'll never make it into the book. Help someone improve. Um, very often there are people there who just, they just didn't know. You can't expect people to know every culture, every language, or just know what mood you got up in the morning through a text-based chat. They don't know, you don't know, but if you communicate, if you participate, if you share, then we all will know better. We will have more awareness, more proactivity and more empathy, which is all crucial for open source, so much further beyond the code. Inspire, do you have a good experience? My first open source experience was so good that I'm working for a nonprofit open source foundation and I don't want to go back where I came from, I love it. And I'm so fortunate because I know that not everybody's experience was like that at the same time. Again, this is open source, open collaboration in a public space. If something happened, you know about it, you see it. The same example in a corporate environment, you don't know. When you know sometimes it's when you read it in the news. And if it's like front page New York Times, that's really bad. And that could be harassment. That could be so many things that happen behind closed doors. And people still prefer that over the open source, open collaborative public environment where you see it and you can go and act. Not everyone harasses other people because they like doing it. Maybe someone got up in a bad mood and just they don't know better that day. Don't always have to take everything personally. At the same, at the same time, there are people with disabilities even to the level of the autism spectrum. They are really bad. They are challenged with communication very often, but they are super smart. But if you don't know about what they are going through, what their experience is, what their disability is, and you just think that, oh, my God, this is an awful person. Then, you know, we're we're all in a really bad place. But if we share, if we share experiences, share that these things exist, then we can all collectively do better. So how you come into the picture, share your experience, help the the open source ecosystem by telling your story. How did you come in contact with open source? What have you been doing? Was it a good experience, a good journey, something that you're still struggling with, something that you learned, something that you couldn't solve yet, let's come and solve it together. The link points to a form that will ask for basic information. What's your story? What's your email address? So we can get back to you and get you be part of this ecosystem of people who are helping each other and helping anyone else out there who who's listening. And with that, thank you all for listening. And now, since we have a lot of time, is there anyone here who would like to share an experience? A good one, a bad one, a frustrating one. Or anyone who has questions, either what I said or anything that you experienced that you're just you couldn't really figure out how to put it in the box yet in a box yet. We had a slide up there about fragmentation. Oh, I don't even have to go back. You don't have to. Yeah, and I thought that was an interesting one, especially with so many foundations in place and how we foster better collaboration across all the foundations. Like you're here, you're open infra, one foundation. I've seen people from Apache and Eclipse and everything. And so what's really wonderful about this space is is that connections that we can make across foundations. So we do a lot of work to get projects, individual projects to collaborate with each other and all that. But if you could talk a little bit about how you work across foundations. That is always a tough one. I personally I come from a little bit of a telecom background, more on the infrastructure layer. And so I guess how I ended up where I am right now. And the telecom space is well, they have their own challenges in terms of moving from standardization to open source. And they're really trying to figure the space out. So I participated in projects like opnfv, it's open platform for network function virtualization, just to help people out with acronyms who hate it as much as I do. That was a project that was created to help the the telecom industry to actually figure out what this whole cloud thing is, how to put network functions into a virtual machine. It was challenging. But it was really a community that formed to do a lot of education at the end of the day, both about cloud and the cloud transformation, as well as about open source itself. At that time when that community was created, I was already deep in OpenStack, and that community was actually a really, really good experience and a really good example in terms of cross-community collaboration, because they were building reference implementations of a telecom cloud based on open source components. So what they did is they picked up some of the things from the OpenStack community, for instance, OpenStack is a large open source cloud platform, so they were using that as one of the core base components at that time. This was seven years ago, eight, a long time ago. I feel old now. So it was a really long time ago, and they both integrated OpenStack, but also looked into how to not just take the source code itself, but use some of the tests, the test suites, that the OpenStack community was creating to make sure that what they put together, that still works as expected. And when they found gaps, they contributed back to the OpenStack community. So it wasn't one-sided activity, like contributors from OpenStack were helping them to figure out how to put things together. Networking is a really complicated thing. It's really not simple. So that collaboration also helped the OpenStack community, who at that time, again, eight years ago, had a bit more data center IT experience and mindset. So understanding the requirements of a telco environment was unfamiliar. So there was a lot of education going back and forth. We know what cloud is. You know what telco and telco networking is. Let's put the two together. And since then, both communities came a long way. But that was a really great example. And actually we had an OpenStack summit in Barcelona. We had the best ever demo. We had this tall little mobile station there, like mobile sites, so you could run mobile phone calls through the servers on stage. And it was actually a failover demo that was put together by, again, a collaboration between the OP NFV, which is a Linux Foundation networking project, by the way. I should have mentioned that first. And OpenStack, that was an opening for a project. Well, OpenStack at that time. But the point is that we had a demo where I was holding a phone and Heather Kirksey, the director of OP NFV, was holding the other phone outside of the keynote room. We were chatting on the phone. I was sweating so hard. Because we had our CO with, like, this big scissor, cutting a cable on stage physically. And we were like, well, the call dropped. And I think we had, like, I don't know how many seconds or milliseconds or whatever that was. To me, it felt like a lifetime when there was no voice coming back to me on the phone. Like, oh, my God, oh, my God, this demo will fail here. And it didn't. So the call actually didn't drop the mobile base station. There you go, finding the words. It operated as expected. The call remained live the whole time. And that keynote demo is my absolute favorite ever since. Not because I was holding the phone. It is my favorite for multiple reasons. One is it was really showing that collaboration between, you know, across foundations and communities because no one could have done that without the other. And the other part is that that demo there really showed that what we all worked on in open source, it's something that you're using in your everyday life. I could have called the ambulance on that phone and the call didn't drop. Maybe I should drop the mic now. I'm having goosebumps. But that's the best example I can give you. So there you go. That's my story. What's yours? So I guess my story is coming from a non-contributor perspective in a traditional sense because my background is in marketing. So when I first started working with, and I work with Aldeco at the Open Infra Foundation, marketing was called sometimes the M word. They're like, oh, the marketer's in the room. We're not going to actually talk about things. Like what are they going to do? What are they going to publish? But like, I think it was interesting, like even talking, like listening to the presentation about like is open source and marketing term. And so, but like one of the challenges I've had was really conveying the value of marketing, what open source contributors and operators and ecosystems are doing and doing together and telling that story because it is really powerful in terms of collaboration. But you don't want like, and you want to represent the right parts and you don't want to put a term on it for the sake of putting a term on it. You want to actually showcase what's really going on. And so for me, it was a challenge to gain some credibility of like, we can do this together and I want to help y'all. And you like, I want your project to get more adoption. I want your project to get more contributors. I want your project to get more funding, which of course is like you mentioned a very important thing. So I think making sure that there's goal alignment between marketing and a open source ecosystem was such a valuable step that I underestimated going in, thinking from a traditional tech back, marketing background like, oh, there's products to sell. I'm going to market them. The sales will go up, you know. And so that was a shift and it took me some time to really educate and be educated about perceptions, expectations and results. So that was my story. I love that story. Yeah, doing it every day and it's so hard. Go ahead. Okay. The condensed. In college I found, I was the only female in a computer programming room. I found open source because I needed, we didn't have computers in the room while I was learning to code. We had paper and pencil. And a friend put command line red hat onto a spare laptop, which in 99 was pretty hard to come by. And I learned all about open source back then. A couple of years later, I was running a classroom teaching, public school teaching, needed to blog for my website, for my classroom. And I had been teaching HTML and CSS, but that's began the foray into WordPress eventually. I went through a couple of other CMSs this first found WordPress. Went to a WordPress event in 2009, but I found out about it so late that tickets were sold out. So I said, could I volunteer as a means of getting in? So my first time at an open source event was already as a contributor because I was checking guests in, which is a great way to get to meet everybody that was walking in the door. They thought I was somebody, and I didn't know anybody. And so later on became a member of the WordPress training team in 2014. That very first WordPress event, again, I was the only, I was one of four women in a crowd of a couple hundred. And so things have really changed in the sphere that I'm in now. I then contributing and two years ago I was hired at GoDaddy and part of my role is to contribute, but also it is forming an OSPO telling my leaders and directors why we cannot be the free riders in the tending of the Commons kind of examples. And so it's conveying that significance of what does open source mean across the company. Also what is happening inside the project that my leaders should know about. It's having the conversations with the executive director of the WordPress project, but also while I'm here, this is a big foray for me into broadening my understanding of open source, learning more about the nuances of corporate culture. If I'm coming from my parents and myself, both being in the public school systems, it's a different world to swim in. And so corporate is funny and open source in corporate gets weird. And in the meantime, as a side hustle that has no money whatsoever, I started a project with Open Collective with two other friends of mine in the WordPress space. WordPress Foundation does not exist to fund contributors. It's just a trademark and event legal perspective handling those functions. And so started an organization to help get people contributing and sponsored to contribute because until two years ago I've been doing this for more than a decade by that point, unsponsored and sometimes going through some pretty rough straits myself in that process with medical challenges and other things. So I don't know, I breathe open source these days, I guess. Thank you for sharing. This is amazing. And I think it's a great example and it's so inspiring to hear that how far you've come from writing code on paper. I mean, I didn't think that is so inspiring and also what you say about, you know, like you're coming from the world of teaching as well. Like obviously you understand more than probably most of us in the room how important it is to educate and help others to understand why you're doing this, for instance, what they will benefit from and not in terms of money and how this all works. I think this is amazing. Who else has a story to share? I think this is a good follow-up story, actually. The first I want to say, I think it's brilliant that you created a pathway to that conference for yourself. Like that's just, yeah, that's amazing. So I teach computer science and that's how I came into open source was I was a computing educator first, really interested in broadening participation and then met people who were teaching open source, doing really cool stuff. But my story is a teaching story that's maybe just to underscore the point of someone's first experience, which is that I developed with a lot of support a open source contribution course, which I taught at a liberal arts college for a couple of semesters when I was working there. And my students through that class contributed to the Mozilla Firefox DevTools project and was really cool. They made, you know, successful contributions to the project over two terms. But the cool thing that I wanted to share with you all is not just how exciting that was for the students, but in particular that the impact of having mentorship from within the community had on them. So we worked with a couple of developers that other faculty had already kind of found to be very helpful and they ended up doing check-ins with my students on Slack weekly. It wasn't a ton of work for them. But it was a really, really big deal to my students who would gather around a keyboard and say, Emily, can you come read this message before we hit send? And so it was like such a good exercise for them to learn how to communicate and get over the hump of the scariness of jumping into a community where you're a novice. And the really cool moment for me was the developers offered. They said, hey, we have time. If you want to do a video stand-up call at the end of the term once with your students. And so we did that. And afterwards the students, as soon as the call ended, they were all like, whoa. They're just normal people who have the Google stuff too. I was like, yes, yes, that is all of us. We are all just figuring it out and doing our best. So I think that that student started out being really frustrated in the course, and it wasn't just answers and a blueprint and assignments to solve. But by the end of the class, I had multiple students who went on to work at Red Hat after graduating. I still hear from students that it was one of their most valuable college experiences. So I think that those little interactions you can have with somebody new to open source or curious have just such tremendous lasting impact. That's also a great story, so something small can just change your life. I think that's amazing. And the other thing is just to add my experience to that story, I also did a little bit of training, mentorship within the community and community-organized efforts. And I can just tell from mentor perspective how much energy we get too from the students, like you're helping someone getting started and they're excited, you're excited, and it's just such a great experience on both sides. Yeah, like everyone just amplifies each other. Yeah, exactly. We're kind of running out of time. I think we had one hand up back here for one more story. Are you still open to share your story? Or... I missed the beginning. So is the idea that you're sharing challenges that you've overcome to help others or the way that... Yeah, I don't know. Yeah, I can quickly summarize and then we can chat afterwards. That's also a good reminder for people who are watching online afterwards and we're not able to be here for this one at the same time you can still participate. So there's a new initiative that's called Community Blueprint that recognizes the challenges in the open-source ecosystem in every context possible. And the idea is that as opposed to writing a book of how to do open-source no matter who you are, what your circumstances are, we would like to collect experiences and stories to understand what people are going through who are either trying to participate in open-source, trying to understand open-source or already have a good, bad, challenging lesson learned any kind of experience and then through those stories and experiences kind of getting to the point of how to improve the ecosystem, how to solve challenges together and how to actually apply open-source principles and processes and tools within someone's own environment and own context through understanding how others went through the same path that they are just about to either step on or feel lost in. That's the idea and if anyone has a story here or who are watching online the link takes you to a form that only asks for like name, email address and what is your story why you're excited about sharing it or what is your motivation to share it and really that's all just so we know who you are how to get back to you and how to help you share your experience with the world so they can learn or they can help you overcome something that you just couldn't overcome yet. I think my story is kind of different so I can just talk to you after but I just support the idea and if anybody else wants to chime in really quickly I'll pass the mic. Thanks. Okay I think we are out of time I think so because it was only 40 minutes. Alright if anyone has questions or would like to share an experience let's chat afterwards and those again who were watching after the fact, grab the link and then we'll get back to you and chat with you and make you be part of this experience of sharing experiences. Thank you all.