 So let's start. Hope you are in a great mood. And we can get the next 20 to 25 minutes of pleasure and so on, so. Let me introduce myself. I'm Eugene, the manager in Great Alchemy, and also a work manager at the National Commons Foundation. He's the community of practitioners of the internet process, and our goal is to make the source as an industry standard way of development in the corporate world. And before I start my story, I would like to share you a question for the station in our source collaboration. And imagine you have two teams. First team needs some feature from another. And second team are unable to do it in time. And what they can do next is to provide the port itself rather than to have a feature and wait for the delivery. And after sometime, the first team returns the port itself, and providing them the open network. The first team, the team from the green button north to the west, and then success. That's how it's explained in the books. That's how it's usually a course in open source. So in open source components, we should be familiar with that. But the most typical case in the inner source world in the companies, it's when the buff teams struggling and get a good amount of questions, why it's not happening? Why I should care about the other squad? Why, how to run, and how a good amount of questions? And in the end, we have a campaign that decides that your inner source is not working. And you're going to talk how to fail your inner source collaboration. To know that ways, you can avoid them and remove that friction. So let's start. And the first is about the culture. Usually, if the company develops software as it was usual years ago, we post new stories, nor read myths, and so on. And not that much is going to catch the teams to do a collaboration. And then we can play some problems or issues when you start to talk of, hmm, let's rate, let's live together and build a common software. Of course, that can be a problem. And the same for the cultural difference side. So if you are not familiar about the differences in different cultures, so for example, I work in the multi-national company, and sometimes I have no idea why my colleagues doing something. And knowing that helps me to understand it better and to know the future and creation. What we can do here. First, we can ensure that company boosts the collaboration. And maybe we should start to think about and improve the culture before we are starting to talk about the inner source, because that can be a good offer to you. And secondly, we should know more about cultural differences. We can read the books. For example, the culture map, it's the good starting point for that. Or you can learn from your colleagues why they should do that, why they are doing something in an after-all, and that can be not a problem anymore for you, because you know why they're doing it in some way. Let's go into the second way. Second way to fail the collaboration. And that's about the matrix. That's about the question why they should do the collaboration. So, the inner source have the same roots, have the roots from open source, and all the source is voluntary. We want to treat driving and motivation about motivation about why they should collaborate games from the personal feelings, that I should do that, I must do that. And here is the same. And most driving development, because most said that you should collaborate will not work. And the answer here lies on the two sides. First, the side of the team or side of the company and company should understand what benefits they achieve while adopting inner source principles and they are listed on the left. And on the right side, we are not created, we are not imagine this list of advantages that's engineering after the inner source. They are came from the latest research about the state of inner source, just practitioners, what you had as a consequence, what engineers feel about inner source after some time on proxy, and they feel that they achieve these benefits. And only when they understand and truly believe that they will achieve that benefits, they, the inner source collaboration can appear. And on the other side, if you're both saying that you must collaborate, that's not going to be a thing. Let's go next. The next point about documentation. So you're open source masters and you know that's almost impossible to have a successful open source project and still be successful. But for the corporate world, it's a little bit different thing. And especially when HR says that working product is much more important than implementation, you can't think of projects without the need, without the need for mention how to run the application, how to start the developer, how to contribute there. And the answer here is to look on open source checklists. So for example, for this thing, you can open it and scan the items that you should have inside your project if you want to have a successful open source in the inner source project, plus some additional corporate stuff. And I call it like everything that's called. So apart from the technical documentation, you also should have and feel great if you give a mirror from the code and business documentation. So explaining what in the business starts doing some parts of your system. Great if you have in the code mode, the business post explaining how your software is working and then we can render the nice pictures from the code itself. The same for the architecture. So since you're integrating with another internal systems inside your environment, so great if you will have that picture explaining what components your system have and what external systems your system is integrating with. And the same for the integration part. Since you're currently alone in the corporate world, you definitely will be integrated with someone else, it will be great to have contract. And this contract will allow you to generate some code. It will allow you to build a device and after it's explained the inner source consumers, how your software is working. And the same for the infrastructure. You have come but your deployments are separately and great to have examples how to deploy this code. And that can dramatically increase the speed of onboarding from new inner source customers. Since you're explaining how to create everything needed for this particular software. And in there, we have set of open source implementations, set of corporate level implementations and then you can have success on the implementation for inner source. Going next, are you ready? And next about talking and speaking between the teams. And sometimes people are not familiar with open source principles, trying to look into some of the history. I will spend a good amount of time prancing the code and sending the distributions and then these contributions are easy to use. Why is it happening? Because it costs many reasons. Because it's a function. Because it's a texture and correct. Or because it's anything. And the answer here lies on both sides. On the first side, I feel great to have the house rules make them visible to explain what is your next plans for the next second ones and so on. Mentor the guests, mentor the contribution that they do those that want to get something from your system. The same for the first, but the same for the second team. Great to know those, know the functions that the system supports and so on and discuss your needs before. And that's the two-way road and that's the key answer on the question how to not waste a good amount of time while doing anything. Going next, going to the technical part. And technically, your system can be monstrous, monolid without any opportunity to easily adapt to slightly different needs, let's say. And here on the slide, just my example of a modular texture that supports the inner source configuration. What I mean, again, your system will be integrated with another and then you should integrate with a different multi-system, different external system. That means that you should have a special layer called adapter and easily replace adapter for the different environments and different systems. And same for frontend, your needs can be mobile application and some of the needs of application you can have different design systems and then your system should support a different way of working in terms of frontend. And the same for back-end, you can have different business requirements and it will be great if your system will be easily replaceable by parts and some parts can be co-canned, some parts can be custom. And that's the architecture of the approach that can help you to build inner source operation. Then your system can help as much as possible customers inside your company. Going next. And next item and next way to fail is about the most practices and optimization and so on. So imagine, you are a team, this team and you are seeing a bunch of things that have a contribution from external teams and you should include them, you should ensure that your system will not drop after this contribution and so on. And it's great to make a release especially if you have special team who are responsible for well-off, especially when you have a good amount of things and mainly to do in terms of release. And that's the painful collaboration that will be with you. And the answer here is to bring the most processes, the most optimization and so on and so on. And just a little example about that. And the point on this one here, this slide is a look on, here is an example of it, but you can explore that it's not connected on your team. We can go to your project, explore is your practices and approach that you applied in your project are good in terms of delivery, it gets all understanding, in terms of how they support this way of collaboration. Another example, give flow on the left, if you have flow or any other flow but simpler than it flow on the right. And can you guess what is more powerful in terms of, I'll say, in terms of attacking with the external distributions? I think on the right, right? And after it's making decisions and scanning processes that you use inside your project, you can answer yourself, that is your practices and tools and processes are a key to handling the external distributions. Then you have, you can apply a bunch of processes and practices that's helped you to meet with that kind of way of working. For example, each class, you can bring it to your project and ignore as soon as possible the function, especially then where it ends, this function is still not tested, but you are able to do it because you're merging it and bringing the action into both more. And then when you're ready, you are turning it on, and then you are dealing with as fast as possible. So, since you have external contributors, they will be happy to test it when you need to ensure that this whole system will be located after the contribution. You can open up the separate deployment for every feature, for every dynamic feature, and then you'll be safer to use yourself to your project that's the quality of the project. You'll be setting a level than it was before the contribution. And the point here is that it will be great if you will ensure that your infrastructure is smart now. Here is the set of open source tools, but it's just one of the examples. It's my personal choice. You can choose your own personal set of tools. The point here is to make sure that is your infrastructure smart enough, is your delivery pipeline is feasible enough in order to have the open source collaboration. And if yes, then you will be successful in that kind of collaboration. If no, maybe you should think about bringing new technologies, bringing new practices in site web projects. Number nine. And number nine, all the tests. Imagine again, you're counting incoming contributions, and each time you should do a bunch of stuff in terms of changing that easier system still or keeping your system in the good quality. And the great is if those check will be automatically because no customer wants to wait for a long time while you will save them, please change the task places and that will be transferred after one week of waiting. And that's not so good. Number nine tests, speed of working. And the same for linters, checkers, quality data to get to pass in terms of being the code of nourishment production. And that's the whole stuff that helps you to boost the speed to make the collaborators happier. So that's what this is. Both inner-source servers, the waste-coupled-nursearchs operation. The idea here is to look on them and think, are you doing something or you can wait and remove creation by doing an exercise about collaboration? And only the last point left, last way to fail, and this is the 10-way fail. So the idea is that's, so we've got these code base to make the inner-source collaboration. What can we do here in order to make successful collaboration? First, after the conference, you will go to the work and maybe if you're already working in the project that's collaborating with the inner-source, maybe you can divide the project especially who can take the punches from the source and use it by a good amount of teams and you can bring their inner-source. Second, you can assess the process, the practices, the tools that they use in this process, within this project, and then somehow to avoid them and remove that vision, start an experiment and try to bring more engineering practices that help the team to get this inner-source advantages and benefits. So in the end, the inner-source contribution will be like that, clicking on the green button and then it's done. Thank you for watching and we'll see you in the next video. Thank you. Any other questions? Any questions? Everything is here. My question, what is inner-source? I'm still trying to figure out. Then I have a question to you all. Are you practicing inner-source in your work? For you? Yes, yes. One, two. The interesting point here, that's much more practicing inner-source support but not only like inner-source. And the fact is, if you're working with that work, you can bring your company into the practices, you can find the practitioners, you can consult them, you can find partners that can bring your company, so on. And you can go to inner-source.com and you can check their materials that help you to bring the engineering to the practices inside the company. Okay, thank you all for joining me. Have a great day. Thanks a lot.