 I'm so excited to talk about my experience for Oasis World here. In this session, I would like to show my experience to help you to find a way to contribute to Oasis World as your way. Let me introduce myself first. I'm Kazuhaki Matsuo from Japan. Please call me Kazu. My social media accounts are almost Kazukokoa. The code is come from the iOS framework. I work in Haspin as a senior software engineer, devised automation. I also heavily commit to contribute to Appian project. It takes almost five years after my first commitment to the GitHub repositories. Nowadays, I work as a senior software engineer, but previously, I worked as a test or a quality engineer. So maybe my experience is actually recently worked for a software engineer, but my best experience is, I believe, almost close to you. And today's topic is here. I want to talk about my experience, how to start contributing to Oasis project. First, and I hope you find an example to contribute to Oasis, especially Appian. Now, second topic is about the Oasis community. In here, I want to show the community roughly and where you are. This should be interesting if you want to find a good opportunity to contribute to Appian project. So, in the end, I hope you will get an insight or motivation to work for Oasis communities. If you can find such good points for Appian project, my talk should be a very good success. Let's start. The first topic is my experience in Westworld. Listener, I'd like to show my career, and my career starts as a software engineer. I experienced a couple of years for automation, testing stuff, a managed project or a product. I also did software testing as well. In work, I definitely used Oasis tools, but I was just a user. I was not so aggressively to commit Oasis project. So, my mind was just a user. I know GitHub activity is not the only thing to indicate my Oasis activities, but let me show my GitHub to show my change. The first commitment was to practice mobile automation stuff using Appian. This is just for me. I think this is a very common thing when you learn new things or investigate something and try to use something, and you change some code, writing a code, and push their GitHub to remain some of your activities. But this is just for me. But after 2014, the number of commitments increased. The target was not only for Appian, but also other Oasis projects. Why I changed so? The first thing was previous companies culture. I joined Cookpart as my second career as a test or quality engineer. Since I wanted to express software testing and software quality more, I worked like an Azure testers such as automation, manual testing, improving software development processes, and more other quality-related activities there to build such quality culture in the company. Then I got a responsibility for mobile application with Appian. So I bet through Appian for mobile automation for both Android and iOS because I was only one test engineer in there, so I must cover Android and iOS by only me. The decision was my first reason why I got interested in Appian. The most significant impact for me to contribute to the Oasis commitment was the company encouraged the employees to contribute to Oasis. The Cookpart heavily used Ruby. Ruby is the programming language. The Ruby is an Oasis product, and Cookpart had committed to the language itself as a company. The company's performance review had a commitment to Oasis project product as an engineer. Thus, I started contributing to Oasis project steadily. The number of commitments had increased after joining the Cookpart, and surprisingly, I noticed that my first commitment to the Appian project was 2014. I just searched when I created this talk. It was almost five years ago, very surprised. I can remember the first issue even now, since the commitment was my first time to known individual Oasis project. I was very nervous then, so I tested very carefully even it was a very, very small fix. The motivation was I wanted to fix the issue as a user. I fixed the issue when I run tests on my environment. One good thing for Oasis product is we can fix it if we find some issues in the repositories. This is a very good thing. This commit is much very quickly. The process was definitely easier than expected. The experience was my first commitment to Appian repositories. That was really amazing. After a while, I continued to work for Appian project and other Oasis project as well. GitHub activity also became being grown. In 2017, I finally became a technical committer in Appian project. The green color does not contain the private repositories ever since public one. This is just a public one and nowadays the activity is kind of became my routine work. And finally, I moved to Head Spin to current job to focus on evolving mobile performance automation environment and grow the environment further. The commitment for Appian project is continuing. I talked about my first commit and that was very small. But after the commit, I felt my commitment was very not so difficult. So the commitment itself is not so hard if you down once. And for a while, I fix some issues which I faced when I use Appian in my project. I use Ruby client mainly since as I showed you, Ruby was a primary language in the cook path. Almost engineer were able to implement Ruby code and we had many helpful Ruby related libraries internally. We could use them to make handling test easy. After a while, unfortunately, the Ruby Appian binding changed to the status as a call for maintainers. And then I decided to work for Ruby as a primary main Ruby binding as a primary maintainer. The motivation was easy. I use it very heavily in the company work. After that, I changed something, for example, adapting the W3C spec support in Ruby binding and separate some complicated features into core part and the decorated part. And I also worked with Selenium guys. For example, Selenium guys have their project called Waiter. And we collaborated with code name top Waiter, which is our Waiter for mobile. I also started to commit to Appian server side as well as client side, developing Appian further. I have sold experience for Android and iOS. So my experience on my work also very helpful to me to enhance the Appian and the commitment. So nowadays, I currently commit to the client, not only Ruby, but also Python and sometimes .NET. I'm not familiar with .NET, so we need maintainers for .NET, by the way. And server side as well. And currently I'm working at Hatspin, but not full time Appian committer, just a part time. And my commitment to the Appian project become routine work in my private time as well. I talked about my experience, how to leverage my commitment in OSS project, especially Appian case. My first step was find a small issue and fix that issue. And after that, I could leverage their commitment to the more widely. If you are not familiar with OSS world, I think maybe your commitment, you are trying to commit, then you feel very scared, because some negative review or something will get. But once you can work for it, I believe your feel become better. And then you will get more opportunities to make your experience deep for OSS world. And maybe you can find more experience in the software world. From now, I want to show the OSS communities. I talked about my experience, but the only important thing in my talking about my experience was, you will find an example in the OSS world activities. My experience was mainly committed to the code base. I heard similar questions by many people, such as friends and colleagues. Exactly the commitment to the code base is very important to evolve the product and project. But this is not the only way to evolve communities. Let me decorate a graph. This green color is a kind of feature and documentation stuff, so it shows the core members develop and fix some issues. We also investigate some course and issues and fix them or write a documentation, how some features work or some practices. It includes not only Appian developers, but also implementing Appian binding libraries or other related libraries. But time is limited. No one can work everything. And around the development members, we need the blue color is kind of supporters in the community. For example, this means they guide some beginners or answer against the questions in somewhere. And hopefully there are some users who get answered by the supporters or developers. Then the guy will be the next supporters for the other guys. This cycle is very important in the OSS communities. Of course, the most people is just a user. So the yellow color is just a user. And in the community, there is a user just asking and maybe mainly using. But not to feedback to their core team or supporters, but they are supported by blue colors one. But the important thing is they are not hierarchy. They are very flat and the difference is just a role. So we should support each other to evolve the communities. This is the OSS world. Nowadays, Appian is one of the just foundation members. So the tools have been developed by committee base. So we need more power by committee. For interesting, in Japan, we have a local committee for people living in Japan. Nozomi, who will be one of the speaker tomorrow, is a leader and I sometimes help Appian users in these communities. This activity is kind of blue or green color in the previous page. And if you are interested in commit, from now I will talk about some projects in Appian If you are interested in trying to create new issues in Appian or try to help Appian project at the first place, we started one localization project. On Appian desktop, we already provide maybe three or four, five, six languages. They are translated in this project. No one can speak all natural languages in the world. So this project is very important by help you because I'm really not sure the Indian languages, of course. So many people, for example, in Japan, also almost 100% finished into translating in Japanese and Chinese also in some place are very active to translating from English to their languages. And this is very easy thing to commit to the project. And documentation also very important but very easy to commit. The commitment to documentation is, I know, actually need a kind of special skills because documentation should be help understanding the project product. For developer, sometimes we describe technically and very deeply. It sometimes make understanding difficult for beginner or for some users. So hopefully as a user improving documentation and creating a PR is a very appreciate. Improving documentation for users as a user is very important to support users as a one of the committee. We also have a forum. Maybe if you, I hope someone already used this or noticed. If you have any questions or something you want to get answered, this may be not a bug. Then you can post your questions in this forum. Then someone apply for your question. And in our project, we have a level, good first issue, and help wanted. For example, in Python case, we have this kind of good first issue. And if you are interesting in committing the code base, then this, and if you know Python and you can implement some easy script for Python, then this there should be very good for first place. For example, yesterday I did a workshop to become a committer, find a bug. Then only maybe seven hours in that, we already got our two PRs. And they are very small and very easy. But there is another PR already done, similar thing. So very easy to create a PR and commit to the code base. We also have some levels in there. This is a few main repository. There is an enhancement or good first issue. And in some issue is just an improving error message. This change also happened yesterday. Very small, just a log debug message. But this is also a very good first issue to contribute to our code base. This is our final page. I talked about my experience and start contribute to OSS world from small change and leverage to the more repositories. And my activities for OSS became the routine work. And I also told you the OSS committee needs more help, your work. For example, commit to the documentation, question and answer. Or if you are interested in the commit to the code base, then fixing issue or a new feature or something is also very good place. Hopefully, some of listeners get our motivation to or interesting in contributing a hope free app in project or OSS project around you. Thank you very much.