 Hello everyone and welcome to our talk about Federal websites and apps feedback objective updates. This is a federal council objective about planning, designing and engineering our websites and web applications which happen to be our base to the entire world. I'm Akash Tiidhar. I work with the Red Hat Committee of platform engineering team as a day job doing things related to initiatives, infrastructure and release engineering. In nighttime, I don a vigilante mask and I go out there to beat objectively for this team as well as an objective representative in the federal council. I'll now hand it over to Graham for him to tell a bit about himself. Cool. Thanks for that Akash Deep. Give me a thumbs up if you can hear me. Yep. Yep. Cool. Sorry. First time presenting through hop in. So a bit of a newbie here. So bear with. Thanks very much. So yes, my name is Graham White. It's following Akash Deep. So by day, I work for IBM. I'm a research employee. And I guess for the purposes of this talk, that's not so interesting. So I'll talk a little bit more about what I'm doing inside Fedora. So I guess most of what I do Fedora-wise is also actually inside IBM. So I lead a community of Flora users within the firewalls of IBM for people running the desktop. But more recently got involved as part of Ben Cotton's program management team. And through that getting involved with the websites and apps team as well. So happy to be here in sort of those two dual roles today. So Akash Deep and I are going to split this presentation deck between the two of us. So I'm just going to give you a little bit of an intro and then I'll hand back to Akash Deep. So first of all, who we are, I guess one of the things to say in this first couple of slides is that it's kind of really difficult to name everybody, right? The community is quite big. So apologies if you've been left out, but we've tried to sort of pick some of the main names that have been involved. Certainly in the period that I've been getting involved in this over the last few months. So my involvement started back in about December, I think, Akash Deep, to try and sort of bring some of the program management side of things to the websites and apps team in general. Akash Deep's obviously been involved for somewhat longer than that as part of some of the objectives that we'll talk about. And we've been getting some great support from Marie and Vipple along the way as well. We are roughly split into three sub teams. The lines, I guess, are possibly slightly blurred between these teams, but these are sort of the broad kind of pillars that we are operating within the overall websites and apps team. So the rest of the deck is actually going to talk you through these teams and what we're doing in each of them. So we've got the engineering team and the stakeholders team that Akash Deep is going to cover in a little bit more detail. We've got points of contact for those from Francois on the engineering side and Pavel and Timothy on the stakeholders team. And we've also got the objective co-leads team, which is the one that I sort of originally joined for the management side as well as the engineering side as well. So that's led by myself and Akash Deep overall. So hopefully as we go through the deck, we will sort of give you an idea about what these teams are doing and how they integrate with each other in a little bit more detail. But obviously, please do far away if you've got any questions about any of this and we'll see if we can get to those at the end. We've got a sort of small set of slides here, so we'll have plenty of time for questions before the time we finish. So actually, back over to you. Thank you, Graeme. I'll go to the next slide. Let us talk a bit about the engineering sub team. This team is responsible for developing and maintaining websites and applications. Performing UI UX reviews and organizing meetings every week to discuss about these stuffs. And we also met a new contributor so that it's not just us who are doing these stuff, but we also find people who would continue on from wherever we leave off. So what we have been up to, we have been discussing our plans about providing platforms for new people to do so as well, be it Fedora Chat or Jitsi, a lot. As soon as new releases come out, what we do is we check our localizations, make sure that it is up to date. We update the links and digest or disk images, our provisions of Fedora Linux, mark and remove beta releases as and when they are needed. And then finally, about on-molding contributors. We make sure that they feel welcome to stay back and to contribute. They can begin with starting providing suggestions, and then when they're comfortable, they can actually start writing some code or some designing mock-ups. There are a lot of ways to contribute to the Fedora websites and apps team. Moving on to the next slide. The things that we have been up to also include on-molding contributors like I told you before, and talking about on-molding contributors, what we have been doing is some mentorship. Over the course of the last one year, the team has mentored two outreach interns to help build and maintain websites and applications. So I'm going to take this opportunity to thank Michael, Franshua, and Anurad for mentoring these interns. And thank you, Shubhangi and Ojong, who have been these interns who selected Fedora Project as a mentoring organization of their choice. And with continuous participation in every Fedora Linux project event and platform, now be it a release party or Nesfit Fedora, we have been trying to make sure that we are more and more visible to people. So our plans are continually communicated upon on discussions FPO. You can find them over there. And our updates are constantly updated on the COM blog. For a greater community, they would know what we are up to and they can totally reach out to us if they want to be a part of our team. Finally, we have been working towards revamping our applications. Now, talking about revamping our application, I have something that I would like to share with you folks. So this is the most teaching that we have been working on for a bit now. It's a bit rough around the edges, so handle it gently, but it's something that's coming very soon. And, well, did I tell you about the dark mode that it has? If you take a look. Moving on to the next slide, please. Right, so what do we plan to do next? Of course, all the things that we have been up to before, we plan to do more of those stuff. Probably add some more stuff on the list, but more specifically, we want to continue maintaining our projects. Websites, applications, we want to maintain them in the state that they are in. And when time comes, we would want to update them. Then improving our response time for our tickets. Websites being our phase to Fedor Linux is something that we should actively maintain and we think that we could do a bit better in improving our response times to the tickets that people create. Finally, we would receive our mentorship efforts to onboarding more contributors, making sure that they know where to reach out to, be it people or documentation. Right, go to the next slide. So this is the QR code that you can scan. I'm going to copy paste a link to the channel that the website's engineering team makes use of. Hopefully, if you could open it up and join us over there, we'd love to know what you think about and what ideas that you have that you want to share with us. Moving on to our next section. Let's talk a bit about the website's revamped stakeholder's team. This team is responsible for looking into the designing of aesthetics, making a style guide for our ecosystem applications and websites trying to make sure that they look consistent, planning the websites and application strategy and centering on the text tag that people would want to make use of for implementing all of these stuff. Moving on to the next slide. So what has this team been up to? Like the engineering team, this team has been active and having their own sets of meetings and the chat channels have been active as well to discuss stuff. Led by Maureen Duffy, we have had many interns from Red Hat to help us with mock-ups and all the shiny stuff that they have been coming up with for our website's reboot. Now, these mock-ups were something that we have been actively posting on discussions FPO, on Com blog, and we have been reaching out for reviews from people. And you can be sure as hell that those reviews have been worked upon. Moving on to the next slide. Right, so discussions to make sure that people know about what the team is up to and the designs. It's not just a survivorship bias of the people who are the part of the team, but we take into account the reviews out there from the entire community. The team has been instrumental in documenting what they do on these sites. And we have stakeholders from the workstation group, design team, ADE-6, Neuro Fedora, and from many other sites who have been coming together and providing their views on these mock-ups before they go out in public. And just like an engineering team, we represent TAPS-UP team in federal project events. We then release parties on Nest. We make sure that this team has an active representation as well. And finally, moving on to the things that we plan to do next for the team. Right, so it's as simple as three things. It's kind of a marketing gimmick right now, right? If you want to make something simple, we just tell that it's three easy steps. So talking about three easy things, we want to make sure that we have more mock-ups. We have more discussions on these mock-ups so that we know what exactly needs to be implemented and more improvements on the discussions that were done on the mock-ups. It sounds easy to start with, but I know the kind of effort that the revamp team has put in to making these things happen. So who goes to them? Moving on to the next slide. So here's the QR code that you can scan to be the part of the revamp team. It's a stakeholder team where people from a variety of six sub-projects, sub-teams come together to express their views. If you want to take a look at what the UI UX team comes up with, it will be a part of it. I'm going to pop a piece of the link to it in the chat section right now. For the next sections, I'm going to pass it back to Graham. Over to you. Great. Thanks for that, Akashity. So I'm just going to finish off with a little bit of a chat around the objective co-leads, and this is the third of the three teams that we introduced you to. So this team, as you can see here, is responsible really for sort of organizational responsibilities across both teams. So we try and sort of straddle, if you like, the two teams that Akashity just talked around. I was trying to sort of keep a handle on those two sub-teams. We also try and push forwards with some of the objectives that the co-leads teams originally set up for. So I'm conscious there are people on the call that have been involved in the objective of this than much longer than myself. But my understanding is that it was originally set up to try and revamp the entire sort of websites ecosystem and encourage more participation and get more people involved. So we are also sort of keeping an eye on those sorts of goals as well. So the things that we have been up to in this team, again, like all of the other sub-teams, we have been participating in discussions. So we have our own matrix channel where people can reach out to us from a sort of overall leadership and program management perspective for this kind of whole websites and apps area. We also sort of, we say here, sort of introspect the team's current state. So that's sort of a posh way I guess of saying, sort of keeping an eye on what's going on, making sure that the outputs of the tasks are conforming to the objectives that we've set out and the teams are continuing to have and make an impact, to basically sort of drive us all forward and point us all in the same direction. So obviously we're all sort of collaborating properly. Obviously then we collaborate with those sub-teams as well. I think certainly most of the co-leads team, certainly the current co-leads team are also involved in the other two teams that actually just talked through. So we're sort of integrated members across both of those teams, but sort of providing that kind of high level leadership layer as well. So it keeps us all sort of almost straight and narrow for making sure all the teams are all together. So what we've been up to, we've got quite a few different actions that we have been looking at. The main one that I've sort of screened here is the project inventory and this is something that I started looking at when I joined the team back in December. So thinking about it from a pure websites and apps perspective and the team that are looking after the websites and apps, my immediate question was, okay so what are these websites and apps then and which ones of those are we looking after? And that sort of led to the idea of creating an inventory which I've started here. So this is very much early days work in progress. There's sort of part of the screenshot that I've pasted here from a Google spreadsheet. So we've got something in the order of 40, 41 websites throughout the Fedora ecosystem that as part of that sort of program management role, I'd like to be able to review both in terms of necessity content who they're aimed at and then start to fill out some of the other fields you can see on the table in terms of, okay so if someone wants to contribute to this, how do they do it? Where do they go find the source code? Who might they talk to in order to be able to contribute and get up to speed? And so this is, let's say very much work in progress. If you want to get involved in this kind of effort, please do get in touch with me with the idea that at some point we'll produce some piece of documentation or a web page that summarizes this in a way that makes it easier and hopefully reduces the barrier to entry for people getting involved in the websites and apps community and specifically around certain websites that they might want to target if there's a bug or a new piece of content or something that they think they want to add or update. Okay, so the second thing was designing the infographic. So we've got Marie to thank for that. That was something that we published on the COM blog a few weeks back which really sort of sets out those sort of three colors that we've talked about for the three teams and what each of those teams is working on. So please go look out the COM blog for that. That was sort of a really nice infographic that we can thank Marie for. So yeah, thanks very much for that. And again, like with all of the other teams that we've talked about, we are trying to make ourselves more visible and represent ourselves within the community. So, you know, here we are at the Federal 36 Release Party talking about what the objective COVID's team is doing as well as the other teams as well. So planning and looking for what we are thinking about going forward into the future is I guess it's sort of almost more of the same in terms of continuing to implement the objectives that we've set out and we'll continue to evaluate what those objectives are. I guess at some point we may decide that they are complete just to go forward with the engineering side of things, but we'll also be keeping an eye on the overall kind of health of the team and the community to make sure that we're still trying to get people involved. Keep reducing that barrier to entry that I was talking about and make sure that it's easy to get involved, easy to contribute and people are willing, happy and engaged within this community. And the final one is that we've been looking at how to promote and incentivize that participation as well. So we've had various different discussions particularly around things like adding a large program and making sure that people again are involved in that sort of happy and incentivized community that there's some form of reward for that participation as well. So we also have a QR code actually if I'm going to struggle to cut and paste this out of full screen mode so if you'd be so kind as to put a link to this into the chat as well that would be great. So please do come on and join us for the discussions in this channel as well. Okay, so there's one last thing that we sort of didn't advertise if we're going to talk about. We've got a slide for which is to say that we are sort of actively looking at and reviewing and updating the documentation for this. So that's also part of that effort towards making it easier to get involved, reducing those barriers to entry, making sure that the operation of the team is documented. So what we do, how we do it, when we're having meetings, where the meeting minutes are, all that kind of stuff but also the other side of how do I get involved in maintaining or updating your website, if there was a contributor that wanted to try and get involved to help with any of that sort of things as well. Okay, so that really concludes our talk and I guess Akashdeep, if you're ready, we can open up for questions. Yep, we do have one question from Edward. Edward asks if there is a roadmap for apps that will be affected or that you will take care of. We shouldn't be asking for stuff that are planned to be worked on, like the calendar and the ambassador's plan. Right, so the thing is we are deciding upon the basis of usage. If the application is more sought upon, say for instance, most of the meetings that happen are on ISEs and on text. So it all made sense that we would want to revamp that application first before we move on to something else. So in the likes of that, we might want to consider revamping badness next. Yeah, I guess. There's probably something to say about the revamp effort here as well in terms of I think our near-term roadmap is to have the engineering team work in I guess you could it maintenance mode to keep the current websites and apps updated as they are running operational content updated where necessary. And when that revamp effort concludes to give us a new set of designs then the engineering team will be able to be set into action to implement those designs. And I think it's at that point we'll probably have a clearer roadmap about going forwards for what we're doing in terms of the implementations of the revamp designs that we've seen. And we can also have discussions at the co-leads level about whether we want to work on that from that perspective as well. Makes sense, yeah. Folks, 40 people to ask more questions if you have any. And like always, you can reach us out to the chat, the link of the chat section that we just shared with you folks, 40 people to join us and your perspectives. So we can get them actually, but either we're doing an amazing job and maybe he has any questions because we've answered them all or we've scared everyone off. Looks like it. Yep, I really hope that's not a case. Oh, so Edward happens to be working on a calendar application. Edward, please feel free to join us and we might be able to help you with that. And together, who knows we might be able to revamp that application next. Thank you so much for attending. Thank you for being here. We really appreciate it.