 On that note, I think Alkin is here to introduce his MySQL cookbook. So he will be sharing his experience as an author and the whole journey of getting this published with O'Reilly. Okay, can I stand now? Just give us a moment. All right, Alkin, take it away. All right, thank you for eating and listening this session. And let's get connected. My name is Alkin. I'm from Istanbul, Turkey, and I'm here to share some experiences about authoring a book. Hopefully I'll share the slides you can go through and contact me if you have any questions later on. I'm kind of known as DB as my Nick. I've been in this business for a long time with the open source databases and also I have enterprise database backup. So I also like sailing and I do a bunch of time spent on the sailboat and this book is part of that. So it's kind of a work life thing that out of four chapters are written in this sailboat. So if you have any questions about the sailing, it would be a good discussion to have also. All right, this is where I work and we actually focus on Clickhouse infrastructure operations right now. And what does that have to do with MySQL? Where the data comes from MySQL or Postgres. So there's a big link between the OLAP processing and the OLTP processing. So that's where my area is. Also, it's an open source database. And what does it do? It's a columnar, fast analytics, cloud compatible database. And if you haven't tried it, maybe you can try it for the analytical workloads and ask questions for future reading or something like that. So let's get to the book. The book is also here. It's 1.6 kilograms. This book was written by Paul who is an Oracle employee and he actually didn't want to write the fourth edition. And this actually includes a developer and administrative chapters in it. So it's a mix and match. It's a solution base or why these cookbooks are solution based. So there's a problem and the solution type. Right now it's 938 pages. I think that's what the book is. And this book took about two years to write and rewriting and rewriting and rewriting. I can say that there's a lot of rewriting and reviewing goes on with these large chapters. It actually, what happens is when you actually rewrite, when you go back after eight months of a chapter that you worked on, you may not remember what you wrote. So I also call this book actually, is a miniscule expert is known in the miniscule community and you can follow her Twitter and blog posts. She has a lot of talks about miniscule, miniscule troubleshooting, things like that. So this is the primary author for this book. So unfortunately she's not here and she says hi. So how do I know this year? There's a 10,000 hour thing and actually we walked into this building. This morning there's a 10,000 hour sign. It's more or less it's a 10,000 hour thing. So it takes 10,000 hours to master a skill. But maybe sometimes on the sailing it takes 10,000 multiple miles to go. And then maybe on a motorcycle it's 10,000 kilometers to be master a skill. So it actually took me 10,000 hours to author a book. You need to have a luck to get a book published. I always wanted to author a book, but this wasn't my intention, like writing a technical book. I was kind of planning on a non-technical book. I've done some experiments and it took a pandemic to trigger this because there's nothing else to do in the free time. We were acting. So before that I authored blogs. You can check my blogs if you search Google. And I also attempted to write a booklet about like maybe eight years or 10 years ago. That also took me about like a year and a half to get. It was a master learning book, booklet. And then it got published. As everybody will talk about that. Authors from our ex-colleagues. And so I did invite many co-authors. I've spoken to the people who actually authored books with other publishers, but never got to that point. I've given a lot of talks globally. And that helped me to be actually learning about the subject and the technology. And I always focused on the same open source databases for the last, let's say a decade and a half. I go back and a little bit more than that in my professional life. But previously I was on the enterprise side of the house. So it's about three decades of experience put together in this book. Someone was saying, including Svetan, my experience, we're like almost a half a century of experience total to get to this book. So what are the stages of authoring your book? When you actually get an invitation or a kind of mutually agreed to write, there's going to be an agreement. So it's like an envy like documents to be signed. A bunch of legal documents you actually sign. And this is basically nothing but a contract like you actually join a company. And then you have to agree on the table of contents. You have to get the outline of it, what the chapters will be. Since this is a fourth edition, there was a requirement to change 60% of the book. So that was the agreement, which was a problematic at the end, but we got it covered. So the other biggest challenge for me especially was the platform. O'Reilly has its own platform and it uses certain techniques to compile a book. So if you're not like very XML oriented person or don't have an HTML experience from the past, this might be a difficulty getting an ASCII doc or a doc book. It's not like you have a Word document or a text where you could just type everything and then copy and paste things. It doesn't work that way. I'll explain that a little bit more later. And then there's an editor's assignment. So you meet with one editor, you start working and then editing will change on the way. That makes a little bit of a challenge. And then there's also supervisors that actually overlooks for the deadlines if you're actually meeting with the chapters that are... It's very commitment in the sense of like we do at work. So it's nothing but like reaching the goals in every quarter, reaching the chapters and finishing them and then packing them. But they go through other reviews later on in the stages. So you should start with the difficult chapters because easy chapters are easy to cover later on. What you should look for the most difficult chapters in the beginning because there's going to be some burnout along the way. So there's going to be a research time needed. Even though you know the subjects, you're not always academically qualified to put a statement in it. So you need to make sure that the information that we put in a book is correct before it even goes out to the technical reviewers. So technical reviewers that are assigned from the authors ask to by invitation and also publishing house like O'Reilly will also invite external technical reviewers, which can actually be difficult to communicate because of the timelines when they get back to you. So you give a chapter after the technical reviewers are done. The other part is technical reviewers may actually challenge or actually ask to make changes. So if you lose the grammar for grammar correction along the way so that you can actually go back and forth with the editor as much as possible, reduce that interaction with the editors. There's a review process is complicated. Since we work two letters, we read each other's work. Every time we actually complete the chapter section. Sometimes chapters are split. Most of the time Smith had no knowledge of certain problems that she would actually jump on and fix those. And I would just do the whole chapter or some of the chapters we would be split in between the two authors. And then there are the final edits before everything else goes. Those final edits are done by other editors. The reason is like it's a second set of eyes. It's another person reviewing your work. Editors work actually. So that's how it is. So how do we put all this together? We actually... is confirmed and then we get the reviews are done. And chapters also go through the quality assurance because there's a lot of console output. The console output don't fit because it's not an electronic version. There'll be two versions, one electronic and PDF, one on the portal and one on the printed book. So it has to be passing all those checks. Character sets, things need to look normal when you're actually from your screen to when it goes. And then they all randomly come back with a feedback because all of us and they say, okay, this is more than 132 characters. You can't fit this. You have to split this up. You can't split everything up. Some of the output are large and long. And that was another thing to do. So the other thing is the bills. The bills are done on GitLab for O'Reilly. And basically you write it on XML or XML editor or write it manually on XML, on VI. And then you push the code on GitLab, you check in and then make sure there are no conflicts. If there are any conflicts or errors, it won't compile. Then you hit compile and then you say to give me a PDF out of this. Sometimes it takes a long time. And then you wait for it to see what actually was typed in as a... That section or chapter or whatever the change you made. So basically it's a cycle of... It's like pushing the code to a repo and then checking the output of what happened after that. So there is this cycle of reviewing, pushing, reviewing, pushing. Moreover, there is also the GitLab part. So O'Reilly uses GitLab for the compilation of the book. We use GitLab for the SQLs and the scripts, all the sample datasets. So everything that's on this book, in the SQL statement, even it's a simple select star form customer, has a SQL file in GitHub repo. So you can actually refer to that, look, copy, paste and actually take an example or advance on it. So there is also the other part. You can actually complete your GitLab part. You also have to go back and make sure that all the steps in each section are covered as a text file, as a SQL file in the GitHub repo. So you have to check that in. And again, compile, check it, make sure that everything works and no syntax errors. So the good part was on the syntax errors, we were on minus square 8. We mentioned this on the part of the book. If you're using minus square 8 distribution, most of the syntax should work, other than the latest updates that yesterday we went through some of those features. So the production schedule, after all that time, there is another production schedule. So this kicks in in the last six months of the book, where we think that most of the reviews are done from internal and external technical use. There is the illustration. We have an illustration on the front page. This orally signs an animal of every book. These are embedded in your species. So there's a little bit of writing about what animal is that and what the problem is. And basically we need to protect the nature. And then there's a lot of cleanup goes through. There's a quote control 1, quote control 2. It goes back and forth and then make sure that everything is set and it looks professionally before it goes to press. And then it goes to a sample press that you get like about 10 books of an example. And then you actually take a look at it, make sure that everything is spelled correctly. No, the correction was made after we submitted because editors go through it. And then sometimes autocorrect and the spelling, some of those things can actually change. Sometimes you do find actually a minor character set encoding errors between the code because we use it at MySQL experimenting on the encoding character sets and everything that there are some examples over there. So key takeaways from opening a book. One of them is talk to other authors like talk to me. And before you actually jump on the gun, do the platform research and make sure that you ask what platform I'm going to be writing. If you're collaborating, maybe Google talk type or work type of thing might be useful and add it with the Grammar in the plugin. And you need to keep track of the process because in the larger books it gets out of track very easily. And then also dedication of time. So this is done apart from our professional life, apart from our commitment to our work. A book is a book actually you need to find and delegate the time of a box to write this like writing a blog post or anything like that you do as a site. You need to block. So I did early mornings, five to seven a.m. every morning. And the, you know, research I've done in that morning because there's no interruption. And then on the weekends I, you know, spread at least two or four blocks whenever the time actually allowed. And so that's the work life and the book balance. It's this is like a similar to doing the degree while you work and you have life. You have, you know, in other commitments and social life that goes on. All committing will kill and then it will cause other problems along the way. Again, it's a commitment. And I also wrote a very detailed blog about the book and then there's a link. I'll share that. And we also had a more detailed technical presentation of the book in Parkour University last November. So there's a YouTube recording of that also in the book. Well, I wasn't actually planning to open a book about a couple of weeks ago. I was on another conference in Pasadena and I got a book offer to write a database design and modeling for my current postgres. And I will be co-authoring with Ibrahim, who is actually a postgres expert. So we can actually combine our forces to go to this book before coming over here. We have drafted our table of contents for this book. So this will start as early as this summer. So I will share the details with a blog post or some tweets. So what's in this book? We'll get a chance to take a look at it. It's a problem solution. And then we come up with points and then describe the problem. Some of the problems are more complex than others. So in each section there are like over 200 recipes that says, okay, how do I do this? And so if you're an electronic version, you can make a search about compression or some other technique, replication security, something that you are trying to figure out. Maybe there's an example. So there was a talk about a special reference system for MySQL. This is new, updated version in MySQL 8. So one of the chapters we covered this with examples, giving some, you know, like SQL statements to use the reference system and then creating a sample table for point of interest and then inserting data that squares that. And then we can create an index on the special system. And then measure the distances between using the built-in functions. And we have some of the functions that allows you to get that. And this is again MySQL 8's improved system. But if you're actually on the location-based services that's built into the database, you can actually now try that. And this is the book. And also there are three other books came out in literally the same time frame. If you're learning MySQL, I recommend taking a look at, especially the learning MySQL. And that was my original idea and the one that I wrote about booklet. The efficient MySQL is for more advanced and high-performance MySQL is for the ecosystem. So how to get things done in the MySQL world with the proxies, backup recovery, scalability, sharding and all that kind of details in those books. So set of these four books will cover you most of the MySQL learning. And that will help you to the next level. And thank you very much. And I can take a question if there's any. Who's your co-author in Postgres? Ibrahim Ahmed. Ibrahim Ahmed. Yes. Yes. My name is Ibrahim Ahmed. I'm a principal consultant. So we will be actually altering. I will make the official announcements once more details are coming up. Any other questions? Anybody wants to write a book? We need more books. So the pandemic era, there was some gap. People actually didn't publish as much because there was less interaction. Some of the older books had been kind of outdated like six, seven years old. There are same subjects. But for more modern, as you know, both MySQL and Postgres are advancing every release. There are new features are coming out. There's more distributed databases are in the market. So there's an opportunity to don't think that all of this book was written. I don't need to write a book. That's not the case. There's always a new version like we had to spend two and a half years for a book that's on the fourth edition. So that means we cannot just sit and say this book was written three times. We don't need to write it anymore. So any other questions? Are there students here? Students. Students. You get the book. So one more quick update. I have donated from my book budget seven of them in the universities in Istanbul to students. After they read them, they actually donated to the library of the university. So I hope you actually take a look at it, read it and then donate it to your university. And then some other students can take benefit. For all the royalties from my part for this book, we'll be donated to earthquake victims in Turkey. We had a major disaster about two months ago. So I've donated donations will be coming for all the royalties from my part for the earthquake victims for this year. So if anybody buys, it will be helping the earthquake victims. We have some sample books over here and we will be signing books. Please get in line and then as much as we are allowed, I want to share some of the books with you. Thank you very much. Thank you very much everyone. And I hope you guys enjoy your lunch. We're going to have some running talks coming up very soon. And also don't forget we're going to have a group photo at 1.30am upstairs at a lecture theater. I'm in right? Yeah, so I need you to also go back to that app or walk. You need to right-click this app and then mute it. Just go straight in. Hopefully your password is protected. Oh no, you're good. Hi everyone, I hope you're having a good lunch. There is some food around. We're here for the lightning talk session which is about the game. It's this one right? Yeah. Just hope there's sound in the video. I think so. I mean if not, we can move on right? If you just click this, you probably want to be able to see the slide. Yeah, exactly. So I'll just click this. Okay, that's that. Yeah, that's exactly that. Yeah, because that's all. Because you should be the slide should be up there. Yeah, exactly. The slide should be... You know what the thing is? So maybe try presenting the game. Just for you to be able to be on this channel. Yeah. For experience and technical issues. Please gather. Please gather. I know, there's so many episodes. So many episodes. What's happening? That's it. Just share the whole screen. Yeah, that's what I'm wondering if you're going to share the whole screen. Or like, can you share it today? Because you had the tap, yeah. Oh yeah, okay. Just share the whole screen. Just share the whole screen. I should go entire screen. Okay. There we go. We do have a one minute video. That's probably the longest part of it, but everything else should be about a minute. Yeah. All right. Thank you for the patience everyone. Ladies and gentlemen, we have Brianna and Jay from GOSH. The gathering for open science hardware. And they're about to have a lightning talk from them right now. Brianna Jay. All right. Everything's working. We're good to go. All right. So I'm good. All right. Hello everyone. My name is Brianna, although most people just call me Bri. And I'm going to be giving a lightning talk today with Jay. And we're going to tell you a little bit more about a group of people known as the gosh community. Thank you, Jay. All right. So usually we use the word gosh, what the heck does that mean? What does it stand for? It stands for the gathering for open science hardware. So we are a group of people from all over the world that are dedicated to making open science hardware ubiquitous. So we have gatherings that have taken place in over four different countries. And when we aren't gathering in person, we're all talking online on our community forum. So we're all about networking and convening and holding space together as a group of people. Okay. So we talked about the G a little bit gathering, but we've got the rest of it, open science hardware. And I'm not sure how many of you might be familiar with what science hardware is, open hardware, that sort of stuff. So let me just quickly explain what open science hardware is. So I am sharing this picture. I really like to have it up when I'm describing open science hardware because you can actually see inside of this camera trap right now. And so I think it does a really good illustration of proving the purpose of open science hardware, which is having access to what is inside the tools that we use for science. So this is a camera trap that's often used for wildlife conservation. But now we can see inside of it. We can see the designs. We can see how to recreate it. And basically following the same principles as open source software, open source hardware is all about being able to use, see, and modify the designs that we use. To make science hardware. And gosh specifically is concerned with science tools. So I often think of microscope sensors, things like that, just any kind of equipment that you'd find in a lab or in some sort of scientific setting. So I won't get too into this because I know we've got a lot of lightning talks that are happening today, but just really quickly some places that gosh has met before our very first gathering was at CERN in Switzerland in 2016. And then after that we went all the way to Chile the year after. And then we actually were in Shenzhen China as well. So we've already two different continents. And because we are such a global community, we have our events all over the world and convene people from all sorts of spaces. Right. Yeah. So I'll just be just briefly talking about the latest gathering that we had. It was last year in November, October November. Yeah. Yeah. And it was happening in Panama, which is, you know, in the South America area. Yeah. Central America. Sorry. Central America area just last year. And as you can see, just a bunch of pictures of us hanging out, having a great time, gathering a bunch of geeks just, you know, geeking out about open science hardware and everything science. And yeah, just, you know, just a bunch of pictures that we also put here. You can see that's a net game, which is pretty much the exotic sort of national animal. Right. Yeah. National animal of Panama. That was, you know, a huge theme at our gathering in Panama last year, which is something we people at gosh, like to do when we have gatherings is that like to get involved in the country's culture and kind of bring it together with the whole theme of gosh and just essentially make the gathering more fun for everybody. So yeah. Right. And now she was just a quick one minute video of just what was happening at gosh last year and just like everyone's brief input and like what was happening at gosh, 2022 last year. So yeah. Open science hardware is about clear boxes. It's about being able to see everything inside of your tool, know exactly how it works and know how it can be replicated for anyone in the world. This year we brought the gathering for open science hardware to Panama. I'm really excited about having us in Panama because there's almost no place on earth where you can have this very fascinating intersection, especially for a group that is interested in science and technology as us to have both of those right there. This massive globalization right next to a bunch of howler monkeys making sounds in the jungle. Probably the most important thing about the gosh community is making these connections between all of these wonderfully strange individuals who are all incredibly active and excited about sharing their thing and finding outlets and communities for them to share with. Okay. So yeah, that was the video and over here is just a QR code in case you guys are interested to find out more about gosh and our community. Yeah. This is just basically a QR code to a rap page that has a welcome package. It's just a bunch of information about gosh. It's essentially like an e-catalog if you think about it. And you can just check it out. You have a bunch of projects up there. And yeah, if you can access the QR code, of course, you can use the website as well. So yeah. And so we won't take up any more footage of your time because you're more lightning talks. But yes, if you're free, please do come check us out at our booth, which is all the way right at the back right next to the exit on that side of the room. So yeah, thank you all for your time of attention. And we just hand it over to the next speaker. Thank you. Welcome to William Xu and the member of the Technology Committee of Open Year. Here is the first time for Open Year to go out of China. In China, it has been very popular as platform. And it has taken around one third market of the market in China. So I'm very happy to come here, to come to Singapore to do the presentation. I don't want to talk about too much about the product because the operating system is very, very complicated. So I don't want to talk about the details. I just want to talk about what it is. So Open Year is not another kind of boring OS distribution. We don't want to repeat it to be another centaur or another redhead or no federal. So what we want is to make a platform which makes everyone or every company can build their own OS. So just like if you have a small device or you have running the cloud or you're running to run the server, you can input some configuration file into the system and the system can create the OS for your scenarios. So that is the total idea. So the tools to support this is Open Year. You are a maker. So these two will be released at the end of this year. By my estimation, it will be in September. So we can get the two. And that is the rough idea of Open Year. So if you want to try to get more information, you can refer to that bus or bus, close the door. You can register to make a trial to communicate or do something like that. And finally, I want to talk about the feeling in Singapore in this first issue. I was very happy to first issue, first time for us to come here to communicate with different community, different projects. And I'm very happy that we talk about a lot of collaboration between those projects and the community. And I also feel very surprised that we never to hold an event or something like that out of time. But I'm surprised that some people know Open Year. And some people even download and use it. So it's totally, for me, it's a very surprise. So I think that is the amazing place, amazing point for the open source. So if you open source to the world, you can get a lot of audience, fans, a lot of friends and get a lot of partners. So I also meet some students here in the university. And I also meet some un-priced here. So we try to meet more and more those kind of company, partners, students, or our collaboration partners all over the world. So welcome to John Open Year. We can do some graduation and to make some divination for the OAS area. Thank you very much. Hey, guys. So I've got a talk going on this afternoon. A few of you guys are nice friends over there. Hopefully you'll be coming. So I know Brendan talked to you earlier about some of the cool things that we're doing at Express with trusted server and with Lightway. One thing that we haven't really covered anywhere and has covered a lot of conversations has been Lightway Core, which is the already open source component for Lightway. It's available on our GitHub right now. And it basically takes the essence of Lightway and makes it into an embeddable library. So this library is designed to be very user-friendly. It's pure MCC. It doesn't have any sockets in there. It doesn't have anything like TCP or UDP. It has very few build requirements. And the idea is that you can then take this library, drop it into your application, or potentially your robot or your hardware, and then with a simple callback, you can wire up this library to anything you want. So, additionally, you have either TCP or UDP, no worries. But if you wanted to hook this up to a radio receiver, if you wanted to hook this up to... I think the most interesting thing we've seen so far is Lightway over Google Sheets. And this is where you take the library component and instead of wiring the network side to a UDP socket or a TCP socket, you actually wire it to a Google API call where one of the clients will write to one column and the other client will write to the other column and then they read from the top of each other's. So this is not fast. You are not going to be streaming Netflix or YouTube with this. But if you wanted a very simple stable connection or you just wanted to have fun with it, this is a really nice way of just moving data around and having some fun. So, Lightway doesn't try to impose any sort of restrictions on you. The idea is to be as open as possible and to see what you guys can wire into it. In fact, we would love to see more people doing more things with this library. I'm talking about Lightway itself this afternoon at 5.30, up in the main lecture hall. And lastly, because our posters aren't clear enough, like we are hiring. We are looking at all sorts of different areas of tech. If you're interested in firmware and DevOps, if you wish any part of development, please do come and check us out. I will set this at the end of my main talk, but I'll be fully closed by then. So if you guys do want to come have a chat, we have great mugs, we have great bags, please do come over. We're just literally up by the final labs. Just a few feet away. So yeah, please do feel free to come and talk to us. Thanks a lot. Thank you very much. Next up, for the last talk of the session, we have Rashi. Hi, everyone. I hope you're doing well. Can you all hear me? So my name is Rashi. I'm based out of India. I am a strategy consultant and trainer with the Accessibility Lab. We're an organization that seeks to include people with disabilities by promoting accessibility in the digital world. So yeah, we... Can someone show the slides? You can, yeah. So we work with organizations across the world, across different sectors to help them with care to their accessibility needs. And we do have... We live in a world where one in seven people have a disability or develop a disability sometime later on in their lives. We hope to make web accessibility perceptible to everyone, where the content across the web interface, whether it's a page or an app, and increase the functionality of it to help people, you know, eliminate the different obstacles that we all have and we all go through while interacting, transmitting, and processing and understanding information. Some of the benefits, and it often gets overlooked, but one is it helps with corporate social responsibility, gives you a competitive advantage, helps you avoid legal risks if you are based out of countries in the US or in Europe where there is tighter regulation around this, helps you capture a good market and also helps with SEO positioning, compatibility, and there are so many other aspects. Visual accessibility also provides an efficient and safe way for people who have different disabilities for education, long-term employment, everyday tasks, and also of course contributes and introduces a new economy. How do we... A lot of people ask us, and I'm talking to a lot of open source advocates, how do we instill a culture of inclusion and accessibility, which is what we do with the accessibility lab. I mean, this is our primary audience where we look at engaging with different stakeholders. It could be UI, UX designers, developers, customer service teams, marketers, directors, and many, many others. How do we do it? We do awareness trainings, we do accessibility assessments, whether it's audits, direct implementations, testing and monitoring, and we actually follow the web accessibility, content accessibility guidelines mentioned by the Web 3 consortium. We're currently at version 2.1, 2.2 releases in May, but we're also saying that we're not doing anything new. It's always been there. We're just implementing. You can reach out to me. We do have... We offer pro bono services for open source tool teams who anyone who has or has been working on enhancing security in privacy. So please reach out to us if you are running an open source project irrespective of the geographical background. We're happy to help you and make your tool and product more accessible. Thank you so much. Thank you everyone for your attention. Any questions, quick questions for Rashi? If you want, you can also come and look for her after this session. Right? Yeah, for sure. Yeah, so for right now, can I request everyone to make their way up to the lecture theatre, please? Because we will be preparing for the group photo. How was that? Strange step. I thought you were going without slides and then it turns out you were fixing it. Can I leave this here? Okay, one more... I need help with the stream yard. With the newspaper garden. No, no, where? Hey, out here. Can I help you? Can I help you? Can I help you? Can I help you? Can I help you? Can I help you? Can I help you? Can I help you? So I'd like everyone, if you are interested, I would like you to gather to our stage here and we're going to listen to Palm from Thailand. And he's going to talk about building open source to make Bangkok suckless, which is very interesting. So everyone, please come here quickly. Yes, everyone. I'd like to support our friend here from Thailand. That would be great. Okay, our talk will start in like one minute. And I'm from Bangkok, Thailand. So today I want to talk about how we are engaging a thousand developers in Thailand to make open source to make Bangkok suckless. So let me introduce quickly first. So my name is Palm and I'm an indie hacker from Bangkok, Thailand. So I'm originally from the southern of Thailand, which is Songkwa. I'm also co-founder of Creator's Garden. Before this, I was VP of engineering at a building. But all of the time it all created and there's a lot of experience. But there's a lot of students. So there's a lot of questions that one of them is what's called tradition. No one thinks that verbal ideas happen. So it was the one thing when where everyone came up with basically anything that is stupid. So this is how it's done. It turns out people really enjoyed it. And we have been here for six years. Great. So this has been our sixth year now and the seventh one is going to be organized soon. So we have been building that since 2017. And we have gotten over 900 developers over the years. And they have built so many projects. So let me show you a couple from our students. First, how do you build a bug-free code? Maybe you use a language model, right? To correct the code. But we have a better solution. You just put like the dead insignia and now your code is perfect. So we have a common solution near like Songkran in Thailand. Yeah. In Thailand we call this germ which is giving your server a boost. It's better than your firewall. Now, how do you improve friendliness of websites? Thai websites are known for being very hard to use and not flashy. So we build a Chrome extension to make it so much better. So you can randomize from the color palette you want. And this is not epilepsy-friendly. And this is the best one. How can animals code? If you're a seal, you don't have hands. You only have your voice. How do you code? You see, you do a programming language for them. So this is a programming language that our friend built called Unlang. Un is the sound of seals. So it uses just five full characters but it's fully tiering complete. You can build any application with this and it compiles to C. Okay, another one. Can you be more productive when you have a lot of windows? You use a window manager, right? No, we do a trolling window manager. So if you use keyboard, you're fine. If you use a mouse, you are screwed. So it tries to move the window if you move your mouse. Okay, and this one. Right now we're moving towards the age of quantum, right? So how do you supersede Morse law? Which is the law that indicates that it's smaller, it's basically harder to jam more stuff on the ships. Well, you enslave the entirety of human and then you make them run assembly. So every assembly instruction is basically just doing arithmetic, right? So technically you can write a program that transcribes your assembly code and send it to a human to answer because we have 7 billion people in the world. You can basically multi-trade better than SIMD. Yeah, so this is obviously very, very stupid. There's a couple more. So like obviously a rig roll. Oh, this one is cool. So basically if you have a logo, but your clients say it sucks, the logo doesn't look like it's properly thought out. We use OpenCV to random redraw circles. So it looks like it's properly designed. Yes. So yeah, the projects itself is obviously extremely silly, but the technology behind us, we use OpenCV, we use AI, we use machine learning. So people got to learn from this obviously stupid things. Yeah, so if you're interested in at 100 projects just scan this code and you can see a lot more gems for yourself. All right. All right, so Thai people, they are very creative as you can see, but there's a weird thing where I saw few developers and there's only three people. There's me, there's Michelle Rhee, and there's one more. So like what happened? We have like so 900 developers building Open Source, but they're not getting outside of Thailand. They're not building anything useful. Here, look at commits at top. You can see that people, the first 10 ones are my friends, so ignore that. But basically other people, they're not engaged with Open Source as much. That's a total question. What motivates you to build Open Source? This was me when I was 14 years old, I think. So I got in love with Linux because my Windows like Windows file system broke down all my files is gone. So I cry for over a day until I remember I had Linux. So every proprietary system didn't work, but basically I downloaded the source code for NTFS and I programmed it to remove all the error and suddenly all my files are back. So I fell in love with Open Source because I can modify the Linux driver, the Linux kernel, and I can make anything possible. If you use Linux, you can have this really totally fancy Windows. There's the KDE booth if you're interested. Another motivation is what you like. So my friends, they like a certain kind of Japanese cartoon. I'm not going to say what kind it is, but basically he's really into that so that he built a whole tech stack around it and it only takes less than a dollar to serve a thousand people. And here's even worse or even better because he was building this cartoon website and he think it's not fast enough. So he wrote his own the framework in bun and now is the fastest. So there's a lot of motivation that can make people do Open Source or when you see a lot of bad syntax and you want to make it better, you make it Open Source. Now unfortunately in Thailand there are a lot of hostility towards Open Source and that was part of our culture in the beginning because we were afraid of people taking our IP, afraid of family foreigners taking our land. So that kind of fear was kind of ingrained but as the newer generations grow they want to change that they want to try to make things more open and more shared. So what motivates you? I would say it's really two things. First you fix the shortcomings of your software. You're using a library but you see hey the software is not really doing what I like. So I fork it, I write a plugin. Another thing is you get to learn so quickly because if you do Open Source you get to learn from really good people you get people like trying to teach you by comments. Now, what do Thais want to fix? This is like the big question if I can't answer this I can't get as many Thai people to join me. So let's talk the elephant in the room, shall we? Okay, what do you think of when you think of Thai culture? You might think of Khao San, all the clubs. You might think of beaches. You might think of temples and Pad Thai but if you take the red pill well it looks a little different for us in Thailand. This is the first time in Bangkok. When you wake up this is what you see. So yesterday it was 152 HUI for us in Bangkok. So basically if you forgot to wear your PM mask well you're going to have to go to the clinic. Many people are feeling their eyes burn. Dryest feet in Bangkok. We have really bad water management problems and here's the light test traffic in Bangkok. I'm not joking. So there are so many cars and it's very hard to travel and this is a cleanest street post. Some people say it's kind of like an installation art in Thailand but well trust me it makes it really hard to travel. So everyone knows that Bangkok has a problem and all of us want to fix it. So we can do open source tooling with data science to make it better. So this is where we assemble people like the Avengers and I want to tell you one thing right now even the topic of the top is Bangkok open source hackathon but hackathon itself is a lie it's not really a hackathon. So it's all started when the type of grammar association they asked me hey can you build a hackathon with the ideas from hack BKK and make it happen. So I thought what the heck is hack BKK so turns out it's an idea of fun you know that kind of hackathon where you don't actually get to code and who are actually like brainstorming ideas. What do you think it is? Well it went exactly as you mentioned the ideas remain ideas most of them and the startups that say they want to take that idea some of them can but it's a proprietary solution. So I actually met this guy this handsome guy he's the newest governor in Thailand he's like Thai people call him Mr. Strong so he's such a so we talked to him about open source in Thailand and this is what he told me and it kind of struck so he told me he wants to see the software being maintained and adopted keeping developers they should spend more time with the communities they're working to also data like he wouldn't like to see projects be abandoned so this is really the heart of open source if it's an idea in a hackathon and it dies no one can use it but if it's open source everyone can fork it they can use it so here's another red pill as much as I like organizing hackathons I have done like over 20 of them but the problem is it's not really the answer to this problem neither is proprietary startups because for hackathons they're really perfect for like ideation getting people to learn right that's its own goal but it's not really for being something that sustains another thing is called big startups in Thailand there are hits but no one's making it open source they're not sharing their code but we are the one that's paying the taxes so there's a saying public money public code now what's the solution let me tell you one project we have been doing in Thailand so we had the election several years ago so we have this really fancy dashboard but the thing is this dashboard was built in less than 8 days so how do we do it it has so many features it has so many things well we make it open source so in this project in the span of 8 days we have over 30 contractors and people are in over 90 PRs now because Thai people are so like they're really passionate about elections because of our current situation so you can see why there's an influx of Thai people opening PRs oh and by the way if you're interested we have a goal mind of how we use several open source techniques like password driven developments and other methods to make open source really easy so we were actually inspired by hack for public good if there's anyone from GovTech here thank you I just copy your idea so we took the inspiration from hack for public good from Singapore and we came to a conclusion don't stop at prototypes but build open source so how do you do that this is where we try to come up with the idea of Bangkok open source where it's not really hackathon it's just a lie it's actually a two month program where we build two workshops plus three hack days so it takes a lot more effort than your normal hackathon but the results were really worth it so we break it up into four sessions two workshops one open hack day where everyone in Bangkok can join and a final hackathon so this was the first workshop so we first started with getting people to know each other and here's a couple of co-talks from that event when we think of open source we think of software but this guy he tried to be an open source community where everyone from multiple can adopt that idea and as you can see most meetups are whole like in a conference hall like this where it's really nice and fairly but we actually held it in the middle of making their own food and producing drinks so it turns out it's a really nice way to bring communities together okay let's do one better how about an open source house so most of the house plan in our world are closed source but if you're trying to build better communities you've got to make it open source so this is why the team from Muse Foundation they try to build a whole village where every house is open source and everything has a CAD model where you can do printing you can do the very precise operations another talk is about a system in Thailand called Trafi Fung Diu so I'm not sure if Singaporeans have something similar but if you see something wrong like there's a flood or there's the lights doesn't work you can report it and it flows into a database the nice thing is that there's an open source there's an API so we took some data analysis so we can know what problem we can focus on another talk is about CWIC tech so in Thailand we do a lot of data storytelling and data visualization because people have difficult time understanding data so that's why we use data a lot in CWIC tech so you can look at the YouTube channel if you want to see these kind of videos let's look at workshop 2 at workshop 2 we try to get people to brainstorm ideas and actually try to come up with prototypes so we have speakers from the domain site and I think this is very important many hackathons they only have hackers, developers like us but they don't have people from government from the citizens from community that actually knows that but of course we also have people who are good at tech so it's very important to analyze into how to structure the rate post so a big part of our success was the Bangkok open source discord because even if the hackathon is really five days but it's actually two months so most of the teams they were actually on discord night and day this team called WeSpace the funny thing is the hackathon has been long over but there are no signs of stopping so this team they just like done another satellite programming the community is getting up very fast and there's already 825 people in the discord now when it's the hackathon many times there's clear competition you have to get first place second place but we scrap all of that because in open source there can't be an internal competition you have to cooperate so the goal is you can join any team you can leave any time and there's no first to third place you can come up with something a little different we also did an open hack day so this is not only limited to people who are in the hackathon but let's say if you're someone who's for example we got a guy who was an abarist so an abarist is someone who work with trees so he comes into the project and he tells the guy like how like tree management works and it turns out to be really good because people can come together and work and fast forward to the hackathon day so in most hackathons like the hackathon vibe is very stressful right you don't really get to sleep and everything is tense but because they have been working on it for already two months it's not really stressful because like it's mostly finishing up the project and trying to make sure everything's polished so we have three judges from different sites so we have someone from seaweed tech and someone from tech and from the industrial site now this is the fun part the award because usually we have first to third place but I think that is very anti open source so we actually make three kinds of awards, contributability which is how easy it is to open a PR or contribute something concept which is how like how good the concept is and implementation which is how good the software works it can't be a prototype it has to work so there is eight group as you can see here and I'll quickly go over them so here's a question not a stupid one like how do you know which party to work for when you have so many political parties and all policies look similar you use AI and you use natural language so there are like I think the students are 13 to 15 year olds so they're assuming they're like middle school high school but the really cool thing is they wrote on like text clustering algorithm to try to cluster the policy how do you know where to buy land there's so many things you have to think of in buying land but they actually wrote a software that would incorporate multiple data source for example is it near the airport how much are the income of the citizen near there is it near the sea so they can make better decisions for business and for buying the land and again these students there are 15 to 18 years old but they're already building stuff for people of Bangkok which is really cool and as you can see here it's not mock data it's actually life another this is the fun one how do you make money while making lives better well you report people who doesn't follow the law and get money so so there are people who like park their motorbikes in like the walkways and in Bangkok you see this every day and you you're really angry at them like why do you park there you cannot walk so they have a channel where you can actually submit this photo and get money but we're like wait we have AI we can use the YOLO model to basically do like segmentation and we know like whoa this is the bike we can report them to the police and so we did that so they take the data from all the CCTV and auto report to the police and you can probably make like a hundred thousand bucks from just doing that so yeah this is how you get rich from open source and how do you know changes are actually being made because like so many things are happening in Bangkok so my friends he wrote a twitter board that aggregate the data from traffic which is the system for reporting problem and he posts a summary every day on twitter before and after and this is really nice because people can actually criticize the government with data so they can reply on the tweet hey why is my light pole not being fixed that's not good oh what about building tools so this woman she is a bonus so she's trying to be a tool to break all the silos in Thailand because in Thailand you need 10 signatures to do anything so she wrote a tool for everyone to connect peer sharing is a nice one so this is a software where people used to do peer sharing in chat groups and they're basically losing a lot of money because of people are cheating so they write a system so that it's impossible to cheat anymore okay we have three more minutes so let's talk about the award winners so this one is the concept award winner which is called Rasa Kicha Rasa Kicha is government cassette so basically is the like the messages from the government but right now in Thailand it's all in GTF and it's not properly digitized yeah so so they try to digitize this together and the next one is free space so this is the best one they try to digitize all the trees in Bangkok because right now they are actually paying the government a lot I lost that slide but basically right now they are paying 180,000 baht in order to digitize 40,000 trees so you can see we're wasting 100,000 maybe 1,000,000 baht of money paying for proprietary software and it would take them 300 years to digitize all the trees in Bangkok and I'll be dead long before that so the nice thing is they use data from street view and aerial view they use a lot of AI like deforestation and tree detection also segmentation and they submit all that data to open street map so you can see this is how like people are actually contributing with open source and there are like people who are not only developers but others who are working on that and you can see we get so many requests over 110 comments and we also get so many contributors so a quick special thanks to Konmichae Lee here from OpenTech because he has been helping us so much with like providing ideas for the hackathon and also thank you for everyone who sponsored so quickly what we learned to get people to like collaborate to open source you must get them motivated so this might be building something silly next is keeping the momentum how do you keep people engaged and finally to facilitate the adoption because an open source software that no one uses isn't really open source so you need someone to you need to get them adopted by people and finally this is the second governor of Bangkok so he was taking the photo for us so it's not only students building but also the governor of Bangkok so the next step is we're keeping up that momentum so we're building a next hackathon for the upcoming election where we can catch if the hackathon sorry the election is being done transparently and that's it for me thank you do you have any questions for Paul anyone where are you finding the participants from like how are they so here we have Tad so he's actually the founder of Kaiyuan Shoot China so today he's going to talk about building an open source ecosystem to win a digital future together so please welcome Tad everyone everyone so let me do a quick chat so who has attended yesterday's or purchase of a foundation presentation that Rich Bowen and Roland Jones presentation raise your hand no the speaker doesn't count okay thank you so much and is it good for you okay actually I have more so welcome to this session I'm starting counting the time it's quite busy I'm Tad Liu so briefly introduce myself I currently wearing three hats the first hat is Kaiyuan Shoot co-founder Kaiyuan Shoot is a ground up open source alliance in China founded in 2014 so we call ourselves a home of open source and we call it a community of communities of open source most of you are purchase of a foundation so my third hat is the open source wind forest advisor so I have three hats so you can see the Patrick's picture up there previously I was with a few companies and start up I was in a multinational company so you can see the green one that the green means open source so the green one already was open source the low one actually is EO2000 with the kambaba bursts I was with one of the top three ladies distribution in the world but they never went listed so it's a start up failure and it's a good lesson to me so I started to embrace the open source system so my I call three body experiences one is in Taiwan born and grew up in Taiwan in US and in China for 23 years so I call it three body experiences so who have the book oh okay you did? three body problem have you read the book? okay there's a tried connection for your power so that's some of your three problems for different devices anyhow the last book says death and but I don't believe that I believe that Penguin gonna conquer the world when we're off in peace and open source can conquer the world anyway so everybody can reach out to me through this content method okay today I talked about open source market dynamics and the developer building globally in China so we can see that open source is increasingly growing anywhere even in China in my opinion the open source acquisition and adoption in the enterprise is larger than the proprietary one that you can see the stats here then the proprietary software and the OSS commercial and the OSS communities software and it also happens in China the same way also we can see the OSS adoption in the industry in many industries like financial, energy entertainment industry like academy software foundation sorry it's wrong academy software foundation developer why not the fastest building working in the world currently the company annual growth rate is 19% so why not the fastest still working in the world now but the share is that we have many projects from my experience that in 2015 when we started and sure we do the first in China there was only one project it's a top-level project and nowadays today we have 34 34 projects and 23 of them have been graduated as a top-level project 11 is still incubating so but however the purpose model is yet to be approved and the people are still the investors the venture capitalists they're eager to invest in open source project but then you can see that last week in Hong Kong there's a web 3 conferences so the web table there's 9 investors only one project that's a very pleasant experience now investors approach you open source project is very popular but there are few investors they look into the project so the successful model is yet to be approved yet we know that in China's enterprise and startup open source enterprises they are going through these stages consumer stage participant stage contribution stage and leader stage but I would say that most of the Chinese enterprise even with top 500 enterprises are still in a very early stage and most of them are still in the early stage and the problem is that the capability gap including the compliance and governance capability and the the capability participating in the open source community that was led by the reason we signed this agreement with open source a few a few reasons one is Rich Bowling mentioned yesterday free as a free puppy they think it's free but actually the rest of the dog a puppy dog is not really free you need to spend a lot of time to take care of the puppy and the compliance many enterprises they can understand that how to use that open source software correctly that creates technology gaps and the security issues so the compliance is one major issue here the selection and they don't know how to select a robust well built and sustainable project that also creates an issue that also they don't know how to choose their open source project business model going forward so it's been challenged by the corporate leaders and how the open source project business model can be profitable and sustainable and that's what next one is the companies and a lot of developers in China they don't really understand how to grow their community or join and participate in the community here right so open source when closed it's probably one of very few communities that focus on being the enterprise open source to a better place so they position themselves as a partner of choice and ok my time has shows 6.15 6.15 seconds so I have my timer, thank you so our vision is guiding enterprise growth with open source so our mission is to building open source knowledge and work in other parts of the world but in China there is a phenomenon is that either the biggest enterprise they lead open source project or they start up what's missing is the small and medium enterprise they don't have resource they don't have knowledge but the top enterprise mostly led by open source project mostly from ICT communication telecom and other traditional industry they still try to figure out how to do the open source that represent a huge opportunity here so that's our approach that we work with the industry customer we have to understand open source how to use open source and contribute to open source to become a leader for leadership right so remember open source empowerment program currently we are out 11 9 courses out of 11 so from 4 to 1 category understand open source and its best practices open source compliance supply chain management that's the very proposition that echo is what we said yesterday enterprise opens strategy model two more courses it's under development so this is the history then joining that how we prepared and published these courses back in last year published almost this time in August then we published two more courses I was one of the speaker here alright and actually first Asia summit is the first one that we launched this announced that final courses and so I supposed to announce it back in China but that's bad first Asia summit final courses will be launched and then remember there's two more courses the last two courses that focus on open source usage and ecosystem building they will take a different approach then we talk to people who has real practice and real experience how to do open source governments and how to do open source project so like ZTE then telecom one of the 10 times equipment provider in China like any group one of the largest internet energy group in China and also we talked with the one community health measurement project called open source compass that help enterprise open source project to evaluate whether this project is robust enough whether it is sustainable alright ok, then now to come we will interview with talk to pipelines really foundation OSPO group giving global rebank so on and so forth so that we put all this side chat together and make a more interactive conversation and accumulate experiences and best practices together for these two courses right open source usage and open source ecosystem building they will learn from their experience alright actually we will have we will have 45 seconds anyone who has more questions I have a souvenir that I can give if none then I'm done here thank you for your listening thank you