The only way to make the Narcissist respect you, there is only one way to make the Narcissist respect you, there is only one way to make the Narcissist have a high opinion of you, when the Narcissist first met you, they didn't admire or respect you, although they made it seem as though they did, they admired your abilities, qualities or achievements, but they had no respect for you, and that is why it was so easy for them to come into your life to trick and deceive you, it was so easy for them to take advantage of you, without any feelings of remorse or regret, without feeling as though they had done something wrong, and when you couldn't meet their impossibly high expectations, they then began to devalue the very things that first attracted them to you, your abilities, qualities or achievements, because the truth is that nothing and no one could ever satisfy the Narcissist, they will always be dissatisfied, and while it may seem as though they respected you in the beginning, it was actually just an illusion, they admired what you had to offer, but they didn't treat it with any respect, they only love bombed you to secure you as a source of supply, so that they could then use you for their own needs, the Narcissist never admired or respected you as a person, they never valued or appreciated you, and as they began to realize that once again they could not feel satisfied with who they are with, they began to devalue you, they chose to project their feelings of low self-worth onto you, because it's either you or them, and nothing is worse for them than having to accept that they are at fault or that they are the problem, they have to disrespect you in order to sustain their false sense of respect for themselves, there is only one way to make the Narcissist respect you, there is only one way to make the Narcissist have a high opinion of you, and it all starts by respecting yourself, if you respect yourself, other people will begin to respect you, if you value yourself, other people will begin to value you, and you may feel as though you do value and respect yourself, but if that's really true, why are you still involved with the Narcissist, why are you still involved with someone who does not value and respect you, if you really valued and respected yourself, you would not be involved with someone who does not value and respect who you are, practice that act of self-respect, practice that act of having pride and confidence in yourself, the only way that the Narcissist will value you, the only way that they will ever respect you, is if you no longer tolerate their disrespect, without self-respect you are susceptible to being used, abused and mistreated by the Narcissist, you believe that you deserve to be treated that way, you stick around hoping that they're going to change, but that's not going to happen, the Narcissist is never going to respect who you are as a person, because they do not respect themselves, but if you decide to respect yourself and move on, they will be forced to respect your decision, the decision of no longer being accepting or tolerant of the abuse, that is the only decision you make that they will ever respect, and while they may never accept the reasons why you have chosen to move on, they will be forced to accept that you believe you deserve better, and you do deserve better, no one is deserving of abuse, everyone deserves to be treated with respect, and if you are a person who respects yourself, you will always have respect for the people around you, the only way to make the Narcissist respect you, the only way to make the Narcissist have a high opinion of you, is to no longer accept how they are treating you, to no longer stick around and let them continue their disrespect towards you, you have to move on, that is the only way that you can respect yourself in that situation, and that is the only way that the Narcissist will ever respect you, thank you for watching, I hope this video resonated with you, please like, comment, share and subscribe, click the bell icon to receive notifications for my future videos, if you would like to donate, my paypal link is in the video description, quote and inquire as you can email me at narcovercoaching at humor.com thank you for watching and i'll talk to you soon


What's going on everyone? Sam here with LaytonSportsGuard, dripping 22, peening Donnerous Optic Football Retail 6 box break, number 3, random team style. So looking at it, your random results, Zoe's, you can find those on the website, under the results tab, as well as the link in chat. Here we go, good luck. One thing I will give about the Donnerous Retail is very easy to open. Yeah. Packed our fly through packs. That sounds good. I'm going to be like Sam. Stars is Charles Woodson. I think so. That's what you look like when you're using your Swiffer. There's Keanu Tei Ingram. You know what you look like when I see you?  Yeah, is that true? Yeah, that's what you look like. I will not look like that. This is Kevin Harris. Buem Afe Stars, the Seahawks, Damian Pierce Rookie, Texans. That is Terian Devs Price. Manus. Bleah Stars is Cleel Mac. Will, do you know I was the first experimental AI? Rashad White. I would believe it. I would believe it. Nice. Bleah Stars, Sam Howell. Nice one there for the commanders. There's a Picket Rookie. The Rookie's County Picket. Kenny. Whoa, Kenny. Elite Series, Jamele. Jamele Drafkins. Hello, Jermaine Johnson. That is something going on on that one. Gonna send an empty box and wrapper with the Jets and a Johan Dotson Rookie. Ooh. Jimmy the Intern was trying to put together a science project. Got the glue on that. Come on, Jimmy. Jimmy together. Hello, Damian Harris and a Cam Taylor Brick Rookie. Kurt Warner, Retro Series. My house is Jobar. Souths Gardener. I don't know, Eric, to be honest. My guess would be after the national. I know we're going to buy a bunch of stuff. There's Tony Romo. Okay, baby, be calling me Hercules. There's Fadarian Mathis. Sounds like a song or a tick-tock. It is a song. Rashad Bateman on The Blue Stars. No, there'll be a national promo this year, Dean. Oh, yeah. We'll have national promo for sure. Yeah, my guess would be the Almanac will come back post-national because we're going there to buy. I know Blaine's going there to buy a ton. Blaine and Rich, I should say. The babysitting Sean the entire time. Yeah, the promo is going to be sweet. Tyler M with a T-Mall spot. We're down to 11 to go on T-Mall, everybody. 11 to go on Optic T-Mall. Nope, that's the wrong one. Optic T-Mall, number six. Actually, we're down to 10 to go. 10 to go. Almost into the single-digiteronies, everybody. We are almost there. Blue Stars. Nick Bolton, Almanac after the Natty, yeah. Really, Force of the Ronies. Nah, I never forced the Ronies. Michael Parsons. Kenneth Walker, K9 rookie. Blue Stars, Fletcher Cox. Sam Howell rookie. Forest 27th, I think is the first day. It's not this coming week, it's the week after. It's 11 days away now, I think. Joe Namath, Foot Fungus stuck in my head. Yeah, that's the song. Boya Mafe. That is Martin Emerson rookie. 26th to the 30th, thank you, Forrest. Matt Corral, yeah, 26th is like the Wednesday. It's like the VIP night. There's Kyler Gordon. A War and Moon Retro Series. Yeah, go harass Forrest for everybody, Dean. That'd be fun. Alec Pierce. I'm gonna tell people to just go and physically harm Forrest. Trent McDuffie. Wow. All right, then. Here's Sean Junior. Jake Ferguson. I got progressively louder. Did not like it at all. James Cook. Experience, 1 out of 5. Would not recommend. Audio listening. That is Dominators Joe Bro. Good luck getting past my body guard too. Sean. Cole Comet. Tyler Algier. Sean will just encourage Forrest. Retro Series, Ronnie Lott. There's Romeo Dobs. Wait. There's always next year.  There you go. Sean's the trash man. Good Lord. There's always next year. True. Alright, we got Ted with two spots in team all. Michael with a spot in team all. Richard with a spot in team all. Matt with the Ravens and Penini one. Downtowns. There's Michael Thomas. There's also the 100 parallel. It's like the 100 emoji. And they're just like shorter printed. Wondale Robinson. Thanks, Richard. Appreciate you, buddy. What are we down to on team all now? Wow, six to go. There's K.Dot. It means we're also down to just one. They picked up any Ravens cards recently. Nothing crazy. I'm trying to think. I don't think anything really like nutty and everything. There's Isaiah Spiller. Sam and Donnie are most important. That's true. That's fair. That's true. Why not be the best, you know? True. That's what I'm telling people. Matt Judon. Robin Lopez just followed us. Wow. Hey, if you're going to get banned, man, I respect the hustle on that. I respect the hustle on that one. That was pretty funny. Yeah, Isaiah. He's not bad. Yeah, unfortunately, Robin Lopez 6'9", 6'9", had to get banned. There's Drew Brees, Jordan Davis. For something I cannot repeat. Of course, those are the numbers. Shocking, K-9, nice one there. Shocking. That is Veelish Jones Jr. YouTube chat is missing out. Twitch. Twitch is kind of a wild west sometimes. Traylon Burks, Red Iron Kings. It's a lot more toxic. Yeah, you should. Sam Williams. That is Alontae Taylor. Oh, that's not bad. That's awesome, Richard. Champ Bailey, retro series. He's probably like the... He's probably the... The tight end two right now, I would say. My house, Nick Bosa. Yeah. Lucine. Marquise Brown. I know we're going to be streaming at the national. Nice. There's Matt Corral Rookie. Why would we not? Because I don't think we're breaking there. The Sean Watson. Are you guys bringing the streaming setup from one of the rooms or no? Tiktok. That too. We're going to bring the Tiktok phone and that's it. That's going to be the streaming setup. Roquan Smith. Would be. AJ Terrell, Blue Stars. Especially if you're going to do like a couple. True. George Carl Aftis. Set up at the booth. Nice. We're in the Breakupavilion. That is Rashad White. Bring a couple cards from Alice's. Go, Dean.  Two up, Blue Stars. And guys, I think just six to go on Team All Now. Reese Hall, Rookie. Oh, I got a break in the kitchen. And with the Tiktok phone. Malik Willis got it on it. Easy. Done. There's Cooper Cup. It's going to be hard to sell spots to Michael the basketball fan 43 on Tiktok. This is Cam Taylor Britt. The background should be a toaster with some toaster scootles. Just popping up every now and then. Random intervals. There's Kenny Pickett, Rookie. Nice. There's Malik Willis. Cheetos and break. Oh, yeah. Two things. The furthest thing that could probably go together in the breaking industry. There's Arbala Bikita. Cheetos break. Donnie's going to topple it from inside the fridge. Oh, no. Montreal, Washington. There's sauce gardeners.  It's so cold. There's Johan Dotson. Well, let's keep the doors open. Let all the food go bad. Yeah, there you go. There's Traylon Burks. I got you near yesterday. Why is it rotting? Sorry, Donnie was toppling. This is D-Bose Samuel. Hollow AJ Dillon and a Fadarian Mathis. I'll put like the toppler's stuff on the side. On the side shelves just so I have... Can't take it. There you go. Have my supplies. They hand the tortillas pizza rolls out for lunchtime. My house Malik Willis. Refractor. Hollow, I should say. Sounds good. And Terry Davis Price, TDP. All left, guys. Thanks again. Chris G. Some gaming. Gaming Poisonals. Derek Stingley. Tariq Wollin. Hey, Tyree Kilt. Little Key. Hey, Alan Robinson. Hey, Rob. Hey, George Carl Aftis. Furious George Carl Aftis. That's Marita Rookie. There you go, Dean, the Falcons. There's Terry Salrook. Six to go on Optic Football. T-Mall, everybody. Jake Ferguson, Blue Stars. That is it for the T-Mall Breaks. Just six to go in the second now. Jaylen Petrie, rookie.  Then we got Star Wars after. Star Wars. Return of the Jedi Galaxy. Random pack style. That is what we're looking to fill up as well. There's a Desmond Witter, Greta Rankings. That would be pretty funny. Bring Jake to the National and have people tell him jokes. We'll tell him jokes. Kobe Bryant, Hollow, Bailey Zappi. Let's make him lap uncontrollable. I like Bresaul. He got hurt last year, which kind of sucked. Hollow, Marquise Brown, which I said. He got hurt at the end of last year, or not even the end. It was like the middle of the season, the Bondics. But see, I think he was leading the league and rushing at one point. Like the entire league, which is kind of nuts. Diamond hands, A.J. Brown. He put up a lot of numbers in short period. Tres and Ebner, yeah, for sure. Like he would have, if he kept what he was doing, he probably would have won one rookie of the year. He might have been leading for like, totally ours as a running back, maybe. T. Higgins. Yeah, that's what I was saying. Like he can lead in rushing, yeah, at one point. Is he not a luxurious need? A big like fast option? Not really, I think he's more of a finesse, like finesse one-cut guy. Okay, whatever it is. Basically just the stuff that you're guaranteed. Like retail, you have the blue stars and the 100s. T-Maw, you're gonna have the red stars. You're gonna have more numbered stuff. Yeah, I would say it might be worth grading for sure, Richard. All right, last pack of the break, or last box of the break, good luck guys. That is Michael Pittman, Junior. Shrae McBride. Yeah, 463 rushing, 218 receiving in seven games. Good lord, Jamar Chase. Only one fumble, that ain't bad. So I guess he is a pretty decent pass-catching option. I'm kind of surprised on that, Daniel Bellinger. He strike me at the back. They're just doing like screens or something. Yeah, that's fair, that's fair. That is Fred Warner. Yeah, I didn't know that, to be honest. We learned something new every day. I now have more knowledge on Bristol, Deontay Johnson. Let me take that in consideration, what we're doing here. We'll check here, I will. I will take that in consideration when I repeat in our fantasy league. Okay, well, it's not good. Coy Walker, sorry. Two in your head. Seventh place. They're on ninth place, ooh. There's Jordan Davis, yikes. This is last, this is last. True. Be rich though. God, rich dunk. There's Greg Dualsich, my lord. I'll never forget Rich in the middle of our fantasy draft. Charles Cross goes, it comes to his pick. It's like the 12th round or something. Makes his pick and he goes, that's a league like winner right there. And it was Alan Lazard. Oh yeah. And I'm like, did you just boom Alan Lazard? He's like, yeah, he's Roger's number one guy. No more Tevantay, blah, blah, blah. And then he came in last. There's Garrett Wilson Rookie. I forgot about that. It was Alan Lazard, oh my God. That was so funny, John Dotson. Oh, that was great. There's Alec Pierce Hollow, Rated Rookie, and Skyler Thompson. Lead series, Trayvon Walker. Say, legendary logos, T-Law, that's a cool card. Yeah, this year will be interesting. This year will be interesting for sure. There's Matt Ryan Hollow, Andrew Booth. It's gonna make me miss it. Josh Allen, I have a same bomb. I only got to wait a little bit. Two owners per team this year. Oh gosh, Danny Gray. I might have to bail out those.  We're actually doing that. Taekwondo, and I think we might. Cause there's enough people that wanna play, that's a thing. That's true. That's a thing, you know? We can't really do like a 12 person league, like it's a little egregious. Nothing really to recap, I don't think. No autos, no numbered, no big insert. Thank you guys again for getting this filled up. We got number four coming up after this.


Hello, everyone. I'm Emily Fox. For those of you that are familiar with me, you probably see me pop up in a lot of different open source communities in addition to the Cloud Native Computing Foundation. Today, though, I'm going to talk to you a little bit about the history behind this event. For those of you that have been in the Cloud Native Security for a while now, you'll know this event is very near and dear to me. It's basically my baby. I love this event because it was my first big project that I volunteered to assist with when I joined the open source community, and it was also kind of the first time I had heard of the Security Technical Advisory Group. However, at the time, they were called the Special Interest Group for Security. It was 2019. I was in Barcelona attending KubeCon Cloud Native Con Europe, and it was there that I was introduced to Cloud Native Security and this group. They were evaluating the security posture of several Cloud Native projects I was researching at the time for a project that I was working on. It was there that I attended a talk from Justin Cormack on project security reviews. In addition to kindly answering all of my barrage of questions, both on camera and off camera, he mentioned to me that I should probably check out this group. They were still young in the Cloud Native space. The foundation was still kind of growing and ramping up. They were looking to break new ground and develop new practices to allow us to apply traditional security practices into Cloud Native technology stacks and really drive what mattered in this growing community space. And as always, open source is always looking for contributors, and technical advisory groups and special interest groups are no exception. So you'll hear me refer to them as the security tag or security throughout this talk, but ultimately it's the same group of fabulous people. So I started lurking in their meetings, just like dialing into the Zoom sessions, trying to understand a little bit more about what they were talking about, what they're trying to accomplish, reading their docs, asking clarifying questions to make sure that I understood the direction that this group was heading in. They had a huge ask to fulfill their mission and their charter, but everyone was welcoming, enthusiastic, encouraging, and flexible in understanding like we're still trying to figure a lot of this stuff out. But ultimately what we needed to do is figure out how do we prevent unauthorized access for Cloud Native applications and workloads in a way that makes sense for all of the adopters in addition to the maintainers of these projects. And as long as our work aligned underneath of the three primary focus areas of the charter, we were unstoppable. The charter was set up so that the tag could fill the gap in security guidance, instruction, and tooling, and we'll just generally provide information that wasn't there at the time. Organizations were leveraging heritage and checklist security requirements completely ignorant of all the possibilities that Cloud Native could provide from a security perspective. So we set out to define how to protect workloads to ensure that they're still usable, where security is not a noticeable hindrance to the user or the engineer's workflow. We also needed to figure out how can we take the existing security control bodies and apply those principles to establish a common understanding and corresponding tooling to help developers really meet those security requirements. But perhaps the hardest and most complex yet that we're still trying to solve is how do we break down the complexity in audit? Because auditors really need to have an understanding of how Cloud Native architectures are supposed to be developed, built, and operated in a secure manner. Oh, and do that for every single domain because Kubernetes is just one of the many facets of Cloud Native security. And you can make an argument that due to the natural complexity that Kubernetes has, it is its own domain of expertise. The stickers on this slide are just a couple of the domains that we still need to do explore at the time, and they are their own domain expertise areas. Oh, and we hadn't, we couldn't really fit all of those into the KubeCon Cloud NativeCon security track and talk about Kubernetes at the same time. There just wasn't enough space. And many of these domains hadn't been approached from a security perspective in 2019. We needed an avenue and a place to explore and kind of drive content along these areas to inform adopters and maintainers about how we should be doing security in these specific areas. We needed that avenue to build up security in Cloud Native because it is more than just Kubernetes. It is a multi-objective, multi-constrained problem space with a lot of different domains, it spans the entire SDLC, and whatever comes next, we have to be prepared for it. So Michael Ducey, one of our community members at the time, who he had previously been running some local DevOps days and was really into the open space scene, he filed issue number 209 in June of 2019 to propose a one-day event that went beyond the current security track at KubeCon. There were 14 of us that jumped on board for that issue and we started planning. We used the GitHub issue to plan all of our meeting notes and a Trello board to figure out how the heck do you run a conference and how the heck do you figure out what an open space schedule should look like for a security conference. We had a lot of amazing submissions and we were able to pull together an amazing day of talks as well as a full open space schedule to really drive a lot of discussions. Ian Coldwater and Duffy Cooley started our day off as a throwback to Kubernetes, talking about Kubernetes defaults and how do we move forward in that space. If you look back at the first open space schedule in the first SIG security day talks, you'll find a lot of the same topics that we talked about in 2019 are still being talked about here today. But the difference is that now that we know more, we can share a lot of those learnings with our peers and colleagues and build on top of each other's learnings. And you'll also find out we talked about software supply chain security attacks before it was cool. We talked about defaults, we talked about compliance and machine learning, and it was a lot to cover in just a single day event. It was a huge success. The program committee and myself and the other colleagues were stoked to hold another one and make it bigger, make it better. So in 2020, we held one for Europe because we wanted to ensure that the European audiences security concerns and care about were similar or at least addressed within this conference. And then later that year, because that one was a success, we did the same thing for North America in 2020. What we did, though, is after that initial event, we performed a retrospective to really understand going from day one to the second event and the third event to get community members feedback. We had a lot of interest from folks. The Twitter chatter was strong, excellent discussions by community members in the open space arena, and then we got a little hint that people wanted something a little bit more hands-on. They wanted workshops, they wanted tutorials, they wanted something to allow them to take the theory of cloud-native security and apply it into practice. So that's what we decided to do with that North America. We held a CTF and it was fabulous. If you were here yesterday, you heard Andy and Andres talk about how we executed those CTFs and how our community members responded. And that's kind of been the thing with a lot of this, is partnering with new community members on what we can do to make this a positive experience for everyone, making sure that they have those lessons learned and that they can take them back with them to their companies and organizations with the correct skills to uplift their overall security, showing how attackers can compromise containers in a fun and engaging way. And it's not just the attendees that get a lot of value from this event. Individuals that run these events and participate in the open source community, they're leveling up their skills. They're able to identify gaps and challenges being experienced by adopters through discussions with their colleagues and peers in hallway tracks or in open space talks. They're also able to strategically leverage some of that event content to drive attendees like you to talk to each other, figure out what's going on in API security, how did you all solve this most recent vulnerability? What are you doing to improve your software supply chain and what is the evolution of that look like for your company over the past four or five years? Because ultimately we're all trying to do the same thing, uplift security. And we've been able to increase industry's attention to security and cloud native over these past four years because and we're going to continue doing it because there was and continues to be a gap. And while that gap is significantly smaller, we're still growing this space and learning and uncovering new areas to explore. You can see from the metrics on this slide, we've doubled the amount of security projects and products in the cloud native computing foundation's landscape. We've increased the amount of security reviews on projects that we had. We even had a major review process revision and we're talking about doing another one to really drive more value to maintainers as well as adopters. And it's because of the first security day and all the security days that came after involving into this conference that allowed us to provide a place for security practitioners to exchange, learn in a way that was not addressed by the previous security conferences. This conference is an avenue to share your experience and to learn from others. I would like to see it continue to expand beyond just cloud native security into open source security because both of these are complementary fields. And as we see more maturity in cloud native security tools, projects, guides, documentation and resources, we're seeing them applied outside of cloud native architectures. This event has grown because of attendees like you and those that came before you, but it was started because of the cloud native security community and in particular the volunteers and passionate members of the security technical advisory group who have driven more content from their work into this conference. And this is the work that moves cloud native security forward, connecting members, solving problems, establishing best practices and sharing what we've learned. I want you all to take this opportunity to network with your peers, talk about some of the challenges you're experiencing and how you've solved them as a throwback to the original open space and collaborative nature that this conference started from. Thank you.


All right, I think I'm gonna go ahead and get started since running a little late. So, hi everyone, my name's Grant Scofield. If you didn't guess from the big slide, I work at the 10,000 pound grill in the Ruby room right now, Engine Yard. I've worked with Engine Yard since March after moving on as the primary developer of aDrive.com. I'm a support engineer, and that's a little bit different of a role at Engine Yard than most places. Support engineer encompasses not only being able to develop and debug Ruby applications, but also understanding systems infrastructure as well. I am an oaky, I'm from Oklahoma City, and I always kinda look down upon Texas, then I went to a gas station, found some really nice beer at 10 p.m., and found out I could buy it till midnight, and that's a lot better than what we have in Oklahoma City. You can follow me on Twitter, under Scofield. So, I wanna talk a little bit about the cloud in general first, because I think that the cloud is taking on this sort of web 2.0 idea. The cloud means a lot of different things to a lot of people now. We have all these different things coming about, but they're really all old ideas. People used to timeshare on mainframes, they used to share these systems, and we've just taken that idea, applied the internet, applied all these new tricks, and now we have supposedly this OS that's gonna run completely on the cloud. So, while we're evolving, I suppose we're going back to the old ideas as well. There's a few different types of cloud computing, and software as a service is one of those, and I think that's the one that most people are familiar with. People are familiar with, of course, Google Apps, using CRM software on salesforce.com, Twitter, and the way that I look at it, really the internet's becoming the software as the service now. Everything we do is online. Everything we do is on the internet. There's also the idea of infrastructure as a service, and these are people like Rackspace Cloud, GoGrid, Sun has a system, VMware is going to one day have a system, Amazon Web Services. These are all providing the base tools you need to actually do something, and that's where we come in. We're entering the market as a platform as a service, just like Google App Engine, Windows Azure, Salesforce is actually getting into that as well, and I didn't mention Spring Source, but those are another bunch of people doing platform as a service. So, the engineered cloud. The engineered cloud is pretty much divided up into two pricing plans pretty much with the same features, and those are Solo and Flex. Flex is a beta product right now that has Solo pricing and you can get on and try it out. The difference between Solo and Flex is Solo only allows you to run one instance, whereas Flex is going to allow you to run multiple instances or a cluster. Runs on top of AWS, so it leverages all those nice things that AWS gives you, like elastic block storage, or we give you your S3 credentials, so you can even use S3 out to your clients, just not internally as well. One of the big ideas that our development team brings to the idea of the cloud is the infrastructure as code, having these repeatable things that we can click a few buttons and spin up a few servers and have that server just be like all the other servers, but tweakable as well and customizable. And then the Engine Yard stack is one of the key things, I think, that may set our cloud product apart because we've been working, you know, some of our lead guys like us have been using EngineX for years and been big proponents of EngineX, and so we bring all that knowledge and all those years of experience and we're applying it to our cloud product well. Now, don't be caught up in all of the cloud stuff right now, there's a lot of people saying the cloud is the future, it's not going to be the future for everyone, you just don't want to get on the cloud because you want to be cool. And if you're doing it wrong, the cloud can actually be a liability. If you're doing a high amount of IO, there's reasons why people like Facebook or Twitter aren't running on the cloud, something like Cassandra, which is very, very high O, is not going to necessarily fit really well in the cloud. So you need to look at your requirements and look at what you need to do. The cloud is not going to kill all your rabbits for you, it's going to solve some problems for you and can solve them very well but it's not going to solve all your problems so sometimes you may need to take a step back, look at your problems and reassess is the cloud the right solution for me or do I need to change my application to better take use of the tools that I currently have. Now, in my past I was a sysadmin in Boston I worked for a company called IT Software and managed thousands of Linux boxes and there's always something very nice about the tactical, that tactile aspect of a server or a NetApp or my Switch or my Baytech PDU. There's all these things that I can touch, I can go into the data center, I can kick it if it's being bad at night. Having that physicality is really nice and I think that being a sysadmin that's worked in large environments that's something I always liked. What I didn't like was filling out all the POs and having to wait three months for that hardware. So that's where we get into the idea of instant provisioning. Whenever I had to order 100 servers it would take me months in order to get the right people to approve, get the vendor who could be Dell, could be anyone to actually deliver those boxes, I'm gonna have to sit down, have someone configure all those boxes or you use Red Hat Kickstart or do whatever I need to do and that takes a long time. In this modern age with things like Tech Crunch and Dig, you need those 50 servers one day, you don't need those servers the next day. So what our product allows you to do is it allows you to instantly provision boxes as you need them. And one of my favorite things is how easy the deployment is. I mean, I think that whenever I started using Capistrano many years ago, we were all really taken with how easy deployment became but it's getting easier because of this idea of infrastructure as code. We also provide a lot of flexibility that I like because what you're able to do is because of this instant provisioning I can spin up a test server and I can run a long running process like a migration and see if it actually works and not have to worry about when I move this to production is my whole site gonna be down for four hours and the migration fails and I'm chasing my tail to fix things. And sadly, unfortunately, I think as time goes on, there's gonna be less and less needs for startups to have sysadmins because everyone's working in the cloud and it's making it so easy. You don't need to know all those really esoteric and Ginex configuration things to get your site running optimally. So finally, we're gonna go ahead and do some stuff now. And so what we're gonna do is we're gonna go over to our cloud environment and we could use Quickstart to get things a little, done a little faster but I'm gonna go ahead and take it the long way. The app that we're actually gonna be working with is a personal app of mine that I deploy on the nGeneric cloud which is called Twirkel. We'll go ahead and use my username with that. You have a choice of nGenex and mongrel and nGenex and passenger environment. Apache passenger is a bit legacy, it's going away. This is actually our staging environment so I guess that's why it's still sticking around there. So I've just created my environment. I'm gonna go ahead and do an application. Oops, hit enter too soon. We're gonna give it a GitHub URL where my repository sits with a, you can actually use different applications. We're not gonna go into a lot of, you know, Mirb and Rack stuff but those are available as well. I'm gonna go ahead and choose Rails two through three and their domain name. We're just gonna go ahead and throw that in there for now. We're gonna create our application. So there's a few more steps involved. We're gonna need to take anyone familiar with Git and doing Deploy is probably with Capistrano. We're gonna go ahead and go add this key to our GitHub repository so we can do our code. Oops, wrong key, I'll fail, really. Yeah, I think you're right. There we go, good call. So there we go, we have our GitHub Deploy key in place. We'll check that again. When you're setting up your instance you have the option to add gems. We'll send this out to James and we'll just add faster CSV. We can do specific versions, add those gems to the environment. You can also do that with Unix packages. If you need to call out to anything you may need and that's pretty much it. And then once we're set up our environment we can go ahead and create instances. So what we're gonna do here is we're gonna say, yeah, we're gonna want three application servers. These, you have different options of the different levels of Amazon systems you want. We're forced to use a separate database since we have multiple application servers. We'll keep everything else the default. We'll go ahead and boot this configuration. So we see here now what we have is we have our three application servers booting with our master database. Now these are automatically load balanced. If we lose one of these instances that instance is automatically going to be replaced for us. So there's lots of bells and whistles that we give you with the system as well. We give you built-in monitoring. Right now we don't do external monitoring. That'll be coming really soon. It'll monitor your applications. Monitor your memory usage. If your memory usage is, if you have less than a few percent of memory for a certain amount of time we're gonna email you that 10 times and we're not gonna spam you, we're gonna stop it. But we do give you the monitoring abilities. Usage graphs such as your IO usage, network usage, et cetera. Really painless SSL certificates. SSL certificates are a few clicks away. You can either use a self-generated or self-signed cert or you can use upload your own. And other tools we give you are the backup tools. We use Elastic Block Storage System from Amazon which gives you the ability to do incremental snapshots. So you'll take a snapshot. The next one you take is gonna be incremental so you can recover any state of your system if you need to. We also have built-in MySQL dumps and all of these things are configurable. So we do support Capstrano for deploys. You can go into our application and go ahead and grab your DeployRB and Deploy just like you're used to. But what we've tried to do with the system is bring a few other tools to the table and what we're using is we're using Chef for deploys now and that gives you post-deploy hooks just like Capstrano would give you but you actually check those into your code base. You can do one click deploys and I'll show that right now. And then you can also use GitHub's ability to do post-commit hooks or actually any Git repository you could implement that yourself. So we see our system still coming up. The servers are gonna wait on each other, wait for the database to boot but they're all in different states but eventually they'll come up. So we're gonna go ahead and pull the cooking show thing where I have a little cluster already started up for so we can go ahead and look at it. So we have pretty much an exact mirror of the environment that we had before when database three application servers. So what we're gonna do is we're gonna go ahead and go over to my application, my Torcal application and we'll just edit some code here and save that, we'll go, let's do it again. Push that up to GitHub. Then before we deploy what we'll go ahead and do is we'll look at the current version of the website. Since I have multiple versions running we're just gonna go ahead and use the IP and not worry about host names or anything like that. So the Torcal application here, we're gonna go ahead and go over to the cloud and we're gonna deploy. Now I don't have any, of course, I don't have any migrations in here so we're just gonna go ahead and deploy our code. And you can choose different things, you can choose different get branches if you want to. And so when you click deploy, any configuration changes that need to be made like if you add an SSL cert, if you have a new SSH key, things like that, those are gonna be deployed as well. And as we can see, we're deploying across everything but the database server. We're deploying the application now, there we go. We actually use HA proxy to load balance in between all the individual servers. Amazon does offer a load balancing system as well. We find the configurability and the control that you have with the HA proxy is really great. So we've deployed our code so hopefully if I did things right, when I refresh Torcal what we're gonna see is we're gonna see the little change I made there. Now going to the website and hitting deploy and one click your code is a lot of fun. But we can also do a few other tricks with that as well using get post commit hooks specifically with GitHub. So we'll go ahead and save that. Now before we do that, what we actually need to do is we're gonna need to go to our application here. And as you saw, we'll have the deployer B is over there. But what I can do is I can click here and I can get a specific URL that we can go over here into GitHub. We'll go find my repository here for Torcal. We'll add a post commit hook in and then I'll show you in a different way that we can deploy this. We'll just add a simple service again here. We'll update the settings. Now anyway, I don't know if many of you use the deploy hooks. We'll go ahead and just do a lame check-in right there. Oop, can't do that. Messed up because I didn't actually add in the stuff so we'll just do, we'll just add a simple file. And what we're gonna do is we're gonna add these brackets in here with specific commands to deploy Torcal. And then we're gonna go ahead and push that. And once we push that, GitHub is going to recognize that we had that specific deploy message in there and then if we rush over to our cloud again, we're gonna see that get deployed across the instances. So I actually didn't need to click, I didn't need to go to the website and click deploy.  So another feature that I really like, personal question, go ahead. Sure, yeah, yeah. So if there's actually a whole, there's a whole system that GitHub's using that lots of people are buying into this standard of message passing via the web. And so that's just the specific message that you put in that GitHub then posts into our environment which then deploys your system. So one of the really neat features that I like is the idea of cloning.  And like I mentioned earlier, you can do a long migration or you can test a specific version of Rails if you like. You can make changes to that environment.  And the clone system is very easy. I can clone an entire system with one click. We'll just call this staging. We'll go ahead and make it production for now. We'll just let it do anything it wants with the IP address. It'll clone the environment. I think this is a really powerful tool because a lot of people will spend a lot of money to keep up an entire staging environment that they mainly use or a pre-production environment or a QA environment that they mainly use for a few hours but they're dedicating an entire system or a few systems for database and things to it. And so this allows you really easily to clone your environment, test anything you need to test, and make sure everything works with one click. And Amazon's gonna take a little bit to bring those things up. So with this idea of cloning, because we're using the EBS system, we have the ability to scale both ways. You can scale your application vertically and horizontally. When I talk about scaling an application vertically, what I'm talking about is increasing your CPU or increasing your RAM because that's your database box or that's your heavy lifting background box that's running RabbitMQ for you. So I have a single environment here. You can't actually do this live. It's not something that, because you actually want a snapshot of the system, before let's say we wanna increase the disk space, we're gonna go ahead and shut that application down. We're gonna give it a few seconds to hopefully create its snapshot, finish creating the snapshots and upload them. And as we see, we can't create our environment here now. But I do have a few old storage volumes that I could pick. This is an older snapshot that I ran. So I could just pick that, if I can wait about 30 seconds or a minute for that snapshot to finish getting in place, which it is now. And I can select my latest snapshots. I can increase the disk space. I'm not, I could actually even grow my environment if I wanted to move from a single instance to five instances, I could do that as well. I'm gonna save us a little money and not do that. And I'm gonna boot the configuration. So with a few clicks, what I've done is I've just taken my environment and increased the disk space. I'm bringing my environment up. There's a little bit of downtime involved in that. But if you handle it an interesting way, you can prevent that downtime. Question, go ahead. Well, it's technically it's not an engineer creating your snapshot. But yeah, I understand, sure. Yeah, I think that it's, I haven't seen too many problems with that. Although, I have seen a few problems step up. But if you terminate the instance, the instance is going to come down in a certain way. So your web server is going to stop, your database is going to stop, and then the snapshot is going to get taken. So you're not gonna lose any data. Things shouldn't come crashing down around you. Yeah, actually, yeah, that's, I was gonna talk about that a little bit, yeah. But there's also a snapshot feature that you can actually take a snapshot right then and use that as well. So we're gonna talk a little bit about scaling, that was scaling horizontally. Let's go ahead and talk a little bit about what happens when you get famous on the internet. So you get on TechCrunch, you get on Dig, someone starts talking about Twitter, or you get on the New York Times. You're gonna need add capacity. And add capacity, adding capacity is quite simple. It's, oh, that's interesting. I'll have to wait for the environment to come back up. We have a cluster that we can work with there. Adding capacity is quite simple. All you need to do is add an instance to the cluster. We have the ability to do utility servers as well, so those utility servers aren't going to run your web servers. They're gonna run tools like Solar or anything that you can configure with Chef. So once I click add an instance, we're just gonna go ahead and add an instance. You can add up to 20 instances. If you need more than that, you can talk to us. That's just where we limit it right now. But really, if your application scales really well, horizontally, that prevents the Dig effect and the TechCrunch effect. And then whenever, a week from now when your traffic goes down or dies down, we can go ahead and terminate any of these instances that we need to to get back to the capacity we need. So we're only having the capacity, or actually, we're only putting out the capacity that we actually need. We're not investing a lot in overscaling it. The way that you customize the environment is with a tool called Chef. And Chef is a really interesting way to configuration manager systems. And so we wrap around all of that and it gives you the ability to do a lot of really nice, custom things with your system because most of the Rails applications I see every day are not one-offs. It's not a simple website. Someone's gonna want to run Tokyo cabinet. Someone's gonna want to play with Redis. And so we'll hop over to some code here. And we'll look at a very basic Chef recipe. And this one, I just opened this one up. This is specifically for CouchDB. Chef is written in Ruby, all looks like Ruby, codes like Ruby. And this statement right here simply tells the system to add the package on the system for CouchDB so that I'll install CouchDB, setting up the permissions on the log directory. We're using a template. We're templating out the Couchini file. We're adding a remote file, which we're using from a template over here, which is actually right here. We have templates. And then we're telling it to go ahead and execute so when the server starts. So we're going to add CouchDB to the default startup of the server in case it's not. So when the instance comes up, it'll go ahead and run that for us. So this is a really easy way to add CouchDB to your environment. And there's lots of other Chef recipes that we don't offer publicly currently, but as time goes on, we hope to put those Chef recipes out in the public for things like Sphinx, more custom memcache setups, you can even do in Bari Ruby with a Chef recipe if you like. So this is a little bit about how the environment works. As I mentioned before, we have HAProxy sitting on all of the boxes. And when something goes bad, what we're going to do is we're going to move that IP address over to another instance. The method uses the stoneth method, if you're familiar with that, shoot the other node in the head. So the two other nodes are gonna race to get the IP, one of them's going to get it, one of them's going to, one of the application server that's still up out of the three is gonna promote itself to master. System's going to realize that, oh, we lost a node. And so it's gonna go ahead and bring up another node to replace that. So we still have our thing going right here. Let's just go ahead and connect to this box. And the little man in the middle attack, because I bring up and down an environment so fast, my SSH keys are always changing. So there's no worries about that. We're just gonna do a sudo. Our system's gonna go down. And there's a little bit of delay in this. We check every minute. If we look right now, we see that we're getting, these CPU graphs are actually brought in from the server. And so we see that this server is no longer reporting CPU information. And if we actually click and try to go to the website, we'd see that it's down. So our system is always polling and looking to see what's happening with your instances. And so when an instance fails, it's going to recognize that in one or two minutes and it's going to bring up a replacement for that. And we can sit and watch that happen, but it's a little bit dull. So we'll come back and we'll see that our instance has moved around. So some of the things that I really haven't covered is that this just isn't a Rails product. I mean, everyone's going to talk about Rails and Rails hosting, but we also support MIRB. In fact, our application's built on MIRB.  Our application runs on the Amazon system as well, on our cloud product. You also get crontab management. You can run multiple applications. You also have the ability and your S3 access so you can actually have your clients connect to your S3 as well. You know, you can store the files on the S3 and use your credentials to provide them access as well. And one of the new features that I talked a little bit about is the utility slices for when you don't need to run a web server. Some of the things that are coming, we're adding features every week. These utility slices just came on last week. Yes, I think this is the biggest complaint, I think that I hear from customers that we don't support Postgres. That's something that we're hoping to get out very, very soon. We don't support the slave DBs and automatic failover of DBs. That's something that's coming very soon. And as you all might have known, the JRuby guys came to work at NGINYARD and we definitely hope to provide the ability to run JRuby on the cloud as well. So any other questions? Sure. No. No, the EBS technically runs on S3 but it's a separate environment, it's a separate system. So when we talk about, there are parts of our system that use S3 so when you have a backup, that's gonna be stored on S3 for you. So we do store things on that and we give you essentially the secret keys that we use to store your things so you can use your S3 accounts. You don't have to have multiple S3 accounts and two bills, you're only gonna have one bill with that encompasses all of your S3 usage for your application. So, sure. I think mainly because the Elastic Load Balancer is really new and we were developing this before. Amazon's pretty cryptic about when they do things. I mean, we just all learned about their new virtual private cluster, the VPN system that you can bring in, so they're pretty quiet. It's something that I know that we're experimenting and playing with and seeing, are we gonna work that into the infrastructure? We've had really good luck with AJ Proxy and a lot of the people that I know running fairly large applications on AWS are using AJ Proxy. Now there's a little bit of CPU load involved with that on your main instance but maybe you're, you may need to use larger instance for that but in general it works for us, it's very configurable and we have it today but I know that we're definitely gonna maybe explore that in the future. All right, thanks everyone.


So we have three presentations to get through in this panel. The first is from Mathep. They've been involved with the Wikimedia movement since 2014. That's the contributor to the video on Wikimedia Thomas, who's also working actively for the similar things in the Wikimedia community group. They will have emails. They manage the competition program of Wikimedia Indonesia. This includes planning and executing competitions, seeking potential partners for collaboration, and evaluating the results. And finally, we'll have Amalda, with a volunteer from the Philippines, at works in Central, before Babylon and English, in Wikipedia and Wikidata. And as an administrator of Central, before we're sharing a lot of building Wikiprojects under the Wikimedia Foundation. So each presentation will be 10 minutes. We can have a couple of questions about Q&A afterwards. But first, we have Wikilog in the Philippines, a five-year review.  Let's get started. Okay, good afternoon, everyone. So I'm going to share the most week photography competition in our country, which is the Wikilogs Earth in the Philippines. So let's look at first a quick background. So Wikilogs Earth is an annual photographic competition held throughout May to June. Participants take pictures of local natural heritage and civic landscape in their countries and upload them to Wikimedia Commons. Photos will be under a free license, which can be used not only in Wikipedia, but everywhere, by anyone. So the first Wikilogs Earth competition was held in 2013. In Ukraine, and the contest between international in 2014. Okay, so how do we fund? So you have there, for the participants, you have to review the timeline and the rules in your country. So general plan for the international Wikilogs Earth is May 1 to July 31, but local timelines vary. So we'll have to check your country if you're taking part in the contest in a specific timeline. So next, you have to start preparing your submission. So you must register or log in in Wikimedia Commons. So you have to check the list of natural objects in your country and take inspired photos of them or find it once you already have. Next, you have to check the international criteria for your pictures. So they should be soft taken. Uploadage during the contest period contain an identified national monument and then have a free license or at least two megapixels of size. Okay, so if you're going to organize, you have to create or join a team in your region. So in the Philippines, so you'll make a community. Okay. So it can become part of the Wikilogs Earth family. You have to reach out to the international team at WLVTeam at Wikimedia.org to join the team in your region or your country or to create your own. Next, you have to coordinate the contest. You can create a website landing page and then prepare a list of each one monuments, promote the contest, and then you can also ask for some funding or rapid grants if they're going to have prices. Next, you have to set up a selection of winner. You have to set up a jury that selects 10 winners for your country and then announce them on commerce at the international team by the dentist. Okay, so if you have here, you can also modify the competition rules in your country. So that's one. You have all of that. This must be your own word to not money to the original ABJs and make sure that there is no water marks. Next, all of those must be uploaded to the main wall, division 13, but then two to be eligible. So all of those must be licensed under CC by SA. So participants must have an active email account if the organizer needs to contact. So you have to upload photos from the protected landscapes and seascapes and national parks in the Philippines. Captions and descriptions are required so that forget to add categories also. So make sure that you are not uploading duplicate munitions. So common practical rules you have to sign in or create a new account on the region of commerce. So you have to need your code as well. You need to use the upload border and then you have to share your upload success on social media using hashtags because in the Philippines we have social media account with Facebook or Instagram and you have to wait patiently for the result. Okay, for the judge criteria you have here the technical quality talks about the shortness use of life perspective, etc. and the originality and the usefulness of image or VTT check. Okay, so you can also use the jewelry tools we have one touch. You can search about that. It's a border evaluation tool used in the VTLUMS competition. We have also probably LH jewelry tool. Also in the selection and rating tool for hold to contest for example VTLUMS Monuments and VTLUMS Strict. Okay, so the first indication of VTLUMS Strict in the Philippines was in 2018. So it is to promote the natural heritage sites of the Philippines. Okay, so in 2018 32 countries participated in VTLUMS Earth. So we have received 1,006 images from 185 participants. So you have here Lentini Palashe Dora Yoriver Infant Yau Wan the first prize winner. So here's our VTLUMS Earth 2018 finalist from the doctor. So most VTCs are landscape. Next we have the VTLUMS Earth 2019. So in 2019 we have 37 countries joined VTLUMS Earth. So in the second edition we got 900 entries from 154 participants 84% of which are 2 contributors. And also 9% of the images have been used in VTLUMS Earth. Next, this one is the finalist, 2019 finalist. So luckily we have the 6th prize winner international competition of Blue Water Team by Lentini Palashe. So VTLUMS Earth 2020 we have 24 participating countries we got 970 entries from 250 participants so 91% of which are new contributors so we have 80% of the images have been used in VTLUMS Earth. So here's our finalist for next So again we got 8th prize winner from VTLUMS Earth 2020 the international competition the proud winner in the league by Michael Angelou Luna and also the Noblespire the Philippine Eagle by Shenmue Akit 29th place winner. Okay, to put out the 2021 VTLUMS Earth 34 participating countries for the first edition had 1005 entries from 198 participants 38% so far the large of images have been used in VTLUMS Earth. So we have So in this edition we have already separate category the landscape and then macro photography okay so we have 2nd place winner the international competition the proud winner at Macaua Nature VTLUMS Earth 2020 okay now so VTLUMS Earth 2020 37 participating countries so the 5th edition had 982 entries from 150 participants okay 78% so which are new contributors and 11% of images can be used in VTLUMS Earth so we're just going to wait for the winner international winner okay so here is the final list for VTLUMS Earth 2020 okay so VTLUMS has consistently participated in VTLUMS Earth since 2018 okay so how did we do that so we conduct outreach activities okay we started as three members we have Irving Freud and then later on we got also this one okay some volunteers in the group and then also our members for the participants they already conducted there also the photo walk or outreach activities okay so if you're not into photography you can also support the campaign by having edit accounts or create articles okay we conducted photo walks also involving teachers okay women and then we got partnerships so we went to an island and then we contacted the department of 3DSM and they also visited some schools okay so that's like some of our awarding ceremony you can invite winners and then let them at least share how they get the photos how or some experiences in joining the contest so we have three members okay so for the local organizers so we have a project with for 2018 to 2022 okay Irving we have event manager for outreach awarding we have it from 2018 to 2019 so we have promotion or social media we have promotion for advocacy and then we have for advocacy okay so we have also international organizers okay deep love island so our team consultants from Nepal we have KC Malaga from India and then from Nepal okay for our jury so we have Jun Paasa from the Philippines okay Erdo Santa Thomas from the Philippines and then by the from Bangladesh there also we have from Thailand okay he's there thank you very much for supporting our campaigns not just only weekly vlogs but also other weekly vlogs from petition so we have we have from India from India and then from okay so what are our means so what work well okay through the community outreach activities we are able to reach the individuals and groups which help increase awareness about the contest as well as the weekly movement so next we have social media has proven it's region info so it's from having central partners or promoting the competition in village farms and other you can also use social media to reach wider audience of course if a lot of weekly videos is that hitting two birds with one stone being able to promote the beauty of the country and our young people about beauty videos means we don't have a large number of contributors and then collaboration is the key okay so what did not work so well so more on this one is more technical so there were several reports from the participants whose user account or IP address was blocked therefore we failed to participate in the contest our own user names have been vandalizing the page so that there's a need to check it from time to time so and then the internet speed is also frustrating whether it's Wi-Fi connection or mobile data so so we'll might do some Q&A at the end if you'd like or if you want to answer a question now no okay so for our next presentation so we got two months okay hello everyone well in this session I will share some of the stories of competition that we conducted in Indonesia, Wikipedia or other projects so okay my name is Dimas I have a competition coordinator of Wikimedia Indonesia if you may have some questions you may before I tell the stories of the competitions in Indonesia maybe it's uncommon to see contests or Wikimedia projects maybe many of the photo competitions like Wiki, Laugh, Monument which is many of Asia Canadians cannot participate because of freedom of panorama of course and also we have WikiLogs Earth that Philippines also has great experience to conducting them and maybe one of the newest contest is some local that we recently conducted about audio local so one competition for the Indonesians Wikipedia photos and articles is hard especially in the countries where education curriculum is not teaching about academic writing at the first place so Wikipedia is like academic writing and much of Indonesians not very well accustomed to academic writing so this is a major challenge and the second one is the Polish spirit is not fully grown on Indonesians well because many of them during training of writing Wikipedia many of them asking what's better fit to us for contributing on Wikipedia projects this is why the competition this is why we conduct the competitions because well it maybe benefits them but also we also have some results that can be used on various Wikipedia projects and the last one is only focus on particular topics mostly celebrities or maybe some hate bombs or maybe AKB48 or girlfriend or boyfriend etc and for the hard topics like science, history it mostly neglected so the competition is a very easy way to introduce Wikipedia projects, increase the content and also content quality and quantity and also to find new content but also simultaneously so it's like so one stones and you get three worlds and the competition also can be used to advocate several issues for example like climate changes or maybe human rights so we also we have conducted many competitions well that's too much but I only I only share about three competitions that have some interesting stories okay the first one is Euphoria it's conducted in partnership with EU delegation in Indonesia it's equivalent to Embassy and originally it's conducted in 2018 for the celebration of Europe Day but today we already conducted yearly euphoria with several teams okay the first one most of the euphoria is using this format so the participants need to create one long article and two short articles but not every euphoria is using this format so the first one is in 2018 it's about the EU as an institution and also for the loves in the EU for the prizes for these competitions are laptops and for the winner articles for the GDPR which is the winner's article in 2018 it's also a featured article in Indonesian Wikipedia it's pretty ironic because Indonesian data protection is well, pretty not so good it's like open data okay the second one is Euphoria for climate it's about the climate changes why we choose these topics because Indonesia is well known for many of its deniers maybe it's 21% that population of Indonesians don't believe that climate change is real so it's pretty concerning so we are using this momentum to celebrate the environment day and also to introduce that climate change is real really and for the articles we know how much websites in the United States and also in the world okay during 2020 it's the pandemic time that of course the topics are European Union response to COVID-19 pandemic because we already conducted large competition previously that during 2020 it's just a small challenge that all of the participants continue to take on the same article to improve the same article of the European Union response to the COVID-19 pandemic so maybe the crisis is small just for cultures it's pretty easy and cheap in the 2021 the EU for India has two competitions the fourth one is Wikiport Woman it's about infographics with the woman rights topic and the second one is human rights it's a writing competition on Indonesia Wikipedia with human rights topic so here's the winner it's about domestic abuse in Indonesia child marriage in Indonesia and for the winners for the human rights we give them human rights it's very low on the price in Indonesia it says sliding and because of the journalists are present as a prisoner and for the 2022 we have also competitions in Korea next month it's Wikiport Peace it's about Ukraine and European Union so it's about Russian invasion to Ukraine and European Union response to Russian invasion okay for the EU for India the main obstacles are the first one is English sources only because many of Indonesians don't have good proficiency in English English sources only is one of the major problems that they may not ask for reaching more participants because many of Indonesians don't have good proficiency including reading the text and comprehend its content and the second one is rules and guidelines maybe it's too complicated this is typically impact on the infographic context which is many of the resources and material are copyrighted so it cannot be uploaded on Wikimedia Commons okay for the second one is it's inter-affiliate challenge for Wikimedia Indonesia and Wikimedia Taiwan so the the goal is participants in Indonesians create articles with related themes in Indonesia and Wikipedia and vice versa the Taiwan participants creating Indonesian related topics on Mandari Wikipedia so it's a it's a simple challenge that people may create some articles with this topic this topic economic culture and politics and 11 participants will be rewarded with superiors in each country okay so for this challenge we have obstacles the first one is because we conducted this challenge is a few months after another competition so maybe participants get both of similar contest and the second one is unfamiliar topics but we prevent this problem with allowing the participants to translate some of the articles from English Wikipedia or Mandari Wikipedia if they can to Indonesian Wikipedia okay the third one and the last one is pretty interesting this is our first spoken Wikipedia contest so participants may create the recording of one of the future articles in Indonesia Wikipedia into audio format during this competition we are partnering with one of the largest communities in Indonesia that focusing on these topics is Indonesian voice over and another community but unlike the previous one this partnership is pretty informal that we are not stated this as actual official partner but we consulted with this community to ask for the rules, guidelines and also they supply us with judges which is helpful to conduct this competition with ease because it's first time and actually I don't know for the first time that what we need to prepare to conduct the audio competition so the contestant need to create recordings of the articles in Indonesian Wikipedia one of Mandari articles and one pretty feature articles for example it's like this of the one it's been like a 45 ads yeah I think it's pretty beneficial for with disabilities that maybe have some difficulties to understand the screen recording because screen recording is not suitable to Indonesian language so we created this challenges as a spoken Wikipedia contest in Indonesia to help them to understand more about the articles on Indonesian Wikipedia but during this competition we have many obstacles the first one is more important because creating a recording is not as easy creating an article or a writing article and the second one is too overwhelming because yeah too many guides too many rules so maybe it's not it's not easy for the first time to understand what is the checking method it's also not easy because we need to hear to listen every minutes of the recording but one of more interesting finding in Wikipedia is more women participating in this competition than the previous competition when the previous competition is dominated by male participants during Wikipedia or spoken Wikipedia competition it's more women that participating on this competition so maybe it's pretty useful for women more participating in Wikipedia projects when we creating a competition what we need to do the first one is of course the topics considering what needs to be improved on Wikipedia projects just focus on the one thing because it's less topic and less confusing just focus on the one topic that it's really need to improve the second one is rules and guidelines because much of the participants are newcomers the rules and guidelines it's like a mandatory because this is where participants may learn about Wikipedia projects it needs to be as clear as possible and lastly prices of course there is no competition if there is no prices you may try smaller prices like vouchers, souvenirs or if you are prepared for larger competition so we want to give some some grand prices like laptops or podcast gadgets etc and to initiate partnerships what is the final point to give off is the first one is reactive and patient because finding a potential partner is not easy sometimes depending on those things are not giving a follow up so it's okay don't be so demodalized if an organization is not interesting so patients is better but the truth is weird of course and the second one explains a lot because it is partnership of course the partner candidate wants that this partnership will be beneficial for both them and for us so we need to explain that everything about Wikipedia projects that competition is conducted and what is benefit for them also it's okay to compromise because well some situation for parties need to reach an agreement so yeah maybe the rules adjusted or the topics maybe as request for the other parties like EU that maybe have request of Ukraine okay we will conduct the competition about Ukraine topics but the competition will be smaller because the topics of Ukraine is not so not so many and the last one is always responsive because that's giving an impression that we are easy to cooperate and the partnership will be working for the long term for summary, try to organize manageable competition first maybe like Wiki Loves Earth is pretty easy to first timer to conduct competition when initiating a partnership keep the expectation low because yeah so many so many candidate partner candidate maybe ghosted us to partner with other Wikimedia affiliates of course Wikimedia Indonesia always open to competition with other Wikimedia affiliates and it's okay if the number of participants is below the target but at least there is a new content as like Min said it ain't much but it's honest work so thank you so much good job we will try to do it but next welcome I might have to split some slides so that we will be able to go to the panel so I have to set heads up if you want to participate in the demo you will need our laptop so I am not sure if it's already available on the mobile interface so yeah that's still so I am again I am Imelda I am part of the campaign so for today I will be the structure of my presentation is introduction for the companies product team, the event center and the first feature of the event center is the event participation so the company's product team is the only part of the team of them in the foundation that aims to like provide some resolution to a company to organize this problem and the mission is for organizers to have simplified workflows and more power tools for the organizers to be able to join a single new organizers in a very easy way so the company's product team the first project is the event center so when the company's product team was developed they conducted a research of more than 20 committee organizers movement from the different regions and they provided this information of what organizers would want and then on this project team developed the actionable items for example an organizer wanted a central place to find tools and resources and on this product team decided to develop this organizer center to include new different tools on this building, event creation, registration so event center in general they and we should improve organizer's tools in a very systematic way and provide features for both the organizer side and the participant side which again focuses on improving and supervising workflows and it is a modular feature which means this feature field will be developed separately and it is extensible which means that different features can be added so for the first feature is the event registration so this is all about that organizer part so for the first feature excited to create event registration so we started the top problems that we gathered from the survey from the different organizers so mostly some of our organizers are using absent source registration for example event pride or using this gameta signature by writing their port as their signature to participate so yeah so why registration because in software development we believe that this registration feature is the very solid building in the development of other features that we are going to develop in the future so as you can see from the registration portion we will be able to create that event creation and communication tools in summary the event is we would like to be of organizers a more easier way to create this registration and for participants to have easier access to event and easier participation experience so before I go to the demo this introduction this tool you can only access this tool under this namespace so we will be having new namespaces the namespaces are Mr. and Mr. Dogg so for this tool once we develop this extension we will be able to create new namespaces which are the event in the event building spaces so also we will need an event page so this is an example of an event page I know some of you already created the event pages so for this example we are using the comments namespace but in the future we are going to use the event namespace for these namespaces so we will need to go to these namespaces so these are the available sites for us to use the tool again I suggest that we use the path to the media yeah alright so this is a test we can create your account you may not use your official media account I am going to go I will so I hope everyone was able to create their own account so yeah again to be able to enable the registration we need an event page under the event namespace so I will create an event page under the event namespace for our example we are going to use this search on the site so as you can see we don't have an event page yet and then I will put this and it is like something here to be able to create a page for example this is an event page but normally we will have more information with objectives and goals of the event but for now I am just going to test the event page so you will be able to see that your event page was successfully created when you pop up in your audience so you can both create the registration through this pop up and you can use this visit and do it later then you have no more time to create it so yeah see enable registration yeah this is the start of your event this is the start of your campaign when you need to track the start and when the tracking is to end it is also just between an online event and a person event or both when you choose both you can add a field for you to add an event you can always fill this information later this goes where the meeting link will go the same way in the country where it is happening it is on the and this thing goes for your meeting for example check out what's up so you can enable it will show you a message that your registration has been enabled your event page includes your registration yes so on the event page that I showed you earlier it will add a banner on the top so that your participants will be able to register and if anyone created an registration so we will be able to see that for this time I will show you how to join no no one created an event page so I will be able to show you how to join as a participant because nobody created a registration so hopefully everyone this is the interface for the participants side as a participant I will be able to see the details of each event I will be able to join just by clicking this also I will be able to read the privacy and all and then continue the registration and then when you see the checkbox you are registered for the event then you can always learn your registration so when someone registered for the event you will always see your marriage so this time again I will be able to show you how to have two accounts to be able to show you how to be a participant in your event page ideally the number of participants will appear here and then other details of your event will appear here a bunch of timelines you can always test the tool anytime on your weather wiki test speaking and currently we are still building the updates for the extension and we have some ambassadors in the community and we have feedback on how to use this tool so please and some young men are the ambassadors of the community and whenever they try to reach out to you please be able to rely on people sometimes so that you will be able to develop the tool when you put them so what can you expect I learned July 2020 during this year when this year was the one that I demoed and V1 will be released at the end of November and V1 will be released V1 will give support for organizers to specify event time zone and optimize confirmation to the emails and also add more organizers to an event and there will be an integration through the programs and events dashboard and event metrics and also an option for required registration so in the next few months you need your help and how are you going to be final organizing because for now the tool will be able to to be accessed by everyone so you will need to have a special right to be able to access the registration tool and you all want to be testers and try different functions so now let's all help together to improve the tool and just try to test it again and test it over and over again because there is always updates from weekly monthly and give us some feedback on our project page and subscribe to our last message we don't actually have any time to do an annual so if you could just ask everyone