 So thank you for introducing me. My name is Hirotaka Motai. I'm a work as an engineer and an OSPO staff. So I'd like to introduce our OSPO comic manga. So have you get? Yeah. Thank you very much. So it is being distributed our booth. We are our company's sponsor. So if you don't, didn't take it, so please come out first. So anyway, so this is a slide to the copy. So I'd like to introduce and so where is my castle? Here. So it this comic is based on true story in my company. So and so we are making the two type of commercial Linux distro wines for enterprise and the other for a minute. So so I think it's a reason why we decided to build up the OSPO. So this situation is samples. I mean, how can I say the sales person, a new salesperson, maybe customer asks why your Linux is not free. So I guess the the emerging of my customer Linux is never to use free of charge. So he's questioning its point of filing next. Your reaction is not free of charge. So and the the person says engineer says man can not reply correctly. So he related on the special engineer. He know the lot of parties open source. So does this station is not as not good to our company. So Ospo is a bridge role between internal department. So we we believe the developer should focus on development. So this is why we building the Ospo. So please take it and did it. So that's all. Thank you. Thank you, Anna. So I'm Kyosho. I'm leading one of the topic in the Ospo, Japan local meetup. So let me introduce these meetup things. So so I'd like to explain why how we organize this meetup or this subgroup. So at several two or three or three years ago, the Ospo keyword is becoming popular. And then at that moment, the member, many members in the open chain Japan working group had some interest in that and want to know that I want to understand that. So first we started to study the GGI groups, GGI handbook at first to understand what Ospo is. And after we did through and study that, we next step, we decided to have a discussion in some topic of the Ospo and that. So we discussed mainly two topics. One is discussing on some simple Q&A and the other is discussing on the OSS strategy stuff. So for the simple, so I would like to just briefly introduce these two activities, discussions. So first one is a simple Q&A or maybe easy Q&A. So it's a little bit so so so we are having some discussion. So we just gather some questions from the members and pick up one, pick up such questions and have a discussion on that and try to make a simple answer for that question. These are some candidate, some questions, discussion candidate and we discuss several of them already. But so during this conversation, discussion, so we know there are so many materials, presentation things in this kind of event or some website, but during the discussion, our syllabus, we can deeply understand what Ospo is or this kind of topics. So that's what I think it's very valuable for the members in this discussion activity. And one example of our result is looking like this. So this one is a question is what are the benefits of the open source activities. So during the discussion, we have a lot of opinions or a lot of ideas for this answer. But there are so many and then we think we find out we can sort our ideas based on this maturity models. So maybe the benefit looks like different based on where that person is. So this is a little bit complicated chart. Maybe we can more make some summarize of each part. Like for example, maybe so we can maybe just summarize each part and then makes it more easy to look at and useful chart. I think I believe so. And there's another example is a question is what is Ospo? It's a very fundamental question. It's also how we have a lot of answers, opinions. So we did the same way, just brought that answers on this maturity model things. And then we have some kind of idea of what is Ospo right now. So again, during the discussion on this, we have more answers, but understand Ospo deeply. And also we have some idea how to explain the Ospo to our colleague or our members. And also maybe, yeah, I think it's very good things for the members. So another activity, oh, I'm reading the other simple Q&A things. And I'm reading this part, OSS strategy part. And this is some result of our discussion. Also, this is very busy things. And also it's not finished yet. So in this discussion part, we have just, so we thought the strategy may be different based on that company's business. So we categorize, yeah, categorize as a business in the line. And plot some characteristics of the business. And also put some issue point for that business. And based on this chart, we are having a discussion. What is a typical or what is the point of the strategy for the company in that category? So this kind of discussion we are doing in our local meetup. And every second Friday on the month and every fourth Friday on the month. So now we are discussing Ospo in each company should do for open source community. So please join us. For this panel discussion, I've got some questions to all of you, because you either have deep experience on working with open source communities. You either are on the way of building an Ospo or you are part of the Ospo. So my question to you, the first one is when looking at the Japan market and Japan ecosystems, what issues do you think that open source community have here in Japan? And anyway, yeah, yeah, like anyone is free to raise. So let me reframe, yeah, sorry about that. Let me reframe the question. So you were mentioning like sometimes it's hard to have. So the Ospo role is to also engage with the community. But this is one of the major issues that or at least I would like to know what is the situation here of the major issues of the engaging with these open source communities and how can the Ospo help? Yeah, in general, of course, some advanced companies have culture to contribute to the community and some company joining very strategically the open source communities. But almost all legacy company in Japan is contribution is almost all voluntary from each engineer. And this is outside of the work. So this is I think a very big issue because I think to maintain the ecosystems of the open source is one of the very important part of the software development of the world. This is also same in Japan. So our open gen and the group promotes the importance of the contribution of open source software. And I think Ospo is one option to access it. So we also promote to set up Ospo in Japan also. By the way, do you want to say something about yourself or for self introduction? I'm Masata Endo from Toyota Motor Corporation. And in Japan work group, I am a leader of the promotion subgroup. Promotion subgroup promotes not only open source compliance, but also open source retail and Ospo also. So yeah, thanks so much. And we can keep doing the round of presentations. I really apologize. I completely forgot about that. So next is me, actually. So hi, everyone. I'm Ayumi Watanabe. I'm from Hidachi Solutions. It is an IT company in Japan. And I'm a consultant, especially for open source management and SBOM. So actually, I am not a member of Ospo or my company, but I am the person who help your Ospo how to do your activity or how to create your Ospo. So answering your question. I saw a lot of people from Japanese companies and they, the common understanding of them is as mentioned, as Endo mentioned before, open source activity is like, how do I say, just a community work, not for the benefit of a company. So we need to change those understanding actually. So maybe individual persons, individual developers who is really passionable to do community work, but a company has not so. So it is the situation in Japan, I think. Yeah, thank you so much. Motai-san, again. So as I mentioned, I work as a developer and Ospo. So my question is, it is important to keep the motivation for the developer to the community. But in general, most, almost the Japanese company has a rule for publication. For the material, it was built in the company. So I think Ospo should do the change, the rule, beyond the developer. So developer had to keep motivation themselves. So I think it's very important to act in Japan, maybe. I think Ospo have to change some mindset in the company to support the engineers to contribute about the space in the open source world. So that's a big thing, I think. But these are important things for Ospo activity. And in Japan, how do you see the general awareness of the Ospo? And how do you think that this awareness could increase in the next year? It's a general question, so everyone is free to answer them. So according to my activity now, Ospo itself is a little bit difficult to understand and explain to the people who don't know the open source especially, and also some top management for people. So that's the biggest thing we have to fight for. So as far as I know, the number of Ospo in the company is a little bit increasingly increased. It's not sharp, but definitely increased. So maybe in the near future, Ospo is common sense in Japan, maybe. I believe so. My understanding is the same. Ospo is not so famous in Japan actually for now, but recently, for example, S-Bomb is very hot in Japan. So next year maybe, Ospo is more and more famous in Japan. And to do that, we need to promote the benefit or how important Ospo is to the management of companies. Yeah, I think, as you mentioned, Ospo is not famous in Japan. But for example, the industry, Rai and Yafu, this is a very big platform in Japan, Majid. And their new home page says R&D and open source. So open source is very big topics of the technical development of software. So I think awareness is increasing little by little. But how to spread in the legacy company as automotive industry is a big issue for us. So next year, I'd like to expand over Japan. Yeah. Also, Ospo is an open source program office. So the world program is a little bit difficult to understand. So normal software engineer thinks it's a software. But the open source program is not a software. So that's another thing to explain the most. I think that it's a worldwide question. Yeah. So actually, I'm laughing because I'm from Spain and we say open source office. Like we skip the program because translating it is like redundant. It's like, no, program doesn't make sense. To answer that, and I think it's important also for the audience to know, because you might have heard of organizations that they don't call it an Ospo. But the mission that those entities are having is how the Ospo operates. So it's like bringing this strategic view on top of open source operations. And the way that I usually explain it is I feel it's fine to don't call it an Ospo internally because the organizations are going to be different. But it's good to have externally like as a common term. So if we are speaking, we don't need to go from one term to another. Everyone understands what is a marketing team. Everyone understands what is a security team. Maybe you don't call it a security team in the organizations. I feel like it's kind of the same with the name. And I totally encourage people to use the name that better works for the organizations. Because I keep having these questions also in other regions and I think it's important. I do also have another topic, another question. Because you have briefly, sir, some of the value that the Ospo can bring to the organization really briefly. But I don't know if you have any other ideas or recommendations on what kind of value can the Ospo provide right now to the Japanese organizations. A very most easy way is to appeal the risks of the open source software because Japanese executive concern about the security risk or some legal risk. But I think if we focused on only the risks, I think misunderstanding will be happen maybe. So I think to install the culture of the open source is most important thing. And not only culture, but also to connect each activity to each business of each company is most important thing. So I think most reasonable ways, it is very difficult to set up whole companies at first. So we promise one good example, good case, arise inside the company and spreading over the company is the most reasonable way I think so. Yeah, that's true, and I totally agree with you. In my opinion, the most important thing that Ospo can bring to your company is maybe open source culture, I guess. Now, commercial company are using a lot of open source and they need to make better relationships between open source cultures and open source communities. So to bring those cultures into your company, Ospo is the best way to do that. So I always recommend companies executives to do Ospo work because if you want to use open source, you need to follow their culture. So you should make Ospo to make your company fit into their culture. So from the point of the engineer, because I'm an engineer. So I think that C-level, I think C-level should consider the risk for leaving the developers because a lot of rules make them confused. So it's simple, but it's so difficult to resolve. So I think it's very important to solve from the engineer. As I explained, there are a lot of benefits of Ospo. So maybe it depends on what is your most problem is and Ospo will help to solve it. So it depends on that company's case. I see. And as a final question, feel free to answer if you feel comfortable. That can be also a question for the audience afterwards. Since now we are in open source summit in Japan, we are talking about this status of Ospo in Japan. Do you have any recommendations that you can give to organizations in Japan that doesn't have an Ospo, but they are willing to start one? Like any recommendations on how to get started? My opinion is that maybe the risk management is the best way to easy to start. So maybe a compliance staff, maybe the first one to working on, it's not easy to complete the compliance staff, but it's very easy to start in the company. That's my suggestion. My suggestion is the first step is a lot of workers come here and touch the culture, open source culture. So it's easy, but maybe they get a lot of awareness. Why as a company contribute to open source or why our company doesn't contribute yet? So I think it's easy, but it's important to act. So you mean like attending to conferences? Yes, exactly. If your company has no Ospo, but maybe your company has a special team for a compliance, open source compliance maybe, because Japanese companies love compliance. So my suggestion is if you have your compliance team, maybe you should start with education for developers. Through the education, maybe you can tell the importance of open source or a little bit cultural thing about open source. So maybe one step further to open source or Ospo, one step is maybe education I guess. My suggestion is very simple to hear the real needs of each engineer, because even if we develop the very advanced strategy of open source, no one can understand it makes no sense. So at first at least there are some needs of the contribution or some headache of the license issue or security issues in the company. So we hear the well and we discuss well with the engineer and the two solid real needs at first. This is very open source approach. I think Ospo is also have to solve. So this is my suggestion. Thank you so much. So I think we have a few space for questions. We wanted to leave some space in this panel to go through questions that you would like to ask to any of our panelists today. Thank you so much for joining us. Thank you so much for joining us. Thank you. Thank you so much. I think to discuss with the government is also a good strategy in Japan also. Because Japanese companies are very sensitive for the intention of the government. But unfortunately almost all open source issues are about security. But security people also want to know about how to handle the open source inside the company. So I think compliance or contribution people is also same issues. Same practices needed like open chain. So we cooperate with METI like financial government in Japan to discuss about what is the best practice in Japan and how to spread the open source, appropriate open source usage in supply chain also. This is one strategy in Japan. I have, it's just my personal thought and this is more related with my experience in Europe with Ospo's being held in governments. I think right now we are seeing a massive growth of Ospo's in the government sector. But I believe that they are like really on the very earlier stage and they need to evolve a bit more. But I believe like maybe in the near future having Ospo's in companies, public administrations and other organizations. Those Ospo's are communicators. They are the linspin, they are the linspin between the organization and the community. But they can also have these conversations with the Ospo's in governments and these Ospo's that are in governments will be this linspin to the government body. So I believe like these Ospo's are powerful not just to connect the open source community but also to connect with other organizations. And no matter they are private or public administrations. I just believe like needs more time to be settled because well open source is a completely different view and needs as we have been mentioning in this panel discussion education and time. Any other questions or thoughts? Source code or commit, contribute? Yeah, yeah, of course in Open Chain community four or five years ago Fujitsu-san disclosed the rules of the contribution in the company. And of course other companies also can. So it is very difficult to disclose all material. But I think it is very each company can provide you as a information. Open Chain community, so it's kind of really difficult to understand Okay, I think so Open Chain is someone thinking about the license issues. So but so we collaborate to the to-do groups. A to-do group is most issues are sharing the information about the Ospo. So we joined collaboration project. And of course Kato-san Panasonic also joining it. So please Kato-san share everything. And also maybe we can have some discussion group in the Open Chain or to-do group to find out, summarize some typical rule set, general some rule set for the template for so every Ospo in the company can see it and promote it in that company. Maybe you can have some such kind of activity in this open source way. Okay, thank you. I think we are on time. So thank you so much for this panel discussion, for sharing your views and your remarks. And thank you everyone for being here and saying until the end. Thank you. Thank you. Thank you very much.