 And our next speaker is Johannes Teegs, who's going to speak to us about bringing open source skills to more people. So please give a warm welcome to Johannes. Right. So hello everyone. I'm here as part of the Inesos Commons community. It's one member. And while I'm not here giving a talk, I do open collaboration consulting community stuff and some DevOps and special things. But let me go on. So who of you ends up working in a large company like, say, 3K people or more? There are a few. And who can regularly contribute on behalf of their company to open source? A lot less. Right. So while I do see that there are people from different sizes of companies and there might be different approaches to open source, MyTalk actually spends all of these environments and roles. Inesource is a topic that is focused on enabling and encouraging collaboration across boundaries. And let me start with a metaphor. We see here at the ocean that it can be really, can be somewhat dangerous like tides and currents and that. But swimming in it can be really fun if you are good at swimming for that. And then there's a nice pool and pools are a safe place to actually learn to swim. And this nice ocean pool in Bondi would allow you to learn to learn to swim next to a real thing and to feel the gusts and the smell of salt and then to just jump into the right into the ocean once you feel ready for that. And let's go to our things. So while working in companies, I observed my personal observation. There are sort of two groups of people. First, the enterprise people, which just go about their daily coding business and possibly take advantage of OSS the free as in free be away. And then there are the open source communities and their members who are actually involved in that and do contribute and all of that. And unfortunately they do not really have that much of an overlap. But for this talk, let's focus on the ways of working. There are lots of other aspects. And actually these days, there is some overlap with more and more of these large enterprises having open source programs, offices and all the nice foundations such as, for example, the Apache Foundation or Linux Foundation, gaining more and more impact. And if OSS, like open source, would be the absolute norm, would not be having these open source focused and open collaboration focused conferences like the Nice Foster here or open source programs offices because all of that would be just standard daily business. And so while that exists, let's assume for this talk that there are still a lot of these really close off enterprises and enterprises. Yeah, right. So they do work and to some degree and brought us nice things such as these laptops or your laptop flight booking services and some parts of our cars. However, they do have their changes, challenges like they're hierarchical. They are often focused on spoken interaction and all sorts of meetings and there's lots and lots of tribal knowledge. And you need to actually find the right person first for whatever and often you have to talk to them for a while to get somewhere and get to that tribal knowledge. And they have silos and those silos have quite some adverse effects actually. So imagine you are depending on some other team and you need something from them and then they just do not have it on their plan what you might need. Some other teams might need that too, but probably you will wait for a very long time if you get it at all. What might happen is that you might end up building a workaround and a mass extra code that you actually have to maintain or you duplicate existing work by that and then you actually are responsible for the box you introduced and that extra stuff. And this could happen per team that faces this issue. Another thing that you might have seen is the case of escalation where things get escalated to all those higher ups, the big cheeses, if you will. And if you do that too often, you basically lose credibility and end up as the boy who cried wolf. So that's maybe some of you have seen some of those corporate things. Then open source. So it's great actually and has lots of positive aspects and I'm sure many of us here have likely experienced some of those firsthand. And I'll just name a few approaches related. For example, there is collaboration to arrive at a solution. This could have fixed the workaround and escalation and weighted out scenarios that I mentioned. The focus on written, archived and searchable communication often which makes this tribal knowledge more explicit and reconstructable and this facilitates onboarding and distributed work approaches. And there's working in the open, as we all noted, poor request and publicly visible that enables fast feedback and the distribution of knowledge. And actually there's a lot of fun in it. At least for me, there is outside visibility and you can do the good thing. And there are lots of other advantages for these large enterprises, far side of cost. So there are however some challenges because it is not entirely free. Maybe some of you have experienced some of those yourself. For example, in the case of working in the open, you have to be comfortable to share unfinished work and open it for criticism and scrutiny by others. And for this you actually need to create communities where people feel safe and comfortable to do exactly that and you have to keep them productive and positive. And you have to develop an acceptance and a way to deal with mistakes in a positive way. There is this case of text focus communication, which means a synchronicity and hence the loss of important non-verbal aspects. And you need to be able to establish a report with far less personal presence with people and you need to be able to create an environment that is welcoming to often unknown people with unknown motivations to join and an unknown time budget and state duration. So there are actually also these governance and licensing issues and many of us likely have learned to do this on their way through the open source community and the larger site and you likely grew while doing so and you build valuable relationships and likely also had quite a bit of fun. Proverbially, you learn to swim in the ocean directly and obviously you survived. Maybe some others didn't. And do you actually remember what got you into the open source community and how you learned to handle these challenges I mentioned and how possibly you were afraid that some suboptimal public contribution might come back to haunt you and in most cases actually didn't and maybe someone was even thankful that there is something instead of nothing and you had to learn about all these licensing things and the mess around it or if you have a company you try to open source, open source something and maybe you would have wished that your colleagues some of them might have more of a grasp of these open source ways of working or you try to hire people to work on your open source software and you needed them to have these open collaboration skills and wouldn't it actually be great to have a safe space to enable people to learn about these open source ways in a safe and productive environment and maybe if you could even get some relief with these silo innovation and knowledge transfer issues while along the way or just have a bit more fun while you still have to work on proprietary stuff. So inner source can actually act as this space that allows people to learn, fail without fear and grow their open collaboration skills on the way it can be the proverbial pool next to the wild ocean of open source and it can allow people who don't feel comfortable to learn to swim in the ocean to prepare for this in a safe way and if you grow internal projects like open source projects from the start you can actually transition them into full open source easier often and the people that are when participating in the end equipped with these skills will likely have an easier time adapting to other open source communities and will be able to act with confidence and kindness there and additionally it actually can bring the advantages of quite a bit of open source to your enterprise that would be collaboration for example this working in the open and some reduction of issues on silo and large distribution and they might even actually get to have a bit more fun in their everyday business that is actually valuable too. So does all this magic that I mentioned happen on its own? Actually very unlikely so. So I need to have some people with great open source and community skills to mentor the new and interested people. If you have a large company they can't be everywhere though and what if you don't have them in the first place wouldn't having a similar model that encompasses a few important things to start with and some documentation on that would be great. In our work we found a few roles in terms to start with making it easier to reason about that and allow you to start building and customizing your own. These are some of the hosts and the guest teams for the both involved parties the trusted committer which is what is usually known as maintainer or committer the person who is trusted with the code base and community contributor probably be what you know and if you have a very large project, a product owner and some of those people may have multiple roles at the same time often product owner, trusted committer, a fuse and you might have more than one trusted committer and yeah just like with normal open source projects. Is any of that supposed to replace everything like page or I don't know what, actually no. You can replace that, you can integrate the intent to solve something via inner source in your normal spring places for your big cathedral software project or you can have grass street style side projects and maybe they'll evolve into something bigger or just be this nice release or build automation script that is in fact used everywhere and there is surely more because inner-source actually comes in all shapes and sizes I mentioned a bit of documentation on the model for people to use to learn and a set of volunteers actually created that and they still created that, me included and there is a set of videos and a set of articles in case you don't like or want to watch a video right now and all of those are open source under creative commons license and welcome computer contributors if you would like to they are available on this nice website on YouTube as well, there's all sorts of links if any of these doesn't work just hit me up on Twitter and if you happen to have an Aralea account they have a very nice version of that prepared to write so just as with open source there are actually some challenges some similar to what you might know from open source and some more specific to inner-source and the enterprise context and like for example measurement of success incentivization of middle management some nasty text issues and there are somewhat proven attempts to handle them and they are collected by community members in something that is called the inner-source patterns sub-community and there's our observation of those challenges approaches that happen to have worked or hypothesis and collected in a sort of pattern format I've got a link at the end and they're actually pretty useful an important question is should actually be the goal to stop it inner-source? absolutely please not let's not allow companies to open source greenwash if you will themselves and call that inner-source got this nice washing label here and if you have the right people with open source guilt and you can make this case to directly open source something absolutely please do it it's the right way to go but what if you cannot make the case to directly open source something or you let the people with the skills to actually do that properly wouldn't it be great to still be able to profit from some open source work approach advantages and get to build open source skills with people on the way that might or will come in handy once you're ready to open source something actually I think this is actually a way to help more people embrace open source who might otherwise not have considered it so that's what brought me here and we have also a nice small ad a nice summit in the middle of April in Madrid Spain and there's a website if you're interested in that and I have a few flyers in the other case right and you're welcome to join us there and so that is all I have here's a bunch of links if you have any questions or other things you're interested in use those hashtags or just message me and thanks for listening some of us are here as well maybe you can put up your hand so talk to us if that was interesting talk to them thank you