Thank you. Thank you. It's like, you know, the new year is here because SNA is here.  Well, this year, ladies and gentlemen, we don't know much, but we'll talk about that. We'll talk about that. And it's great to be back.  I was in Brazil looking with their chief going over their nascent nuclear submarine program, which, by the way, is the real deal. It is on a path. It will be here someday. And literally, we were on the Amazon, you know, running from Anacondas and Piranhas, checking their drug program. Actually, their counter drug program is they patrol the Amazon. So what a difference a year makes. Throughout the holidays, I don't know, you all have a good holiday? Pretty good holiday? Not so bad. The world kind of behaved itself for the most part, and we kicked the budget to January, so that was pretty sweet. Vice Chairman had a big part of that, so give him a big shout out for that. Those of you that wear a uniform anyway. But the deal was people were saying, oh, man, it must be awful, you know, you got to put up with all this and that. So if I could tell you anything today, I got the best job in the world as far as I'm concerned. Every time I go out to sea, and we were out there around Thanksgiving, we're out in the Truman, out on the Gettysburg, out in the Boxer. There may be uncertainty in this town, but there is no uncertainty on our kids out there on those ships. And I'm not kidding, I'm not making this up. They were all full. In fact, maybe they felt, well, it must be bad to be you. I'm okay compared to you. But the fact of the matter is those kids were very happy. So I went out and I showed them, I said, hey, these will be your fire-resistant variable coveralls, and they were very excited. In fact, my son said, I wish I was back in the Navy. Those will be here. In fact, they're delivering now to the baton, as well as the George Herbert Walker Bush. So I'm glad to be here with surface warriors here. My son was one, as I kind of mentioned.  When I was here two years ago, I was really complaining about him, but it's less now. He's paying his own way. So what I want to talk about is a future of surface warfare, just a tad on that, focus areas for me in 14. And a little bit of a thing about a topic called quality of service. I think you may have introduced that, but I'll give it where it's coming from me. And then Shortney Gorton will be here tomorrow. He's going to talk about another aspect of that in greater detail. But by my bed stand is 1812. I'm a little late getting through that, but it takes me a while to get through books. And every time, you know, I feel kind of, oh man, the weight of the job or whatever, I pick that book up. If you haven't read it, I really commend it to you. 1812 and start reading about how our legacy and those people that got started in our Navy, surface warriors, and how seamanship tactics and expert gunnery can do a lot with a huge Navy and kind of turn the nation around. It's an amazing thing. If you say, well, what else you got, Greenert? I say, well, I'm also reading a book because I kind of spread them around. I've got a ton of them here on this iPad. It's a book called No Lost Cause, which is about how Columbia turned itself around under President Rebate. It's a very interesting book, and I commend that to you. And that's all from the CNO's reading list for today. And I move along. You guys, the surface warriors have been the backbone of the Navy as I just alluded to from our birth. And it was war fighting first that got us the 1812, the War of 1812. A lot of what we wear today, a lot of what we say today, a lot of our traditions come from that very thing. 201 years ago today, the USS Chesapeake captured Her Majesty's ship, Hero. And it was four months later that the Battle of Lake Geary and, of course, Captain Lawrence, and Don't Give Up the Ship, and all that took place. So, again, great legacy. We've evolved to what is now the most capable Navy in the world. People say, once again, they say, well, man, you guys got all these challenges, and we do. There's no question about it. We got a lot of challenges. But where would you rather go? And I talk to a lot of service chiefs out there, a lot of them, and I think I'd rather be where I am than where they are despite the challenges that we have. So let's see where we are today. Maybe you say, oh, not this again.  We look at where we are, all right? Where we are. Warfighting remains first. I review this all the time. We've got to operate forward, and we are, and we've got to be ready. Those remain the tenants. They'll be there. Twenty years ago, you may not know that, we had about 100 ships forward, and we had about 360 ships. Ten years ago, we had about 300 ships. A little over that, we had 100 ships forward. And today, we have much below that, you know, my folks being, by the way, I haven't seen my A.A., my deputy A.A., my speech writer for like three, four hours. Are they here? That's where they said they were going. I'm getting anything done all afternoon. They're swows. I'm drunk on swows in my front office, I mean, so. If you see, if you see Jesse or Derek, Jesse or Rachel, would you tell them that I thought about them sometimes? Okay, hey, all right. How about that? Okay, good. Jeez, I'll tell you what. Where was I? Oh, yeah. We weight average these, so this guy has the holiday in it, and so my point is on the norm, it's about 100 ships, and this will ramp back up as we finish deployment. But it's surface warfare ships. They make up the majority of those ships that are forward. I know it, you know it. And I would tell you, those at the tip of the spear are getting it done, as I've said before. The surface force fleet vision that Tom Koepman put up, I read it, I read it twice. Tom and I have talked about it. I talked to the surface warfare officers. I think it's one of the most coherent and well thought vision that I've seen from the community leaders, and I don't mean that badly. I mean, it's good for what Tom has done, and I urge you, if you haven't read it, to read it, because it's not just a bunch of pablum. It's got great detail, and I think you guys will do well by following it. It's got important missions and new ships involved in it, and I want to talk about that in just a minute. How many of you have seen Captain Phillips? Pretty cool movie, you see that, yeah? It's a swole movie. There you go. Good job, Pete. So, here's a different take. So I'm there with my swole lieutenant retired son, watching the movie, and the camera backs away right at the end of the movie, and you know, Tom Hanks is in there, it's all done. Good job, and my son goes, wow, check that out, all those ships. And I'm looking at it and saying, yeah, it appears that we have an armada to take care of that little orange boat. Because I think we had the Halliburton, I don't remember which FFG was there, the Boxer was there, the Bainbridge, and I recall there was another ship out there, I don't know where it got, I don't remember that, but I'm thinking, I wonder if people think we have that many ships to chase pirates, because we kind of don't. And I said that, I don't know what message that is, and so that brings me to what I'd like to talk a little bit today, a little bit of our narrative. We have innovative new platforms coming in, in this community as a group with the rest of us. We've got to bring these things in. Next first one up, this is, you know, our favorite, right? The freedom, this is the freedom. She did a good job down there. We wanted to shake her down, find out what this means, get this concept doing. We're writing about it, you've got to write and talk about it, and you've got to talk objectively and deliberately about where we're going with this program. But it's a real deal. It ain't like we got ones these Tuesdays. They are going to start coming at us, and we've got to accept it and move this along. So important aspect, Fort Worth is leaving here soon. I've been pinging that twice. I was done in Indonesia here in December at an International Maritime Seapower Symposium, and in May, the Singhs and some others said, hey, don't be pushing these things at us too fast. We need to kind of figure out how that is. And now they're going, so why is Fort Worth coming so late? And I'm like, really? And the Indonesian chief said, I want this thing in Jakarta, I want Fort Worth. Can you put it on the list? I want to be up on the top of the list. The MOZ, Kuala Lumpur, the Malaysian Navy, he wants it too. This ship really resonates with areas of the world. Next, the sister ship. The other one. They're doing the one before, the monohull will be doing a lot of the conops early on. This ship will be doing a lot of the systems, the mission package. And my view is, and I think our collective job is to bring that mission package in, capability into the fleet and demo it as soon as possible. So I've been pushing on my folks and some of you who have worked this. We're going to do the airborne line, airborne laser mine detection system. Bring that out into the Gulf here this spring. Fossey Miller is ready for it. He's excited. He wants to coordinate that with the international mine exercise so we get real data on these systems and how they work. I think we need to move ahead on that. Next, please. The mobile landing platform, the Monferport, she's ours, and this was her and her sea trials. I'm looking for better pictures, but you get the picture. It's big. It's got volume. It's got persistence. Imagine what we could have done with this in Operation Domion there in the Philippines or any other HADR or a host of others. She's going on deployment and there are adaptable mission packages we're working on and it isn't just go haul it. We don't have the luxury of floating piers and we didn't build this for just that. Next. That's her out there kind of doing, some people get, if you're in the chamber of commerce, you go, my God, it's sinking. You say, no, actually, that's what the deal is. Next. So the Lewis puller. She is beam built. She's about half done and I have not looked at the tables and the bill's not done, but if we get what we requested, we'll be able to transition that previous to look like this and a float forward staging base. All right. You can see what's on there, two 53s on there, but we're looking to, we need to have MV-22s on there. I would love to be able to use it with an F-35B as a lily pad. We'll see. We'll work it. But for now, this thing is designed to support mine operations, obviously, airborne operations, obviously, special forces operations. We need to embrace it and figure what we're going to do with this. Imagine this sitting around off of Somalia, off of Yemen where we could support. Days and days and days of operation. Next please. All right. She's leaving tomorrow for deployment. Amagourtney wrote me a summary and said, okay, we're all ready to go. Adaptable packages. She's headed for U-Com for a month, AFR-Com for two months, come back for an upkeep and then down to South-Com for four months. And Sinclair Harris has a great, great lay down of what he's going to do. Klingen knows what he wants to do with it and he is AFR-Com and U-Com.  My view would have been when you back away at the end of that, she did it. She could take care of something like that. And why not? Fast, adaptable. I'm not going to put you through all the other kind of pictures that I have, but we need to learn about this ship and what we're going to do with it. We have 11 of them coming. Two more will be coming this year. Two more. And then one shortly and about a year from now, the other one. So we'll have four, about a year from now, three on deployment. All right? So we've got to move out on doing that. Next. Oh, here she is. The Zoom wall. Okay? So we're going to commission her soon. And if this is a little bit of a representative of where we are, not underway yet, but not tied up to the pier, not stuck in the dry dock, not stuck on the way, this ship is moving along. And we need to conceptually grasp the capabilities and understand the capabilities that this ship will bring. A lot of it is special access and a lot of it isn't. And imagine what this ship can do in the Western Pacific. And my view, it fits in perfectly. But we'll be bringing the ship with Deliverance 16. It's pretty much on track. A lot to do. First of a class. Very, very modern. A lot of stuff we're putting in. This was part of the transformation piece. But again, this community, we've got to decide what we're going to do with this. So that's kind of platforms. We'll move on to some capabilities we're bringing on. Next, sending her out this summer. I think all of you knew that. What can we do with it? What do we want to demo with it? I'd love to bring some drones out, maybe some of those training, you know, high-speed ships to see what it does. But directed energies in our future. Next, a demo on a joint high-speed vessel for the rail gun in 16. We are moving ahead with that. I was over at the Naval Research Lab recently, they tell me they view the technology to be moving along appropriately. We need more demonstrations. It's about power, repeatable power, and the barrel. And making sure we don't, it literally smoked the barrel. That's hot when that high-speed projectile goes through there. Most of you know what I'm talking about anyway. No more than what I'm talking about. So this is really a big deal for our future. Not just gunfire support. It's well beyond that when we get there. Next, kind of a little bit of back to the future. We needed, in my view, more lethality in our PCs. So folks went out, and so we put a griffin on here without too much cost. The Congress helped us out. Thank you all very much for those of you that might be in here. Many of you were part of this, and now we have a quad pack on those that are out there. We're bringing two more of the PCs out there, which will bring us to 10 out there. So they have a decent gun that's repeatable, accurate. This quad pack, we want to test these out there, not just test them. We want to do proficiency firings in the fifth fleet, and we're on that track to do that. So, by the way, that's obviously two different ships, as you can see there doing that. Okay, next. The classification of this room precludes me from going into too much detail. Those of you that need to know or in the know know that we've got a future with this thing. It's a remarkable missile, and can do more than it was originally kind of conceived for. It's in our future, and I look forward to that in a host of areas. So weapons, platforms, they're different. I'm not saying we're moving to MLPs, AFSBs, JHSBs. Hey, that's the thing of the future. I'm saying it is an augmentation to our fleet matching capabilities and in places that we are now using $2 billion each of ships, perhaps, and other things that we can do better to resonate with and use the taxpayers' money and what we should be using our ships for. So more on that, and we've got to keep the press on. We've got to integrate and embrace the platforms, develop the con ops, tailor the ship to, as I said before, to the mission and the operating area. Now, in operating forward, if you will, we've got to get some places going. I've alluded to a few of them, but let me get to the point. Two of the DDGs are going to Rota this year. The cook will be there in February, just about a month from now. Pete, is that about exactly right? You're going to be there, right? Ms. Secretary will be there, Secretary Mabus will be there. Later in the year, we'll have the Ross there and then the Carney next year. So by next year, let's say we'll have two there and then shortly after that, all four in Rota. Very excited. Two PCs to Bahrain this summer. I mentioned that before and that will kind of close that initiative to get the PCs out there permanently and you saw the lethality piece. We are still going to put little combat ship in Bahrain. The Bahrainis are ready to support. We're doing kind of surveys there and see what kind of mil-com will take place, and that's our plan as we move out. Little combat ships to Singapore. I mentioned that. That is going to pace and we will continue on that effort. And as I mentioned, the joint high-speed vessels, after we get the first foregone, then we'll transition, if you will, to the distribution worldwide and they will spend most of their time overseas. They will be more forward station than rotating through there. So that's kind of the operating forward piece. Let me touch on a few focus areas in the Q&A. I put out my position report in November. I'm not going to drag you through it. Go read it. It outlines the things that we talked about a year ago and where we are on those. So I laid that out there. But the focus areas for 14, for me, will be Electromagnetic Maneuvera Warfare. That's a tough acronym, E-M-M-W. Shortening tells me there's not enough vows in it. We need to get a few more in there. So we'll work on that. But what does it mean to a surface warfare officer? How about safety protection and the means to protect yourself? Because we ain't going to be able to shoot down everything that's shot at us and getting out into the electromagnetic spectrum, understanding it and jamming, spoofing, and defeating by other means is the way of the future. We got to learn how to do that. We have to understand the spectrum from the gamma rays up here to the radio waves down there. You say, really? Do I? Yeah, you have to do that. You're going to have to do that. We have to know where we have our radars, where we have our comms, where we have our Wi-Fi, where we have all that stuff that is spewing energy out into the air. We have to know our signature. We don't know it very well now. We think we turn everything off and everything is silent, and we've actually done some objective measurements and we're not silent. And when we're not silent, we're being targeted, and that's the facts. And if somebody's developing a new cruise missile and they're shooting it at us, we'd be better off jamming it, spoofing it than trying to go find something that can keep up with it, and that's the way it's going to be. So we got to get on board on this thing. The Fleet Forces show they bought it. We're going to do it. We're going to move out on this. The George Bush just did their comp. 2X doing many deliberate MCON, if you will, exercises. We're going to continue to move in that. Undersea domain, Mike Conner gave me the road ahead. I'll get out more on that, but it's when we're going to have an autonomous underwater vehicle, where it's going to be and in what year, and more on that as we come out ahead. Marine Corps Navy integration is a focus area this year. We will continue to support Don Blitz and Bolt Alligator. That is the fleet exercise of amphibious operations. You saw some of the platforms that are going to become part of that expeditionary footprint. They're on the edges. They're not joint forcible entry. That's not what I'm talking about there, but they are a part of what some call the new normal. Persistence at sea, able to go in and do anything from embassy protection to a high-value unit, to a high-value individual, whatever you want to call it, targeting to just response in embassies, whatever it might be. But more on that, and we're going to take a more focused view and have a pretty adult conversation at our headquarters and Marine headquarters on where we are in our amphibious ships, readiness, operations, the Global Force Management Plan. As we've looked closely at our carriers and our carrier strike groups, we're moving right into the ARC process of that. And lastly, the Arctic Roadmap. And I got a little display here. This is from John White, his take on the ice line and the airs. Hopefully you can see this, but it's from 12 to 20. And these tracks here, hopefully you can read that, are our best estimate, that is the science community, on what sea routes would be open and when. And if you look at this, six weeks, north of the sea route, look at that draft, 41 feet, transpolar, two weeks, deep ocean transit. So that's good news. If you're a Merisk individual, you say, okay, I know when I'm open about 2025 and in the Northwest Passage is very complicated. So the question is that, generally speaking, how viable is this? When will it really be viable? To what degree? And is it threatening up there? And who's the threat? What's the threat? And what do we got to do with it? And so I've thrown all these questions out. We have a much more deliberate approach to it. But there's a lot to be answered. It's not like the next gold rush, I don't think. But it is an area we need to understand. We need to take a look at and decide what does it mean to us for security, for maritime security, freedom of navigation, and global force management. So we'll be looking at that more closely. Sexual assault will remain an initiative that is of high importance. I am very satisfied with our strategy. We are making progress, and it is actual, tangible progress in the directions we need it to go. It's a simple four pronged approach. Well, the approach is simple. The execution is very hard. But it's about prevention, and it's about victim advocacy. It's about getting investigations done right, proper, quickly, and it's about holding people accountable who conduct it or sexual harassment. But I'll tell you what, it's commander's business, folks, and that's the command climate. And we can only train so much. We can only keep driving at home, and we've got to get down to business and get accountable for the climate on our ships.  We're going to have to do this together. It remains an important matter in this next year. So quality of service. As we've been talking, actually, for a long time, the McPon and I have said, you know, how do our people feel with regard to their compensation as we've been studying compensation retirement? Do they feel they're being compensated on? McPon, other studies, all that. And it kind of comes down to saying, you know, in general, what is the quality of our folks' service as they're out there, and what does it mean to them? How do they feel about being compensated, which we would kind of say their quality of life, their pay, their housing, their education, that would be tuition assistance and the other things. Child care. In fact, they have a fitness center. You have parking. The things that they get delivered, if you will, for coming to work and how we compensate for them for that. And then ultimately, retirement. But the other side of that is when they walk across the road and they're on the pier and they go on board the ship, what's the work environment like? What's the quality of their work? Is the pier broken down? Is the ship rusty? They don't have good needle guns if they have to do that. Do they have a proper supervisor? Has that supervisor been trained? Do they have maps? Do they have tools? Can they do PMS? When they go to pull the part out of the bin, is it there? It's the quality of the work that I'm not very comfortable with and I think we've kind of slipped in that. I'm looking for opportunities to get that quality of life and that quality of work together so that the quality of service is more in balance. And we'll be talking and working on this in the future. Not necessarily part of that. It's not really an equation. It's kind of a component here and understanding of that service is the idea that we have an FRP, a fleet response plan. I think it's been reasonably successful defining how we get together and how we go out and operate and prepare our ships. Some have said, you know, see, when I took the watch, you get to get rid of this thing. It's not working anymore. I said, give me something better and I get crickets. I'm looking on this to make this right. We think we have a really good idea and Bill Gordon is going to talk about this tomorrow to you in more detail. He and I have talked about it a long time. I've talked to the chairman about this thing because we've got to get the COCOM follow on to the demand, if you will, the request. That is beyond the Global Force Management Plan, the request for forces under our control. But we need, this plan is designed to give us a predictability to give us a cycle that we feel is broad enough and if you will, broken down enough to have the time to do the maintenance, to do the training. But we've got a man up to do that. We've got to make sea duty a primary centerpiece of that. So we'll look at sea pay for that regard. We'll look at sea pay premium. We'll look at who goes to see the most and are they compensated right. We'll be looking at all that as part of the minimum FRP as we go here to the future.  I don't want to steal all this thunder, but I want you to know this. It's been under review for a long time in the department. It has been socialized outside the department of the Navy and I support it and I support what Fleet Forces is doing to a great degree. So if I were to close, which I will here right now but I find my closing pithy comments here, I would say simply our mandate is presence and we've got to be for where it matters when it matters. You know that. We've got to focus on that operating forward aspect of it. We've got to integrate and embrace these new ships that are coming in here. The ancillaries and make them work and make them a part of the scheme of the equation. We have to optimize our fleet response plan. We can strike the might balance with our quality of service. And in the end, you all know this, but it's our sailors and our civilians who are our shipmates that are asymmetric advantage. Go back to the book, 1812. It was the leaders and the sailors back then that made the difference. They weren't all that big. So thanks. Let's take questions and talk about what you guys want to talk about.


Hey guys, what is up? Welcome to my channel. For today's video, I am going to be doing a quick new mascara comparison between two of the most recent popular mascaras to have launched. We have the Rare Beauty Perfect Strokes Universal Mascara. And then we have the Patrick Tau Major Volume Mascara. A lot of mascaras have seen to come out lately. I have a lot that are in my pile to eventually try. These were definitely the most popular and I ended up getting a lot of questions about which one is better. So that's what we're going to cover today. If you want to see that, then just keep watching. Hi guys, if you're new here, my name is Morgan. I am a product knowledge enthusiast. I just love knowing anything and everything about all the new makeup on the market, sharing my thoughts with you guys. And these are two brands that I am very interested and frequently cover on my channel. Full transparency. Both of these were sent to me in PR, but I'm just a little fish in a big sea.  I did in a recent live actually test both of these side by side. However, it cut off. So I figured I'll just do a whole dedicated video on this because you guys did want to know which one was better or not. For a while, I've stayed away from mascara reviews as I have very, very short thin sparse lashes. And I just feel like my mascara reviews aren't with everybody else's who have better lashes in mind. Normally I can't give very good visuals because I'm not working with much. But so many of you guys have reached out that you have similar lashes to mine, so you wanted to know my thoughts. So while visually you might not be able to see, keep in mind it's not the mascara, it's my eyes. But anyways, let's get started. I've tested both of these mascaras thoroughly and both of the kind of videos where I featured them. They were brand new to me. I've had these both for about a week now. I've been testing them every day and they're a little bit more dried out now and used. So now I feel definitely comfortable at giving you guys my thoughts. And let's take a look at both of the mascaras first and foremost. So we are going to start off with the Rare Beauty mascara. This is $20 and it comes in the simple minimalistic kind of packaging. It is made in Italy and has 0.45 fluid ounces. Now the big marketing behind this one is that it's made for every single lash. Their claims for it are that it is volumizing, curling, lengthening and long wearing. Pretty much everything you want in a mascara. Let's take a look at the wand here. This is what it is going to look like. Hopefully we can get a good focus on that. It's a pretty fat mascara wand. So for somebody like me who has short lashes, especially on my lower lashes, I do have a hard time with the size of this wand. Let's take a look at the Patrick Till Major Volume Mascara now. This one is $29. So it is about a third of the price more. An additional $9. So this one is more expensive and mascaras are something honestly that you can get at the drugstore, you know? So the packaging is in line with the rest of his line. Absolutely beautiful. Let's take a look at the wand here. They have similar style of wands and let me just put them side by side for you to see. I noticed more product clumping up on the Rare Beauty wand. Can you see that? But they are quite similar in size. But the amount of product that goes onto the wand is really what is varying here. There's a slight more of an hourglass shape on the Rare Beauty mascara. But yeah, both of them have big wands. Now the claim of the Patrick Till, let me go over to it, is that it's volumizing. It's an ultra dramatic mascara that maximizes your lashes. But they don't really claim that this is necessarily lengthening. This one is just supposed to provide volume. So we're going to take a closer look at this. But the claims are a bit different here. I'm going to curl my lashes with the refer lash curler just to make sure you guys can see. Now my lashes used to be much more sparse and short than this. So I do realize at this point I don't have the shortest and the most sparse lashes. But still there's not too much layering, you know. I have used a lot of new lash for the last few years. And that's really improved the length and volume of my natural lashes. My lashes can't keep a curl for the life of them. So they will fall with both mascaras. So keep that in mind. The Rare Beauty is not curling to my personal lash. But it's a personal problem. I haven't come across a single mascara that's not waterproof that holds a curl. So we're going to start off with the Rare Beauty mascara on this eye. Everything that I'm wearing since you guys are up close and personal right now will be linked in the description box. We're going to start off on the lower lashes.  I already made a mess because if you have short lashes like myself down here, huge wand. Not very good. I'd reach to other wands for my lower lashes. So here's one coat. You can see it did out a little bit of length here. Let's do one coat up here. I have this pesky lash that literally goes down. Okay, so here is one coat. I mean, it looks really good right now. Not very volumizing, but it definitely did out a little bit of length. Let's go into the Patrick Taugh now. I do find that the bristles of the Patrick Taugh seem to be just a smidge longer, which makes it a little bit easier to reach my lower lashes. So this is slightly easier to apply, but very minuscule differences. So here's with one coat on my lower lashes. Let's do a coat up here. What do you think? I think that the Rare Beauty is holding the curl better. It does seem that the Patrick Taugh is a bit heavier. Honestly, with this first layer, I kind of prefer the Rare Beauty. They look very similar, but the Rare Beauty is giving me just a little bit more. So let's go in with the second coat. From my experience, these mascaras definitely change with the second coat. Let's start off with the Rare Beauty. Now that I have that first coat on, it's easier to build that second coat. This mascara is working better than I've ever used it before, honestly. It really is building the length like crazy. My lashes look a little spidery. This is the first time that I've experienced it with this mascara because previously I found that no matter how much I layered it on, it didn't get a little bit clumpy. We're starting to get to that point, but it really is building up length really nice. Let's do a second coat of the Patrick Taugh. All right, you guys, for me, the second coat, and this has been continuous with all of my other uses of this mascara. The second coat is what brings the magic of this mascara. I think it looks way less clumpy. It's definitely not as lengthening as the Rare Beauty. However, it didn't claim to be lengthening. My lashes look nice and full and black. While the Rare Beauty gave me length that I didn't have before, I prefer how the Patrick Taugh builds and I prefer how the Patrick Taugh looks. Going into this review, I knew I prefer the Patrick Taugh mascara. I think the Rare Beauty is a little bit more lightweight on the lashes. It's a little bit better for everyday wear and it does give that little bit of length. But in terms of me, as much as I like length, like I would prefer a lengthening mascara for my bottom, I really do enjoy the volume that the Patrick Taugh gives me and I feel like the Patrick Taugh builds a little bit better. That being said, both mascaras are really great with building. I'm going to do a third coat. Normally I wouldn't do a third coat, but for the sake of the review, I want to see if the Rare Beauty is going to start getting clumpy. Cause this is odd. I've never experienced the slight spider lashes that I'm getting here. The length though, but it's given me spiders and I haven't had that before with this. Mascaras change over time. I definitely prefer the application and the wand of the Patrick Taugh. You guys are getting really cute faces right now. You see how the Patrick Taugh is just building better. I still have each lash really defined and it's giving me that volume. The third coat is a little bit crazy. This is not what I would do for my everyday wear, but I did want to do a comparison for you so you can see which mascara would be best for you. My personal thoughts, if you already have long, big, full lashes to begin with, you just need a coat of mascara. I would recommend the Rare Beauty. If you're looking for volume and definition, I recommend the Patrick Taugh. Based on my preferences for my short lashes, I'm preferring Patrick Taugh. Even though I wish I had some more length with this, I just feel like the definition that it adds is so much more flattering to my lashes because I don't have the most lashes and it doesn't look really messy. Keep in mind lengthening mascaras on my sparse lashes because I don't have much to work with. It's very easy for mascaras to get spidery like this. So definition is a little bit more valuable to me because I have less hairs, if that makes sense. So there you go. Those are my comparisons of the two mascaras. Let me know which side you prefer three coats in. The Rare Beauty or the Patrick Taugh. I hope this video was helpful to you. By the way, as far as wear time, neither of these I've experienced flaking from, which is a problem with the type of mascaras that I like because I like them drier. They flake a lot. These two so far haven't flaked on me. So I hope you guys enjoyed this video and found it helpful. If you aren't subscribed to my channel already, I would love it if you would consider taking this time to do so. And I will see you all in the next one. I guys have a good one.


Hi everybody, I am Matthew Miller and this is another Fedora Council video meeting. We try to do most of our business online on mailing lists and tickets and IRC meetings, text-based meetings. But it's also good to now and then do a face-to-face kind of video call. I'm sure everybody in coronavirus times is used to this by now, so I won't talk about video calls too much. This month we've got kind of a special presentation by a lot of interns who've been working on awesome things in Fedora. And so we've got a lot of people to get through here, so I won't take up a lot of time. I will turn it over to Vipple, who's one of the coordinators for the program and he's going to introduce that and we'll go from there. Welcome everybody, let's get started. Hey, thank you Matthew for the start-up and hey, I'm Vipple, I work in Red Hat, in CPE. I work things around Fedora CI, but today's not about me. We have a lot of interns who did a great amount of work on things around Fedora. We had outreach interns and GSoc and this Council call is to highlight their works. So can anyone see my screen? I just want confirmation once. Yes. Yes. Awesome. So I'm just going to act as an MC and I'll be going through different slides, calling people out and it will be their turn to speak. So I'm just here to help coordinate this call. So Fedora organizes, we had tea and sometimes more minted projects where we try to work with different folks and try to get into the community, work on a project and it has always worked very good for us. This year we had GCI, Outreachy and GSoc, which is Google Code, Google Summer of Code and Outreachy. GCI, for GCI it was the last year this time, Google has stopped that thing. But for now we have Google Summer of Code and Outreachy. Let's just jump right into it.  Hi, my name is Murray Norden. I am Fedora's Community Action and Impact Coordinator and I coordinate the Outreachy internships. The Outreachy program is, I believe, six or seven years old and it is a program that expressly invites and creates opportunities for folks who face under-representation, systematic bias or discrimination in the technology industry of their country. So we have a very wide range of different types of projects everywhere from design to coding projects within Outreachy. And a fun fact, I was an Outreachy intern. That's all I got. Thank you very much, Murray. That was a short and sweet introduction. That was all about Outreachy in brief. And now we have Sumanthro, who is the Google Summer of Code admin. And I would like him to talk about the program for a minute if possible. So, hey guys, this is Sumanthro. And I will coordinate the Google Summer of Code. The program in itself is basically supposed to be for students who want to start learning or this is a stepping stone for them in open source and programming. So usually we have a lot of mentors from Fedora come together and propose a bunch of projects. And then we go ahead and pick some of them and then we try to find interns and there is a certain application period which goes on. This program is dedicated towards students and we have great mentors every year mentor the students. We have org admins like people and me help them facilitate weekly reports and stuff like that. That's mostly what GSock is.  Yes, and thank you Sumanthro for that. In the end, if we have some time, we would like to go through some of the questions if we have around any questions around these mentor projects. But right now I just want to jump into the main focus of this call, which is introducing our interns and what they've worked on. So his order of presentation just so that we know who is coming next alphabetically ordered will start with GSock. And the first project is dashboard for packet packet is a great project. I'm really excited about this. So until if you can take the floor and I'll be controlling the slides. Just let me know. Okay then. So hi, I'm Anshut and I'm working on dashboard packet my mentors are who know and Francis the packet service of the book and you've changed the slide. The packet service is an installable after get for just like GitHub, Badger or GitLab and basically enable it on a repository. And then when you make a pull request on said repository, it validates it. It builds the project in Fedora and basically it gives you the you can basically install the copper. You can use the NF enable copper and then install that that build project and test it out and maintenance can easily see if it's working. And if it is, they can basically approve the pull request and merge it. So it's easy to test packet service also enables you it helps you to work in source kit instead of this kit. So well, that's thing. But we can you change the slide? I have. Is it not visible there? Okay. So progress. I built the rest API for packet and I did it using flask post quest SQL and SQL alchemy. So the thing here to the one new thing I learned here was packet. Basically, we have different triggers right so far full request can be a trigger. The branch push can be a trigger. So basically packet follow this different. What do you call a design partner for databases that I was unfamiliar with and well, thanks to who not on the team. Well, I learned it and basically it was different and I learned something. So that's great. Then I built the dashboard using react and flask. And what can you go back. I mean, that's for good. So well, Thomas actually constantly bothered me to make that's for good and that's something I learned. So yeah, I also learned Ansible and I played with containers and open. But we can choose slide. So this is a picture of the swagger API documentation since there's nothing else to say. Well, it's already changed. I'm sorry. I didn't account for the lag inside changing. This is the next. There's a lag or something. Yeah, I guess. Yes, so yes. The video one. This is a dashboard. I see. Sorry about that. There you go. I built this using react and pattern fly pattern fly and the pattern fly team is great basically because they help me I had some issues and they help me. Yeah, this is basically the jobs page where you can see your list of all the jobs that packet does jobs can be copper bills or Koji bills or even testing farm run where basically tests it tests your rapid transit test inside of Fedora in a virtualized environment. And this is the projects page where you can see all the list of projects that have packet service enabled and you can search it by repository wise or namespace wise. So basically you see the easy you see you enter the namespace and so example get her dot com or get la dot com and you see it. And then you see the list of peers that have been handled by packet. The dash funds that are on testing farm. The center was testing farm I think and you can see the releases that have been handled by packet the branches for branch pushes instead of pull requests. And issues packet creation creates issues so well that's just system. So my takeaways well I learned the importance of good commit messages because I was constantly bordered by who know and. Now I learned to make good commit messages and probably proper grammar and no punctuation. And basically consistent so it's important and then tests. When I was applying for Jesus Thomas constantly. Like in every single bestie thing me to make tests and I learned and now I do. And I would make them and I was with the packet team and they were great all of them and I learned a lot obviously good programming practice. Well that's thank you. Awesome thank you very much for sharing that and I don't see any questions in chat so I guess we'll jump right ahead because I've got a quick one. What what makes a good commit message. Oh. Basically describes what you are doing basic the headline should be at should describe them. Once intense what you did and one thing who not told me was to use it so like this basically embedded. Add this feature update this modify this something like that instead of. Instead of something like packet can now do this or packet can now do that instead of something like that you have to make their imperative. And no full stops I added full stops. Thank you very much Matthew for the question and I'm sure a lot of people will learn a lot of things from this slide now. Next we have improving the network role at Linux systems roles. And the mentee is Elvira why didn't you go ahead and take the presentation. So hi I'm Elvira and my work has been to improve the network role at Linux system role. So yeah next slide. So as you will is an automation tool that helps user configure different target systems at the same time and also deploy software and many other tasks as continuous integration rolling updates and many more. Linux system roles is a collection of roles and modules that assist different system administrators in the configuration of their Linux subsystems. A module here is what we could call in other programs. Go back please. Yeah, thank you. So a module here is what we could call in other programs. An extension or a plugin. And it's written in any programming language and our role is a collection of different tasks that these users can. Can get unused and it usually simplifies their work for many different tasks in this case in Linux system roles. There are many different roles like the network role which is the one I've been working with that helps you. Creating different network interfaces and editing them. But there's also the post fix one or the firewall one. So there are many different things you can do with with Linux system roles. Yeah, now next slide. So my main task in the network role is to add pythons to the integration testing. Right now they use Ansible playbooks written in YAML. Each are the real way that users execute the Linux system roles when they need to. But this is difficult to debug because of the output we get that is the full Ansible output and not just the errors and it's not very specific. It is still useful and we will still use it because you get how the module interacts with Ansible. But we need a way to get into the particular classes or function to test them. So this is the advantage that has added pythons. The fact that you can directly execute the network module from Python and you can get the full power of this programming language. And that you can reuse code easily from one test to another. Next. So here you can see on the top part you have the how you write a playbook. It's just a part of it. And on the bottom part how you write a test with pythons. On a glance you can see that for example an assert would take you on a playbook more than three lines while on pythons as you can see on line 89. An assert is really intuitive and it's just one line and it's easy to see. Another thing that you can see here is that on pythons you can set a specific input for the setup of a test. This case is test NIC1 which means network interface card. And this will ensure that independently of which system you are developing from you will put the same input into the different functions of the module. Next. My work until now was I've been doing different smaller PRs in order to get in touch with how the network role worked because I didn't have much previous experience with it. So I've been working a bit on bugs and also a bit on documentation but the main challenge was the pythons integration and as you can see the PR is open. Next slide. So the current progress on this PR is that right now we've been able to execute the module without Ansible which was the most interesting thing to do because that way you got rid of the unuseful testing, unuseful output and it was quite a challenge because I had to simulate how Ansible modified different files, like different Python modules that it needs. So we had to mock them. And the other thing that is the only thing left right now is to make it really compatible with all the supported distributions. Right now it works with CentOS 8 but we need to make it available for the versions that you can see listed from Fedora, CentOS and Red Hat. So yeah, next slide. So my takeaways that I get from this project is that I've been learning how to use Ansible which I've never done before and also to use PyTest and I'm really liking it so it's a really cool thing to say. I'm also getting deeper insight on debugging many system tools. Before this I was a Linux user but I've never really taken a real look about how providers worked with your network information and how they created network interfaces and so I've really learned a lot from that. I've also started contributing seriously to a free software project which is something that I really wanted to do and that is quite a challenge when you are maybe a bit shy and you just interact with other people through, yeah, digitally. So yeah, I really like that too and also learning to work remotely which is something that I think it's going to be quite useful from now on. And I also think it's a challenge because you get many different distractions and you really need to go through that and really get the work done. So I will answer any questions now. What are your questions? I'd like to hear. Yes, definitely. Thank you. I'd love to hear a tip for working remotely. I think even those of us who worked remotely for a long time can learn from people's experiences. So you want me to say a tip? Yes. Well, I would say. What did you learn? Yeah, I learned that I work pretty well at night. More than I would think and what's important is that you no matter what timetable but you need to get a timetable because otherwise you spend the whole day thinking about all the things you need to do and you are never really working.  So maybe I was like that for only two or three days and I was already thinking I was going to lose my mind. So it's really important to set timetables for that. Awesome. Thank you. Yeah, we all could do better in that. Thanks a lot. Let's move to the next slide then. We have package integration with GitLab and the mentee is Sreyas. Yeah, hi, I am Sreyas. I've been working on package service integration with GitLab. My mentors are Francis and North. Can you go to the next slide? Yeah, what is package service? So package service validates your pull request or merge request and builds your project into a federal operating system. So when you meet a pull request or a merge request into a repository, package service will build your project into a federal operating system and make this build status back to the pull request. Can you go to the next slide? Yeah, I guess this is the lab. I moved to the next slide. Yeah, package service integration in GitLab. So this is what I've been working on. So the first thing that I've been working on was adding Webhook to the project to get the GitLab Webhook and understand the events. So authenticating the Webhooks in GitLab is a way different than GitHub because GitHub has its own way of authenticating the website as the events are coming from GitHub. So I had to work on that manually and how to automate the things for a bit of a different part. So the first thing that we do is pass the events which are coming from GitLab and do things on specific events like if the event is a pull request or a merge request, we know that we have to build that project into a federal operating system and send the build status back to the pull request. So, yeah, so GitLab has a different way of sending the build status back because in GitLab you require permissions of the repository to send the status commit.  So unlike GitHub where you can send a build status to a commit, I mean commit status to a pull request, in GitLab you need to have permissions of the repositories from which the pull request is coming from. So there's nothing as external pipeline in a merge request. So this is one way we are sending the commit status as a pipeline, external pipeline and if party service doesn't have permissions of the repository, I'm sending the status commit as a comment on that merge request. So here you can see that the comments are pending pending and then these will be auto updated with the running and the state of the each test or build status. My data is where research is really important because the first week I've been working on was the project integration with GitLab which didn't do really well. There's always a better way of doing it, so plan ahead. Making draft PRs is a really good idea because you can communicate and see if you're doing in the right direction or have a better understanding of what you're doing. Well, I've learned a good programming practices in terms of readable code and small changes into the repositories and by looking into high stuff of GitLab, we can say that GitLab is not really different in terms of handling of things. But when working on GitLab, I've seen that there are a lot of differences in GitHub per year, so you really need to plan ahead while working on GitLab or these type of things. Awesome. Thank you. Do we have any questions for Stres? Someone else that may have a question? Okay. Yeah, I have a question here. You mentioned, I think, multiple times while you were talking about planning and GitLab being different from GitHub really kind of messed with what you were hoping to do. What do you think you would have done differently if you could go back and do this again? Like, what would you have thought about? What would you have done to do this better the second time around? So while planning, I had a different plan because GitLab has something known as project integrations, which is similar to GitHub app. So I spent a lot of time researching about it and the two weeks I think I spent on it were a waste of time and I think I could gain that more and work on the webbed part more efficiently. So you overestimated or underestimated how the differences or difficulties? What would you say that that was? The difficulty part was a bit underestimated because I thought I could do it in that time period, but then I realized there are a lot more things that I have to do to integrate it with budget. Alright. Awesome. Thanks a lot, Neil, for the question. Yeah, no, my pleasure, question mark. Alright, so moving to the next project we have NM State, which is implementing wireless support for NM State. Sudarshan, are you in the call? I just see a left the call. Okay, we can move ahead and we can come back to this once Sudarshan is back on the call. Is that alright with everyone? Jumping through the slides. And now we have, we are in outreach zone and this is Karma's time to talk about how to create a GraphQL API for Boothi. My name is Haan and the name of my project is to create a GraphQL API for Boothi. I'm a developer and I've been coding. Could you, could you hold that? So, let me introduce Boothi and GraphQL. So Boothi, Dora's operating system, it's basically an interface for developers to test updates to students and for students. Yeah, I couldn't hear you. Am I all audio trouble? Can you hear me now? Thank you. So I was introducing Boothi, it's Fedora's update training system and it's an interface for developers to suggest update changes and for testers to test those changes. And a GraphQL API is basically an HTTP based API, which can be used to create and post data. So right now it helps us to get data out of Boothi. And this is actually the first time a GraphQL API is being used. A GraphQL API has a typical graphic structure which is composed of nodes, edges and fields. A node is like an individual object like a release and an edge is a connection between two different objects. For example, all releases in an update. And a field is an attribute of an object like the ID prefix of a release. Could you go to the next? Why GraphQL? Currently we have a REST API for Boothi, but it was not following the best practices and vis-a-vis its counterparts. GraphQL is, GraphQL exposes a single endpoint and it allows for a faster deployment speed. And it also enables declarative data fetching and therefore we get flexible output structure. The next slide. So a more interesting way to realize GraphQL's uniqueness would be through the analogy. And say you want to order a pizza. So with REST you can only choose from three pizzas on a menu. And if you want something custom, you would have to manually combine their topic. But with GraphQL you can order any custom pizza and you get exactly what you asked for. So if you want mozzarella cheese, you'll get that. And if you want mushrooms or something else as a topping, you'll get that. Next slide. Thank you. So about the timeline and my progress. As part of the final application, we had to give a timeline and my mentors and I came up with the timeline as shown on the Gantt chart. So currently we've added the GraphQL endpoint and we're using the graphical client for querying data. And we've also added graphene and other dependencies. We've added three queries as of now. All releases, get releases and get updates. The first one fetches all releases. And the last two fetch specific releases and specific updates based on the arguments which we send to the query, which is user. And we're valid tests for each of the aforementioned queries. And currently we're extending the implementation to other objects like users and bills. And we're also looking at pagination. And currently we are just getting data out of body. In the future, we also want to write data on the body or allow users to write data on the body. And for that, a stretch goal for the project is to add authentication and authorization, which we work on. Could you change the slide? This is a working demonstration of the GraphQL API. So could you please start that? So we're using the GraphQL API. And we will use code to send a post request to the flash GraphQL endpoint. For example, we want to query all releases and we want their names and their state. So this is the structure of the query. And this is the post request we're using called to write that. This is the output that we're getting. But if we want a nicer output, then we can also use a client like HTTP Pi. So if you want to query like a specific release, we can do that as well. This is the query and the argument is F33. And this is the output. We get a similar output on the GraphQL client. So let's say we want to query the long name as well. We got an error message which gave us a nice hint about the name or about the correct attribute. So let's do that. That is the long name and the state of the update. Thanks. So my key takeaway is one of the major key takeaway has been a considerable growth, avoiding knowledge and capabilities and also confidence in the work I deliver. And much of the credit goes to my mentors. And I also learned about the importance of good intervals, skills and communication abilities. And I had a great community experience and it was a wonderful first time experience in the industry. So thank you. Does anyone have any questions? Thanks a lot. So great presentation. Do we have any questions? I don't think so. That's good. Let's move ahead. Next we have Fedora Baziz migrating to Bazza and Snehal. Take this part. Hi, I'm Snehal and I've been working on migration to Badger. So yeah, my mentors are Michael and Sian and let's go get right into the... So this is how Fedora Badgers looks right now. You can see that there's a Fed message hub, which collects all the messages from every event that is happening. And Fed Badgers is the heart and soul of Fedora Badgers, which reads these messages and applies some rules on them and checks whether someone is earning a badge and awards it to them. Similarly, we have Chrome services, which for some third party... Some applications, some messages which don't come on Fed message, we need Chrome services. And of course, you can also award badges through scripts that sysadmins can run on the server. And yeah, so the plan for migration is pretty simple. Just replace everything that has the rear on it and move it to Badger. So here 30 API would be replaced with Badger Client and yeah, the Postgres DB would be Badger's MySQL DB. Can you go to the next slide? So yeah, the things that I've already done for Badger have been... The first thing that I did was make up SDK. We call this Badger Client and this is basically a Python interface to call the rest API of Badger. Pretty... Yeah, it's a class-based API, which I'll talk about up to this slide. Then of course, I learned about unit tests and yeah, this is the first time I wrote tests. So it was pretty nice to actually learn that. And then we also... I also wrote scripts to add, issue, and revoke badges. So this is admins. If they prefer to use scripts, they can still use them. Then I built... S2, I built images for Badger server, which was probably the task which was the toughest. Probably explains why I've written it down twice. And yeah, so I had to try like a bunch of different base images for this to work, but in the end it was working. And then I also made OpenShift templates and added Fedora authentication. So there are two major tasks that are pending right now, which is migration of Fed badges to Fedora messaging and its integration to Badger Client. And then there's also the migration of data, which so yeah, I have to migrate the Postgres data into the MySQL data. Can go to the next slide. So this is the Badger Client. And you can take a look at the API that provides. It's pretty simple. It's a class-based API. I've tried to type check it. So if you are using any code editor, you'll get all the types that are required by these APIs along with that. And yeah, I think that's it. Can you go to the next slide? So yeah, my takeaway. Well, some people call it takeaway. I'd call it things I didn't do. So yeah, so working from home was a different kind of experience. I'm not really used to it. Most of the time I worked from my bedroom and which was a big no-no because working from the bedroom means you're most likely going to fall asleep. It's better if you have a different room and then work there. So you have that mindset just as soon as you get inside that room. Communication is key. Of course, be in touch with the mentors always. Usually I'd have weekly meetings and that's the only point I communicate with them. Sometimes I contact them between weeks as well. But yeah, that's one thing that I like. And DOTS, which stands for don't overthink stuff. And I think it's most of the time whenever I was trying to carry out some task, I would overthink it. And end of the day, I'd realize that the solution to my problem was the first instinct that I had and overthinking this made me lose time. So yeah, thank you. And if anyone has any questions, I can answer them. I've got a question. How many badges do you have personally? And what is your favorite one? I think my favorite one is Baby Badger. But yeah, I don't have a lot of badges. I think I have some 10. I haven't been that keen on collecting them. But yeah, once Badger is online, I'll be trying to grab them all. Excellent. Thank you. Awesome. Yeah, go ahead. Yeah. You briefly mentioned in your presentation that part of this was involving moving the database from Postgres to MySQL. Did I hear that right? Yeah. Yeah. Okay. I just didn't expect to hear that. I was just trying to make sure I didn't hear that wrong. Yeah, Badger is using MySQL. That's a little unfortunate. Yeah, you don't usually see people moving the other way. But let's move ahead for now. Sure. Great. So next we have Smira, who will talk about creating and improving designs for different federal project initiatives and events. So Smira, go ahead. Hi everyone, I'm Smira. My mentor is Marie Norden, and my project is creating and improving designs for Fedora's initiatives and events. So the project, basically I'm a part of the design team, and the design team provides artworks, user experience services, usability and general design services to the Fedora project. So there are a lot of new initiatives that are always in motion in Fedora, and so you need design stuff for them. So my task was to work on them. Next slide. Okay, so this is the first project that I worked on. So we needed a template for the budget reports. Currently the Fedora budget website requires you to manually enter data because the script isn't always work. So the idea behind the project was to make a template so that anyone can easily enter the data and it looks consistent, easy to analyze and looks pretty too. Next slide. So the process was my first, the first thing I always had to do was research, which was very important in any design project. So research meant evaluating what my project deliverable was, how others did it. So if I was making the budget report, how do others make a budget report? What does it look like? What is the current trend? How does it look? So that was my first, the first step that I would do. The next one was to make a couple of templates. Can you go back? Next slide. We'll see what works. We'll look up stuff from each template and then narrow it down and then iterate over and over until you reach a final deliverable reports. Next slide. So I made a design that I decided even after the final project is submitted, a lot of feedback, good input and a lot of questions. So after I'm using this project, I'll go back. Next slide. Okay. The next project I worked on was for graphics. So to highlight the different components of the work done to make sure that people understand what other things are doing and painful contributions, that was my idea behind this project. Next slide. So again, it started with research. So I had to look up how the graphics look, what are the things I have to take care of even technically. Infographics are supposed to have big bold text, colorful, more graphics, things like that. The next step was drafting templates. So these were the two templates that I worked on and the third step was soliciting information. So if you guys must have seen my mails and messages and tickets and comments that I left. And the fourth part was the bigger research which was actually understanding all this information that I got because then I had to work on it to represent the information. I had to understand it myself so that I could make graphics, make designs, make artwork for that information. So that took up a huge chunk of the task understanding what each team does, what are their motivations or what are their goals, the current projects they have going on and what exactly is the project. Because if I didn't know myself I could never actually depict them in the infographic. The left one, you see the design that is actually the final template that we ended up using and this is the final one for Fedora Join. Next slide. This is the project that I'm currently working on so this is the Fedora Zine. The motivation behind this is to recognize people who are making Fedora awesome, gain more contributors, highlight products and Zine will also be distributed at conferences hopefully soon when we have more physical conferences and of course a digital copy will also be available. Next slide. So of course again, research. I had to look up how Zines were. So Zine was a concept I was not familiar with what exactly is the aesthetic of Zine why are they like how are they different from a magazine? It's not just a smaller mini magazine it's a publication in itself. So I had to look up and actually understand what Zines are. The next step was designing covers so these two that you see these are actually like the final ones and we'll be using one of them for the cover the other one will be somewhere in the Zine itself. And the third part is soliciting content which is currently going on. Next slide. So for the third part I need your help. I want everyone to contribute to the Zine. You can submit anything you want. It can be paintings, it can be poetry, photography, anything that you want to submit. It would be good to have in the Zine and that is the ticket link for the Zine if you're interested in making a contribution. Next slide. Okay, so these are the things that I learned. Stop doubting your work. Honestly, this is because of Marie and the Fedora community with all those always nervous about my designs the stuff that I've worked on. I would always think this does not look that good or this is not really wow, but Marie always encouraged my designs and it's not just her even after I would submit my work everyone worked from the Fedora community would appreciate it and then love that put in bridge my confidence up and kind of help me be more comfortable with showing my work the second is research is very important especially in design you have to make sure that you understand the content of the product and the product itself the target audience, why are you making what you're making otherwise the final design will lack vision or if you don't put enough research in your work then the user will not be able to understand it and it won't make sense to the user and the last one is to step back from time to time there were some periods where I would just for one week I would just keep working and working and the thing is more work did not equate to a better work or a better designs because sometimes I would lose vision or track of what I was supposed to be doing so this is what Marie would always suggest me to take a step back see, evaluate again what I'm supposed to be doing take a breather and then go at it again and that would help a lot even in programming I guess this is called rubber duck programming I think so when you are stuck on a problem you just look away and it comes to you, the solution comes to you so that actually helps a lot in design too so yeah, thanks for anyone has any questions I don't have any questions but I want to say thank you for the beautiful artwork, the join poster stood out to me in particular but you may have seen it in my Nest keynote so thank you for that, I probably should have put the credit there by it so I apologize for not including the credit credit is important and open source so thank you very much for making that and all the other things you are working on as well thank you these designs are a great smear I'm sorry for pronouncing your name incorrectly earlier yes I don't think we have any questions so let's move to the next slides then next we have porting and redesigning Fedora websites and Meher why don't you start now hi everyone I'm Meher and I've been working on porting and redesigning the Fedora websites and my mentor is Rick Ilrod we can move on okay so I know most of you must be aware that currently the Fedora websites are being maintained in two different repositories the sub domains like alt.federac.org spins, labs, arms those are being maintained in the Fedora websites repository and they are independent sites as of now and the main website which is getpedora.org isn't the new repository so my job was mostly basically to move all of those independent websites to bring them under getpedora.org and rewriting them in the new framework which is the flask and frozen flask okay so basically I had to integrate the current build script to include all of those websites and all of those download pages have several download links and the checks and stuff so for that we are using a YAML file and it's a one point destination if anyone wants to update the download links like for instance if you want to include display the beta edition or if some link is broken and we don't want that to appear or if I want to overwrite a certain download link so I don't have to know the entire code base but I can just make the changes in the YAML file and it will automatically reflect in the download links there and for the rest of the the routing part it's these are just static HTML pages we just have to tell frozen flask where to find them so and for the checksum download the current websites that the currents of domains have most of them have a different page for the checksum downloads and some of them are directly linking the checksums along with the downloads so we are planning to move all of those checksums to the security page and so that anyone who wants to find any of the checksums can go over there and it would be easier so yeah that's also something I'm working on yeah we can move forward yeah so the major part of this project was redesigning all of those pages so I try to you know these websites are the first point of contact for anyone who is not that familiar with Fedora for the downloads and so I try to make it as user friendly and easy to navigate as possible and I try to make sure that the user finds what they're looking for and not they are supposed to be minimalistic and concise and yet they should be containing all the important information about the download and the support resources required to use them so and all the websites should be consistent and pretty yeah we can move on these are just some examples you can just skim through these I'll just go this is the IOT page these are spins and labs but this is alt, cloud yeah this is an example of the KD plasma desktop for spins yeah so I I started working around like I started in early July or something and this is my first open source experience so it was a bit intimidating in the beginning you know understanding the whole code base and trying to make sense of how things work and especially establishing a good workflow to have it all work together so yeah it was a bit overwhelming in the beginning but my mentor Rick really helped me at every step and now that I'm comfortable I am having a lot of fun yeah so my some of my takeaways are that when you are building something for the user you have to look at things from their perspective you have to understand like how they perceive and what they want so you have to make sure that you consider all of that and not just see your own perspective and another thing is that you can never get something right in the first try itself you have to keep reiterating and take input and consider their opinions and sometimes you can run out of ideas or things to do and so yeah you should always keep looking for inspiration and one of the most important things was writing clean code so I try to keep in mind that I am not the only one who is going to be reading this code there are people after there will be people after me who are going to work on this code so I try to make it as easy to understand and readable as possible so yeah that's it from my side thank you awesome thanks a lot do we have any questions around this yeah I have a question where can we see or work in progress or maybe to another point when do you expect this to start being merged into the production website yeah most of my lips I have we are all locally built but I'm just waiting for Rick to finish the AMI script for the alt and then I can start sending out PRs looking forward to it yeah I have a small question just from my confirmation Fedora easy fix was not part of your work right no no that wasn't awesome okay that was something just going into it thanks a lot for clarifying that so Sudarshan is back I'll go back to the slides we don't have anything anymore so I'll try to go back and Sudarshan you'll be next let me just see if I can find the slides sometime I'm really sorry for the minute there was an issue no no no it happens hopefully I can reach there before all of us are okay I think I found it there you go you introduce yourself now Hi I'm I'm Sudarshan and I'm a third year computer science undergrad and I'm really excited I was excited to work on this project because this was my first open source project but I have and a person as a student who is interested in networking it was very exciting and next and next slide please I was working in the end state and the project aim was to enable end state to be used by other programming languages and system that doesn't support Python end state is a Python library that manages networking states of hosts and using a defined schema and the project we used was VALINC and VALINC is a simple protocol that encoded all the messages in JSON format and communicates through Unix and TCP software connections and next slide please and so far I have completed the implementing the support for VALINC VALINC support in end state now the basic all functions can be accessed by VALINC and still this implementer is pending for review stage it's all been amended slowly bit of small changes from the members of the group and we have also I have also implemented the system deservices as end state VALINC and during this process it was we were able to identify some issues and Python VALINC package that didn't support what we expected as documented and we had some discussions to review or change the version and we understand that we should support the package it's been shipped to most in default so we have been working around that to manage those issues next slide so this is a sample screenshot I have posted how VALINC works with the command line tool and the first line it shows that we can call the VALINC end state functions show in the specified way using mentioning the VALINC address it's been listening to or we can use the resolve either currently the VALINC is only being we encourage the users to use only this unique socket file based addresses because of some because of some access control that should be addressed later and the second line shows that there's some we can use the directly the using the VALINC interface and the show we bear when we use VALINC utility call resolver to resolve it system wide and we no need to specify the address each time and the second line shows how to pass an arguments in this case the state of the state we desire using VALINC command line tool and actually VALINC doesn't accept JSON but it just accepts only the JSON string slide very good yeah and VALINC can be we can also access this using VALINC clients and interesting thing is we can the VALINC clients can build the clients using any programming languages just with the support of JSON and unique sockets so this is just an example using Python client and the left the screenshot shows that the NM state VALINC interface definitions and as you can see every method in errors returns a log which is a debug or higher level so the debug it and one of the things we had to work around is passing the arguments through to VALINC and one of the issue was that and we had to because of that we cannot directly pass the arguments and we can only pass it without any issue using JSON or JSON object and we are passing currently the NM state VALINC accepts the parameters in a VALINC object under the arguments key and yeah I hope it will be addressed in later VALINC packages and these are some outputs how VALINC show come on and error formats that being that's currently in use and my take away is as being a new experience I really enjoyed working in the community and I was shy to come in because I thought that contributing to open source and need to have a great understanding in code and good practices but these days I'm learning a new language and while learning I am contributing for the packet open source and it really changed my idea on open source and working with professionals thank you I should mention my mentors they were very helpful and Fernando helped me really completing and giving me feedbacks to improve my commit messages and testings and other mentors too and this is being a challenging experience and hope to continue contributing for open source thank you very much do we have any questions for Sudarshan I don't think so let me stop sharing my screen now I can see everyone's faces that's awesome thanks a lot to all the interns you did a great job in explaining all the projects you have worked on and we have very much on time I guess in my opinion and if you have any more questions around mentor project now we can talk about that unless someone else has to discuss something yeah I guess I have general question people talked about enjoying the experience I'm glad we were able to provide that for you in Fedora what could we have done to make it easier to be part of the Fedora project and what can we do to make it so that when your internship is done even if you go on to a job somewhere else or whatever else you're doing we can make it so you would like to stay involved with Fedora as you continue your career in life I think that was a question for interns right oh yes the current system is great it's okay so well it's great yeah I think the thing about the thing you said about contributing even after the internship I think I'm going to keep contributing just because it's a challenging task to contribute here and yeah it's helped me grow and yeah that's one of the reasons why I keep contributing I like working with other people just the first time I worked on open source projects before but not as in with other people I have to interact with the team every day and we discuss things sometimes they don't know the answers either so we do research together and stuff like that basically working as part of a team that's what was the what I like most yeah the community here is really amazing I think I came here for the project but I'm going to stay because of the people oh let's write that one down that's good thank you if I did put you on the spot with that question there but if anybody wants to tell me later like if there's things we can improve experience better or to make especially going forward or as an intern like that DM you can find me let me know thank you in my case I just want to say thank you to all of you because the work you are doing is pretty awesome I think all the projects are going pretty well and thanks to people to to organize to everything related to the internships and you are very welcome you can any of us not only Matthew but anyone in the council or even in any of the teams you can you already should know where to find us or your CEO matrix or whatever so please raise your hand if you have any questions if you want to contribute further or just hang out in the community you know just hang out talk to people that's even very appreciated we love you all having here I know people have already said these things but we mean it we just don't say it because we want to say it I have another thought I just wanted to say thank you to the mentors the folks have taken their time to mentor the new fresh blood no but really thank you to the mentors for putting the time I mentored this this round it was my first time and I found it to be fun and fulfilling there was a lot of good time so hopefully people have enjoyed the mentoring experience as well if anyone wants to comment on that if there's I'm sure there's more mentors on the call yeah hello I'm on the call yep do you have a comment or just hello sorry did you have a comment or was it just to say hello no just to say hello I'm on the call hi glad to have you here alright then thank you again everybody mentors mentees support people all of everything it's great to see this it's one of the many things that makes me excited about the future of fedora and open source so nice to hear from you all thank you again goodbye bye bye everyone thanks everybody