 Hi, I'm Yun Chen from GovZero Community. GovZero Community is an open-source SIFTAC community from Taiwan and very kind of decentralized SIFT spirit. And one of its projects is called this factory. It's a platform to help citizens to map and report illegal factories on farm lands in Taiwan. And I'm the private manager of this factory as an open-source contributor and I want to introduce how we collaborate in this talk. So first, the idea of this factory was very simple. The civil society organization who raised this idea called Citizens of Earth Taiwan, they want something very simple that you can just take a photo and you can mark location and then the data can be automatically printed out as the official documents sent to the government so they can do their campaign and advocacy. So for the past year, we got some results. Eight factories were demolished and others are still in process. And that's, oh, I want to share with you about what is this factory about because today I want to focus more on how we did it. When I say we, it's a very loose open-source community, GovZero, and a CSR with a gena to push. That is Citizens of Earth Taiwan. So it's actually about how to herd the cats, product management, and open collaborations in civic tech projects. So the story begins like that. The CSR came to the GovZero hackathon. They have an idea, really brilliant idea, and they wish they can find some wizards to help themselves everything or magically build something. However, they might be a little bit disappointed because they actually met a color of cats. They are very good at what they are doing, but they are very independent. They only do things they are interested in. Once they lose their interest, they just leave. So how can this happen? How we make something deliver on time and impactful? As a product manager of this project, I want to share my experience on this in four factors. The first one I want to introduce is the goals. It's very important to set up our goals in open source projects like this because we have more than 40 contributors across five time zones. We have 10 weekly active developers and people are floating in, floating out in the project. So you really need the goals, the North Star, to let everybody on the same page to see, okay, that's where we are going. And we see what we can do to get there. So even a lone wolf can collaborate and help us to go to that destination. And for me personally, other than the digital product, one of my goals is also the empowerment of severe society organization and open source communities. Okay, now we have the goals, but how do we get there? We cannot just jump to the moon, right? So the next step of the product development is so important to keep it agile. And within the agile process, I think scoping is the most important part because we have very limited human resources. So we cannot afford doing something nice to have. So this is the diagram that is focused on what the simple structure or the core features we need to deliver. So then we can break it down into different models and develop the first models first and then later to develop other parts. So that's what we are doing. We have the math of reporting and then we have dashboard and then we are not even making online interactive games for the netizens to spot the difference, help us to mark the new factories. So the first two are very traditional product management stuff. And the third one I want to talk, it's about open by default. I think that's the only way that you can make this kind of lose and open collaboration happen because we open our every meeting memos online and of course our source code design and everything. So it's accessible for everyone who want to join the project. We also have online workspace. Everybody can join a discussion. So if you are newcomer, you can just pick up a small tax and then if you like working with us, you can take us larger tax to do a longer run. That's why we break down the tickets and also the milestones things also help people who want to leave the project know that their products can be living good hands. So the last one is actually the most important one and the most interesting one. The NCSO staff always ask why you guys want to contribute your free time to this project without pay. And the developers answer is because it's fun, it's open source and it's for social good. Fun is the first priority. And fun here not only means that we have really good snacks and drinks in the middle, but it means that they can try new technology, they can explore their professions, they can do what they couldn't do in their day-hand job, enjoy the freedom and turn me to contribute to your project. And as for the CSO, I'm very glad that they know that this technology is not just building a website. It's a new culture, it's a new way of collaboration. I was so happy that it told me they started to use online share drive for internal communication. So to wrap up this talk, there are four takeaways. First, open by default. If you want to build something for civic participation, then your project itself should be civic participation. Second, keep it fun. That's how you build a motivated team. The third, always keep an eye on your goals because you are here to fix the society, not just the website. Last but not least is the agile. Please, please, please always testing what user need before you started to build something huge. That's a hard lesson I learned from my last failure. And today I'm very happy to share my experience and I want this can bring up more discussion about product management and open collaboration in Civic Tech because that's how we can build the Civic Tech that really is of the people, by the people, for the people. Thank you very much.