 Hello, everyone, happy F35 release party to everyone. And if you have not yet upgraded to F35, or fresh installed it, if that's your thing, then what are you waiting for? I'm Akash Deep, third, I'm the objective lead and the Fedora Council objective representative for the Fedora Websites and Apps team. And I work with the Red Hat Community Platform Engineering team. Unral, how about you go ahead and introduce yourself? Thank you. Hello, everyone. And also welcome to our first day of the talk on the second day of our release party. My name is Unral. I'm working with Fedora Mindshare Community and Fedora TDA. And also I'm working for the Website and Apps application team as a member, as a developer. So I hope we will be able to talk about all the objective teams and updates together today. So Akash. Thanks, Unral. We welcome you again to the Fedora Websites and Apps objective and team update talk. Let's move on. Right, so here's who we are. The co-leads of this objective team are myself and Ramya Parimi. We are helped with Justin Flores and my Norden's mentorship. Babel Zelowski and a lot more other folks are helping with the program management. And we're actively supported by the Fedora Design, the Community Platform Engineering team, as well as the Red Hat Open Source Program Office. There's a chart on the right side on the screen with tiny markers with all the other team members who are an integral part of the team. And the thing that you see at the very center is the Rock the Web badge, which is awarded to everyone who takes part in our team. And if it looks like something that you want to have, be sure to stay with us till the end, because we'll be telling how to interact with the team and get involved with what we do. And also, the other incentive is seeing your name on that graph. Let's move on. Right, so now that you know that who we are, let's grade that if you knew that already. This is the objective model that we started with. And Unralc would drop a link to the wiki page that you can find it and maybe take a closer look. Thanks, Unralc. Let's move on. Right, so where do we head from? Because the objective model was the starting point. We went back to a drawing board to come up with the approaches that keeps up with the ever-changing expectations from the team and the varying work styles that the team members have. While it's a work which is actively in progress, we, I mean, that includes Marie, Justin, Ramya, and myself, meet every after a couple of weeks to discuss and work on this. And here are the results that we were able to garner so far. Starting with the documentation. Both contribution-based as well as development-based documentation are actively worked on to address the needs of the contributors who would want to jump in and start contributing to the objective. Then we reexamined the big picture. And we made sure that we keep our expectations right for the team and for the objective as a whole. We participated in the December cohort of Outreach 21 internship as a mentorship team. And we have four commenters. Them being Michael Scherer, Franchoa Andrew, Unralc Cesar, and yours truly, to acquire two interns who would assist us with the objective and the projects. And finally, we kicked off the federal website's revamp discussions with Pavel Zelowski's program management experience. So you can pretty much expect good things coming soon. Let's move on to the next slide. With the objective team actively introspecting the approaches and the engineering team continuously working on maintaining the sites that we already have and reworking the projects that need to be reworked on, we came with one realization that the one goal that we set out with, the things that we agreed on to accomplish when the objective kicked off, those once ago, have more or less stayed the same. We still want to create and maintain websites that keep up with the modern technologies as well as their user-friendly, both in their look and feel, with the involvement of easy navigation and logical arrangement of elements. For prospective new contributors, we want to make it simple enough to locate the information that they're looking for in order to get started with contributing to the project. Once we are done with implementing all these things in the prominent websites which have a better visibility, we would use that as a reference for other federal websites that help in providing other offerings such as pins, alternative downloads, et cetera. Then we would connect with all the offerings like I mentioned, additions, versions of Adobe Linux, and we'd make sure that these are uniformly visible and accessible, and it should not be like that that a certain spin is left out just because it's not visible enough on our websites. Now, I will pass it on to my friend here who will let you in on the things that we have been working on as a team. Unwal from ODU. Thank you so much. So I'm going to have to talk about the team updates we had, and this is how our magic and dreams is working on. In this stage, we had some strategies and approaches based on our project, and of course, we would like to talk about how the things works and how the things has been done. So we, of course, developing a proof of concept as always, then if this is going to be successful, we always go to the larger website and we always take some feedbacks from others and we, of course, get consulted to stakeholders and get their feedback and ask them some of the questions to our users and contributors in the Rampa Fedora. And based on that, we discovered some new possibilities, maybe their ideas and whoever, everyone's ideas, of course, will come to an open. And based on that, we will improve our websites and our ideas as well. And I would like to talk about in this event, which is going to be, of course, going to be focused on the further websites. So we already work on the contribution documentation to better suit. And of course, we had some more documentation on Git and Postman section with the details as well. And then this is a little bit of a CI section and some other folks but knows better than me and I'm just trusting them their information. And they, of course, build and deploy and CI testings and where once the pull request happened on the website, which is amazing, now we can taste our website, each pull request and see what's going on or good or bad, which is nicer. And of course, addressing them, it's also a nice feature that we have. Of course, we worked on our system and our website interactive stuff has been done. Also, rephrasing picture changing the images and all those other backend and front end works also has been done as well in our websites. Also, I would like to focus on that, which is one of our important pieces in Fedora, which is going to be easy fix. And we started a while ago about revamping and changing the easy fix to make it much more nicer and modern to in our new and with also cooperate with our new logo to make it awesome. Of course, we made some discussion with between websites team and also mind-shifting, which is including myself in there. And then we talk about how do we make it better and spread the world. Basically, we would like to discuss how is it going to be useful for our contributors, which is we got some pretty amazing results based on that. And then we worked on that design very extensively. And based on that design, we have now better looks. And once we are finished and all things are ready, we're going to publish it. And hopefully our users going to be also newcomers and the contributors going to be definitely going to love it, hopefully. In the back ends, we did some Python changes, which is just for make it easier on the deployment. And that's very important on a couple of cases like packaging for something for Python in Fedora infrastructure. And then in the website section, we add some new API and of course getting our pictures with LibraVatar and of course, don't forget that. Also our post information based on what is required because we wanna make sure that person open the fixes, accessible from everywhere. And then we would like to discover the possibilities to do our contributors and newcomers as well. So they can find that people slash person, which is very important. Another thing is we have meetings in around the Fedora so many times as all so many folks around here or the knows about it. And the people doesn't know, most is are basically when we did a Fedora meeting in IRC or metrics, this topic today is mostly they're holding in metrics slash IRC together because thanks for the bridge. And when the meetings happened, we recorded that meeting and publicly shared it into our Fedora mode website, which is it's basically holding all the meetings and the discussions we did in Fedora and based on Fedora topics. And also based on that changes, we did some extremely a lot of UI changes and fast search results and on the front end, which is it's basically using a cyclones JavaScript changes and definitely a quicker search and faster indexing. Most of the work is done on the, on the front end and the JavaScript section to make it much more nicer. And maybe after the, after the presentation, I can maybe show you some quick demo behind it to in order to show how it looks like right now. Hopefully if it doesn't, yeah, he is okay with that. So then I come to the back end section. We have of course some same changes what we did for the previous one to make it, of course much more compatible with our RPM packaging on Fedora and set up Python tools for easy deployment. And some quality of life fixes is not so much of changes on the backend because backend was still strong, but we want to make sure that using some modern Python abilities to make it much more flexible and nicer. But it's pretty much working at the same on the backend mostly, but on the front end and the JavaScript power we did much more work on that section as well. And then other than that, if you want to join and getting involved, that's Akash perspective. So I'm waiting to him to please. Thanks for that. So we'll be dropping links to the metrics channel which is based on IRC over here. Yeah, thanks for the links. You have pasted them all at once, which is great. So this is the channel that we usually have our conversations with. You'd find us most of the times, but you know, time zones. So feel free to drop the links and the messages and we'll reach out to you in a while. Then the repositories that we work on are the things that are marked there as well. There's the more repository that he has not, but here it goes. And the documentation for the objective for better understanding what we do and the way that we do things is linked there as well as the mailing list if you want things to stay on record. So this is how you can get involved with us and let me see if I have the upstream copy of mode cloned to my remote local directory. In the meanwhile, folks, please feel free to ask your questions if you have some in the Q&A tab. Onurad, there's a question about you taking over Fedora. Yeah, I was going to keep it for the last. Right, right. That's a good question, David. Basically, we appreciate contributions in all the size but to be honest, the past that need most contributions are different and we have infrastructure folks around us who would help us into deploying stuff or working on a backend but in front end we're kind of lacking. So we try to make use of the defaults that most CSS frameworks gave us with and add a little fedorable touch to it if you know what I'm saying but that's pretty much what we can do. Also, Fedora Bootstrap is something that has not been yet updated from 4.3.1. That's a bootstrap version it's based on. It would be great if we have someone who is adept on front end to maybe work on bootstrap 5.0 and amp it up to become a bit more fedorable. So yeah, front end if you ask one area which is requiring most contributions right now. Onurad, please go ahead. Yeah, as you said as well, backend is pretty much fine right now. We already get covered at most of the stuff. So most of the things we change is most of the time it's just front end changes to better for our users and contributors. So that's very important section. It's a Matthew asks, when does the objective conclude? We set some outcomes for the objective when we started off and we decided right now when we evaluated ourselves on the basis of the model that we created at that time that a lot of it has been done. Well, a lot of it has not been even yet started. So those outcomes can be one of the parameters which we can evaluate ourselves. And then again, we have our bi-weekly meetings with Marie, Justin, Rami and myself where we evaluate on what the team is doing and is it actually going towards the goal that we want to head to. And also we can say that since the improvements are getting in track and getting to be online soon and also we had the kickoff happens on the main website. So I think we can say it's gonna be successful hopefully. This is what I believe mostly because we saw the progress, we saw the movement but the part of the time it's sometimes depend on the contributor in a person but I believe that after we did the big chunk of our main website and the site website as well I think we can call that as a success as at least for a stage one or just a complete job but it's definitely going to be successful which is from this perspective and on what I believe as well because I saw the changes. Honorabh, would you like to stop sharing the screen? I'd share mine and that back and share, you know how. Yeah, sure, sure, sure. I'm sort of into my sharing. Appreciate it. Right, please let me know if when the screen is visible. For me too. Yeah, so fragment, it's just a sign on info mode it's just upstream, the thing that we're working on. As soon as this becomes remotely stable we're sure to push this towards the staging and we'll check on the changes we'll make sure that the community gets a look on what exactly that we have been working on. But for now, what we try to work on is to make it as mobile first as possible. So, you know, let me give an example. These are the meetings that are, let me take an example of the most active meeting places federal meeting one, two, three. I'll just take a random three, right? And this one release engineering, right? So it's just the same plain old mode for the most parts. So you would not feel alienated when you start using the new one, but with a few more quality of life changes. So suppose if I were to go to a, well, let me head back to the summary page. Geez, there has not been, oh, there is, right? So in the previous mode you would not have seen something of this sort. It would take you to that place but we added this little highlighting part. That, and when I reduced the width to something that a phone would have, this would occupy the entire width. Thus making it feel like as if it has been written, especially for a phone. The searching algorithms has been worked upon as well, which means that you would get your meetings, at least the ones that you're looking for in a much faster way. Let me open up a random meeting, just for an example. And there you go. I get the highlighting as well. I think that NAPA is something that we can work upon. Maybe add a few more stuff, but folks, please feel free to let us know in the chat section if there's something that you want us to implement over here. This is still a work in progress. I might give some one idea. It's gonna be front end idea, but. Sure, go ahead. Black team for Alice. Oh, okay. Sure. We still need to get in touch with the design team. Yeah, yeah. Get them on board with this, but yeah, there's something that we're interested in. At least for, not for an entire website, but at least for the reading the logs. It could be only that section could be dark. I mean, the entire website can stay with. When we look at the logs and the search, if there's become black, that will be nice because people doesn't like so many shine things in their eyes. I just see from the chat getting some support from over here. Oh, are we? Yeah, even Franco said plus one for black team. So I'm not gonna argue with him. Totally. I'd be finding the corresponding meeting, the sweet message and replying after it's done. Oh yeah, I mean, we are working on a feature which involves WebSockets Matthew. So the way it works is it interacts with federal messaging. And as soon as it gets to know the event of finishing of a certain meeting from data normal data gripper, it immediately lets you know with the use of a toast message on the site. So you get to know that, yeah, this meeting has ended. And yeah, Franco, black team. I get a plus one from you. That means this is something that we would want to consider. Murray has a question. When do you think the team will have a capacity to work on the federal craft project? I'll take this one. Sure, go ahead. I already working on that behind the scene. I would like to show it after I get some certain point, but Murray, I need your help on some sections on the design perspective for abilities and search, but my work on the front end and the back end is almost done. So we can start replacing the old one with the new one and creating new graphics for small sections around the other websites if you want to use it anywhere you'd like to see it. Because I like to see that moving graphs and much more interactive stuff on that too as well. Yes, Murray, I would love to do that as well. We need you. Actually, I specifically need you. Thank you so much. All right, let me stop sharing my screen. Luna has a question about, yeah, favorite meetings and associating it with a certain account so that whenever they log in, they would be able to see the meetings that they're interested on. It's an interesting feature. We'll write it down somewhere and maybe think if it is something that we want to implement. No, of course. Posting in the discuss could be a nice idea. I automatically, which is, it's a possibility I'm just gonna go argue with that, but I really want to posting the entire log, Matthew, or just like posting some summary. Okay, so because, yeah, and that would be nice because we don't wanna place so much information and it just makes a little bit too much for overwhelming. So yeah, summary would be a nice idea. Yes, exactly. We'd hope that I'll put the message first directly into the normal data group. Yeah. The normal data group is basically a static piece to get to know about things and creating about things that exist already. So yeah, makes sense. Yes, Matthew. Exactly. I was thinking the same thing. Summary and the bottom line is going to be the following for the log, of course. Take for instance, if we take a meeting from federal classroom and yeah, so if we have this summary right here, it has a link to full logs. That's the reason why I did not even consider adding a full logs button, a dedicated one, to say the least at the top because, well, this gets the job done. Okay, I think I'm going to sneak into the discussion API and log in and send some stuff and things over there and we did the permission. Matthew, if you have an access, please provide us. Oh, what is that? I'll open up as a tab in my browser and I'll take a look at it shortly. But yeah, talking about the question about my mustache, you're not likely to see me without mustache like anytime soon because if you see me without mustache then that's not me, that's just an imposter. Just grab hold of that person and throw that person away. That's not me. If you remove our mustachees, we're going to be basically imposter in the game session, right? Everything is possible, guys. Yes, we have among us session in like an hour from now? No, two hours, there's some talks between us but I would like to see everyone in that game session today because that's what we are here as well because we would like to have talk with our friends and have some fun, of course, in our nicely weekend. Be sure to have among us install on your devices even if you're not able to install it on Fedora, that's totally fine. It's freely available on Android as well as iOS. So see you folks over there. Okay, so, oh, Akash, we got the API key. Awesome. I'm going to finish that then. Yep, yep, let's go. All right, so let me do my ending as well to be, you know, I work on this Panda, you know, for some individual asked for some Panda and logo on the middle of it. So I did some work on it. Hopefully she will approve. So I would like to say thank you everyone for their presences and I hope you'll enjoy our talks. And don't worry Mary, you already understand what you meant. So I hope you enjoyed and if there is any other questions, we still have some couple more minutes. And other than that, thank you so much. I hope you enjoyed in this lovely meeting in the weekend.