 Hello, everyone. Welcome to our topic. Today we are going to talk about the Hexon event in China. Today we have three speakers, please. Let us introduce our number one at first. He says, this is Fred Li from Huawei. And also, come on. This is He Rai from Tencent. I'm Jin Feng from Intel. We three people will talk about our Hexon event today. In the last several years, in the last four years actually, in China, we have held eight times the Hexon event in China, eight different cities. It's a very, very efficient and happy event for the overstake community, for the developers. The time we can see, the first time we hold it in 2015, April. And the latest one is this year, spring time. This table is for the data. We calculate how many bug fixes in the Hexon event and how many engineers attended and how many companies contributed. We can see in the history, we have totally, we have 817 bug fixes for all the related product in overstake. And also we totally have 26 companies in China have attended this event. And for the engineers, we can see we have, the first time is only 20 engineers. But after that, more and more people have attended this event. The latest one of this year, totally 102 engineers attended the event. And this page is also some numbers from the history of the Hexon event for all the eight times. We have totally three Platinum member companies have supported. And for the gold members have 14. The gold member, I mean the overstake foundation, the gold members. And the corporate sponsor has eight companies. And organization, maybe the organization is not some company. It's just from the, for example, the government organizations or other similar community from the industry. Yes, totally a live organization has contributed the resource and the people to make it. And also we, among all the attendees, we have two super users about customers for the overstake. It's a very prominent number. And this page talks about how the Hexon event in China, maybe it's not direct influence. Maybe it's indirect influence. Along with our Hexon event, the overstake, upstream contribution number has also changed when released by when released. We can see from the data from the latest six releases. In the first time, we can see the total in global, in the world, the 166th company to have contributed the overstake upstream. And from them, there's 18 companies. And the company from China and more and more in the latest release, we can see now the global number has become 175. And from China, we can see the percentage has increased a lot. It's 45 companies from Chinese has a lot of contribution to the overstake upstream. That's my part all about the data and the numbers. The next, yeah, is right. Okay, thanks. Okay, now I would share some general procedure about the Hexon. I hope hopefully you are going to run in the same Hexon events in your country. I think from the figure you can see, it is very typical event management or event operation procedure. Every year we need to have the plan, then we have each for each event because every year we have two or three. So we need for even we have a plan and then we need to do the promotion and run it. After that, we will review and get some feedback from the events and then as a feedback to our next year's event and next event plan. Okay, the first phase, the yearly event is quite important because we need money from different countries or organizations. So without the yearly plan, we don't have the budget. So basically, we are trying to make sure how many to decide how many events we have and how much we need, how much money we need. This is basically information. And for each event, it's a little detailed because we need to know which city we need to have the event in. Because China is a large country, we need to consider the engineers distribution, where the engineers are there. And so we need to confirm the sitting time and how long it will need. And also we need to get the defined scope and how many sources we need so that we can prepare in advance. Regarding the scale and the budget, that's okay because we have the yearly plan. But we have our technical team need to decide what kind of activity we will have during the two or three days. In the promoting part, basically, we will prepare all the logistics. And also our technical team need to use all the communication tools to communicate with different people. To involve the engineers from different communities or different countries or different organizations. Of course, sometimes we can invite some customers because from there we can get the requirement. And we can get more how our product or our technology will be used in customers. The fourth phase is how to run it. I think that typically we group the attendees by technologies or communities or tasks. And then they will work together and have the discussion independently. And after that we will summarize the output and also yearly we will give some prize to encourage the people to join the event next time. And then, sorry, this is a table. It's a table. It's a fifth file. We need to review and call the feedback from different people and then we can optimize the next. For example, next year we are going to change the grouping ideas, grouping way. This year we group the people by technologies. But next year we are going to group the people that buy ideas. We can have the idea and then we can group the people across the technologies or projects. Okay, at the end I present just a small summary about what we have done since the last eight Hexen and what we plan for next year. First of all, the first thing that we figure out is just there is a gap, especially a cultural gap between developers from China and other countries. And sometimes Chinese developers have worked very hard but they don't know how to present their ideas and they don't know how to do the commit to the community. And this is the reason why we organize as many as Hexen as possible. So the reason that they can be well integrated to the community and know the whole procedure, how we can do the upstream contributions to the OpenStack Foundation. This is the first thing and the second thing, we like to change the scope for the Hexen. We call it the OpenStack Hexen since it works only for the OpenStack projects. And now for the next year we are calling it Open Source Hexen, means that not only for OpenStack but also for other projects just like Kubernetes, Harbour, SAF and other Open Source projects we will all bring together. The same reason as we change the name of the submit here. We try to make it more open and large scales for other projects since now for most of the users of Open Source we will use all these software together. And for Hexen we will do the same thing. We bring all the software together not only for the eyes but for the path. Also we would like to bring some AI projects, Open Source AI projects together. I think that's all. Thank you. And just to show you last time the photo and this is our Hexen and many as participants. Okay, thank you.