 So, hi everyone. I'm Takanori Suzuki and I'm so much excited about to be here today. Today I will talk about bridging business and open source. And I will share our experience with integration, integrating of Miracleunax with Armaniax as a case study. About me, I'm Takanori Suzuki. I'm chief open source officer leading the Ospo in cyber trust, Japan. And I also open source engineer. In 1999, first time I met open source and I knew what is open source by the famous essay, the Cathedral and the Bazaar. And after that was when I was university student. And after that, I joined to the cyber trust, Japan. And now it's at that time, it was Miracleunax. And I worked for the Miracle ZPX, the open source monitoring software and Miracleunax, the enterprise Linux distribution as open source engineer. And also currently, I'm working for the Miracleunax development system. And I also joined to user, by the way. And agenda. I will talk, explain about the overview of our company's business. And about the Linux integration. And then I will talk about how was the role in our company about Ospo. And after that, I will talk about how we bridge to business and to open source community. And finally, I will talk about conclusion. Okay, this is the rough image of our company, business and department and product. The originally we merged with cyber trust is a PKI system company and Miracleunax, the Linux distribution server, Linux distribution company. And this time, I will talk about this Miracleunax. And Miracleunax is an enterprise Linux distribution, compatible with CentOS and well. And about the integration is we integrated Miracleunax with Armourinax. We did this last May in this year. And like in this picture, we joined to the Armourinax project. And we became a Platinum sponsor of the foundation. And also joining development in the community. And now we are collaborating with Armourinax. And now our Miracleunax is based on Armourinax. And in future, our distribution and Armourinax become same distribution. So for doing this, I will explain how our Ospo supports the company to do this integration. First of all, our role, the Ospo role in our company is like this. Mainly four roles. One is bridging to open source community. And role two is bridging to business. Sorry, ensuring the open source compliance. And role three is bridging to business. And role four is managing the open source program. And this time, I will focus to this two roles, bridging to business and bridging to open source community. So I will talk about bridging to business. For bridging to business, we Ospo do mainly these two actions. And we think in my company, our Ospo, we think the open source activity main character should be a company and each business unit. So basically Ospo is helping and supporting the company and each business unit to do open source activities. So basically, we listen to the business unit and companies and suggesting how to do open source things for the business. So we, first of all, we gather the insights from each business unit. And we suggested how to collaborate with business unit to propose engagement with open source communities. And by hearing the listening to their needs and the situation, we found there's some challenges before the integration. One is the lack of collaboration with the community. Because our Miracle Relax distribution is open source, but a bit distant from the community. Of course, we sometimes contribute to community and getting information from the community. But we could do more activity with community. And actually, it's needed for more sustainable and more big ecosystem. And also, the duplicate effort is another issue. And by this integration, we think we can get benefit from by this integration. And after we joined to the Almanac project, we can collaborate to the project and there's enough stable foundation system and it's transparent community ecosystems. And because the Almanac foundation system is well made, so we can get more sustainable and independent governance in the developing the distributions. And highlight in this stage is hospital structure. We talked so much with other business unit and also the C level people like CEO and business unit leader. And actually, this is one of the biggest important part for doing this activity by Ospo. Because as you see, the blue part, the open source, that is me. Because I have, I got the C level name, I could easy to talk with other C level people and easy to communicate with other business unit. And under my position, there is a corporate level Ospo and that Ospo has some functions like strategy, compliance and promoting open source culture and education and etc. And our Ospo has Ospo members and they are from each business unit. So, because they are Ospo member and at the same time they are business unit member, so we could get more easily to get the situation in the situation of the business unit about open source. And it's more, it's easier to explain how we should. So, because there is Ospo member in each business unit, understanding and easy communication in the business unit. So, next about the bridging to open source community. About the bridging to open source community, we Ospo did these actions. As I said, our Ospo is mainly supporting the company and business unit to do open source activities, autonomously. So, basically our activity is encouraging and supporting for contribution and participating to the foundation and also the presenting the achievement and future plans that event and organization of events. I will talk about each activities we supported. About the contribution to development in community, I think that is the heart of open source. Everything should be start from here. And we could do some contributions in Almaniacs, like we joined to build system SIG and also participation in Raspberry Pi support and RISC-5 support and also the enhancement in S-BOM features and also proposing new SIG certification SIG. And as you see, Almaniacs is now not just cloning of the led. So, this, for example, Raspberry Pi support and RISC-5 support and S-BOM, SPDX support, Almaniacs original features. So, we could do some contribute to make the Almaniacs better originalities. And about participation in Almaniacs open source foundation, we became a partner sponsor of the foundation. And the important point is the governance model of the Almaniacs. And actually because of the governance model of the Almaniacs, we joined to the Almaniacs. The governance model is important. For example, in Almaniacs, first of all, Almaniacs has a foundation. So, not by some, controlled by some one company, basically controlled by the Almaniacs foundation. So, it's more and the foundation is, has stable rules. It provides a sustainable and independent, independency to the Almaniacs project. So, because of this, we decided to become the, become to join the Almaniacs. And of course, even we became to the sponsor, still the contribution in community is important. Because, as you see, the just joined to the foundation and ordering something just to community is nonsense. And joined to the foundation and also joined to the community, then we can do open source. Activities effectively. Next, we presented the achievement and future plans at the event. For example, this event in open source summit Japan, 2023, we have totally, our company could get the seven sessions. And including these three sessions about Almaniacs. One is mine and another, other things, these two sessions. About, one is about S-Bomb. Do you know, the Almaniacs is one of the first S-Bomb support, supporting enterprise Linux distribution. Almaniacs supported S-Bomb last year or almost one years ago. And we added the S-B-B-X support features and also adding the NTIA, now adding the NTIA requirement support. And that session is talking about that. And another session is about the future of Almaniacs. And this session, we talk with Almaniacs chair, chairperson, Benny. So we could present the achievement and have having the session with Almaniacs community, Almaniacs foundation person. So that is the achievement of the event. And next about organizing the event. We are now organizing the Almaniacs Day Tokyo. That is the world's first official Almaniacs event. And we are actively supporting that as our Almaniacs activity in Japan. And we could invite chair, founder and architect of Almaniacs as a speaker. And that is December 9th. It means next Saturday in this week. So we could make many achievements by integrating the Miracle Enact to Almaniacs. So conclusion, the key achievement and milestones is successfully integrated Miracle Enact with Almaniacs, enhancing the company's open source footprint. And by bridging to business and open source community, we have enabled active and sustainable contribution to open source and aligned with business needs. And the lessons and future directions. Contribution to development in committee is of course the heart of open source and still important also from now on, always. And also the OSPO structure is crucial to drive the OSPO within the organization, OSPO activities within the organization. And also understanding the governance model of open source project is vital. Like Almaniacs project foundation model is, I think is great. So these are lessons we got by merging the Miracle Enact with Almaniacs. Thank you. Do you have any questions? Presentation. I'm curious about how you are evaluated internally in your company about the OSPO activity for such as KPI or something like that. I think that activity of the OSPO or OSPO should be linked to the business success, I think. So how your company evaluates OSPO? I see, I see. Why I'm curious about why your company have decided to have OSPO internal organization. Okay, okay, I see. First of all, the evaluation of OSPO, now we have these four roles, big roles. And we internally, we break down these roles more in each activities. And our KPI is from these how much we could do such roles. And like for example, in this time, we could support the business unit and company for merging the Miracle Enact with Almaniacs and bridging with the community. We could smoothly support to do that. But that is after we could start the OSPO. And before starting OSPO, we are actually, this OSPO structure is another key point. Actually before making OSPO, we had, how can I say, we had an open source committee in the company. And we are the in the business unit member in each business unit. So a kind of a voluntary work in the company for open source. And sometimes each business unit has issues or something they want to do open source things. Then we can suggest we should do such thing or another thing. And for driving more about open source, we suggest to make the OSPO. And by making OSPO, we can solve such issues. And then after I suggest, I talk with CEO and let's make to let's make OSPO and please give me the C name to open source officer. And because of that, we could do the OSPO activity effectively. Is it okay? Thank you. Another question? Thanks so much. I understood about the KPI of the OSPO itself. And I'd like to know about each community's activities KPI of because I think a long relationship with the community is very important. And I think, but the company have to set the each year's KPI was something purpose or goals. So how to set the each community's work? I think the important point is how much binding the business goal with open source community activities. If the business goal requires open source activity, it's naturally we can do open source activity and we can continue such activities. So setting the and binding the business and open source activity is key point, I think. Is it okay? Okay. Thank you so much. Thank you. Do you have other questions? Thank you for the talk. And you explained about after joining the Armorynex, the contribution increased. So my question is the the real benefit or some kind of increase in the business side, do you have any good benefit in the, do you find the benefit in the business after the after the joining the Armorynex? The benefit of the contribution, you mean? No, no. Yeah, yeah, contribution by contributing. For example, the increase of security or increase of some functionality or something. I see. Actually, for example, for example, our company is now also working for the open SSF, the software supply chain security activity. And for doing that, SBOM is important. But, you know, just making the SBOM for software, one software is not enough. SBOM for the everything in the system is important. For doing that, supporting SBOM from operating system is the start point, I think. And that is important. So for doing that, contributing to the Armorynex and the adding support and enhancing the SBOM features in community is effective. And it can be connected to our next business. And also, there is a certification. Certification for the next distribution is, of course, it is important. And it's difficult for small share distribution. Because, you know, if some distribution has less share in market, software vendor or hardware vendor, not tend to certificate that distribution. So by merging, by joining with Armorynex, we can easily, easier to get the certification by joining the Armorynex Foundation. So that is another benefit. And also, about the building system sick, we could get the many knowledge about the building system, not only our internal of the company. So that is another benefit for building our original distribution or enhancing the distribution or new product. Thank you. Other questions? Okay. So this is everything I talk. Thank you.