 team okay? Yeah you don't know yeah sorry in a couple minutes please. Thanks everyone for the patience. We appreciate it. Today we're here to talk about Fedora badges 2.0 and I don't know who's here in the crowd so I will do a short introduction. I am Marie Norden and I have been working on Fedora badges for over 10 years now last month so that's pretty cool. Also involved in some other teams in Fedora and previous Fedora community action and impact coordinator and currently working for the Python software foundation as a community communications manager. So I'm going to pass it to Emma to introduce herself. Thanks Marie. Yes my name's Emma Kidney. I'm on the Fedora design team as well as the community design team that's within Red Hat and I've been part of that since 2021 so I'll pass it over to Akash. Thanks Emma. I've been contributing to Fedora community for a while now. Name's Akash Deepthir and right now I contribute to both Fedora infrastructure as well as I'm a part of that team called the community platform engineering team. All right so over to you again Marie. Cool so I'm just going to do an introduction here about what we're sharing today and what Fedora badges 2.0 is all about so as I mentioned I've been working on Fedora badges for over 10 years so it's that old plus some and it's showing its age. If you've been on badges that Fedora project or you know it's showing its age a little bit and if you've interacted with the system you know that some of the badges don't work as well as they used to because different pieces of the infrastructure behind how badges work have changed both on the Fedora side and the you know how some of the badges was built some of that technology has changed too so a little bit over a year ago we had some folks from CPE and community members say you know if we want to revive this what do we need to do to make that happen um so one of the first things we did was like gather some raw raw support about it and gather some testimonials about why we love badges as community why it's important to us what kind of impact it's had on our lives and our lives in Fedora and you can actually find that discussion thread on discuss discussion.fpo and it's got some really nice stories so definitely check that out so once we're like okay we want to do this we got a group of people together uh to kind of plan and talk about what we needed to do so we realized we needed three things which would be a new back end very importantly a new front end because the front end is looking outdated and Fedora's aesthetic has grown and how we look at websites and interact with them has also grown and also new art there's tons of beautiful art there but some of it was made over 10 years ago so you know the badges aesthetic has grown we wanted to bring that kind of up to speed so currently we're meeting once a month on a call and we have two element chats so I am going to plug right now a request for more volunteers and people to join in because we really do need this to be a community effort to get it back up and running and part of what we're doing to make that happen is modernizing the whole system so that it's more interesting for people to work on you know everything from the back end the front end and the art so you can join us on a monthly call and we have two channels that you can come and introduce yourself and get involved so we have our usual badges channel that's been around for ages we also have a badges development channel so that we can keep that conversation focused and you know folks can go back and forth about the development as much as needed without kind of clogging up that main channel where all of us are working so that's a little bit about who but when where and why we're doing this revamp and I think I'm going to pass it now to Akash to get into the back end thanks Marie right let's move on to the next slide so Tari was the front end as well as the back and then the application structure for the Fedora badges it was basically a web application or well still is because it's still used in the community that interacted both with the database as well as a trend at the front end now the problem with Tari was that you know it was a website and we wanted it to act like a web application and in 2023 I just looked it up real quick 95.8 person people use their websites web applications from their mobile phone so it was time that we optimize our things to be a lot more mobile first responsive so you know with time over the course of multiple years what we investigated and found out that you know APIs are the way forward to talk with services you know instead of sending SPB requests which are a part of a website and let that website refresh every single time you do anything of that kind it's better to use something like an API and that way your website will be like a web application interactivity would increase so that is the simplified access part the next is the faster back end and with time we have gotten a lot many technologies a lot many things that are much better capable of using the system resources that they're provided with on rather mentioned off one of those frameworks fast API which is capable of running asynchronous code thereby responding to multiples like millions of thousands of requests and the same resources that any other synchronous frameworks would be capable of so a faster back end has become a need of the other then of course the better interaction like I said before we need something to be like an application while not working as hard to make one application then put it to some other thing well why not some make something that's based on the technology so that we can create it once and use it everywhere else granted there are problems with that lots of it but we can definitely onboard as many people as we want to irrespective of the platform that they're making use of with using the technologies and finally with the use of efficient databases instead of running while SQL queries by that you know just like that we use things like abstraction like SQL alchemy and there are the libraries that let you write phytonic code while you're interacting with things like a database so that definitely helps to reduce that curve of learning and gets people started really quickly with contributing the next slide please sorry one second oh i'll get i'll get we just got a glimpse of one of your next talks so that's a good thing yeah oh god i couldn't look for that though so attendees if you watch that you should definitely turn up in like an hour from now when Emma's talk is there i think it's an odd 30 from now so be sure to be there it's one of the good ones right yeah so now that we know about the state of the baddest technology stack right now we know it for the fact that the revamping is required and we would love to use something that's already there and try to fix things up but we can't quite and here are the reasons here are the change requirements from the service that would not let us do just that so we're trying to make an open ecosystem so as to make sure that we have both an API as well as a frontend the frontend again being a reference frontend that people can make use of but if they want to well write client application in frameworks like q.gtk that accesses our api that's perfectly fine they totally can't do that so we really want to keep an open ecosystem so as to make sure that people can contribute not in the way they want but also in the tools that they want to create with these things and also the boosted efficiency with the use of asynchronous frameworks with you know abstraction layers so as to make sure that the programmers are spending more times writing solutions and not while creating wheels for the car that they want to drive then the third thing is of course making our websites look more akin to applications and like one of the folks in the common section mentioned making things mobile first but not forgetting desktop users at the same time so definitely that and finally lapping every single thing that I just mentioned in an inclusive process that is welcoming to everyone irrespective of how experienced you are in python or in java script or in frameworks in the frontend side of things we don't care we'll have a documentation that's going to get you started with contributing in no time and there's definitely something for everyone next slide please right so the reason why we don't want to revitalize what's already there so of course it makes use of an aging technology called pyrimid for which documentation is there but the community is not so we really want to use something like fast api that's a lot more current something that people can contribute to and also mention off in the resume so it's a win-win situation for every single one then of course the prolonging activity of the code base which led to a lot of test cases failing the ci workflows topping to work and at this point in time it's better off to start with something new rather than trying to learn an old code base that might not be worth it and then the experience acquired now if you were someone who wrote it back then it would feel like a natural thing to you but for everyone else who is learning it into 2023 a technology that was 1110 years back might not only be heightening up the barrier of entry but it also won't be worth contributing to and finally scarce documentation with repository spread in pager and on github and some on githlab as well at the time of speaking this it's very difficult for a beginner to get started contributing so definitely no revitalizing and more revamping the next slide please and yeah i'm going to get quickly over with this because there's a bunch of other stuff we talked about in a design side of things as well as the front end side of things as well but this is how the skeleton looks like take a screenshot but if you don't want to take a screenshot the next slide would send you the information about the documentation so the next slide please and yeah so this is the documentation where you can find all about the investigations run by the fedora infrastructure as well as the community platform engineering team about this project take a look at that and here's the project repository we accept issues pull requests any contributions for that matter and with that i'm going to pass it over to murray over to me i think oh yeah over to emma sorry yeah my refined yeah so i'll just quickly go over it's the ui ux side of things but i guess um the main question is why revamp like murray said at the start the current look is a bit outdated and it's also old branding and as you can see up the top here you can see the old fedora logo the old door font the old door blue and the accessibility to information is a bit limited and it would also just be nice to align it with other fedora branded websites and applications like fedora docs fedora discussions and and the newly revamped fedora website as well um community feedback so last month i would have sent out a fedora badges front end questionnaire on fedora discussions i would have liked to have a nice little infographic here to explain the information that was that came from that questionnaire but unfortunately i did not get the time to tell that this week so um but i will say there was a satisfactory amount of participation on that questionnaire and what i can do is as soon as i have that ready i'm going to share it up on fedora discussions because there is um some valuable feedback there and some nice insights to things and the user flow so this is a visual representation of how the user moves through a website so this is based on the current fedora badges application at the moment and this is to just kind of help you see all the different paths to kind of get all the different pages you see up the key here you know the boxes page the link then as well and an action so in our case it's mainly login and the admin pages are kind of in this white gray color and not everyone has access to these obviously it's just people with admin rights um but they do have quite a lot of more pages to see um the low fight wireframe so low fight low fidelity and they're just basic wireframes that outline blueprints for web pages so this is just to give everyone kind of a general look and feel of what the fedora badges could look like um yeah there's going to be no major changes to the architecture um from my side anyway um well i would have liked from this was to gather kind of community feedback regarding the current direction i know obviously these are very kind of rough at the minute they're not that refined um but it's to just kind of give you that general kind of gist of where it could go and what i can do is i can just paste in the discussion post here um if people want to give any feedback they can and then onto the high fly wireframes so high fidelity um are just a bit more complete in their visual representation so a bit more refined um kind of closer to what the mock-ups would actually look like they're still in the early stages and what i can do is um once the mock-ups are complete i can post them on discussions um for feedback and i can work with the community until we are satisfied with the outcome and this is kind of a similar approach i took with the fedora website revamp if anyone remembers um or was on fedora discussions then you would have seen i um every time i was done with a particular page i would have posted it up on discussions with my justification for you know why things looked the way they did and then the community could give me feedback on what they liked or didn't like or what they think i should change and so on so it is it is an involved process with community i think as well um next steps so as i said the mock-ups will be posted as they are done um and i will work with community until mostly happy with the new look obviously we cannot please everyone but i will try um to get as close as i can so keep your eyes peeled for that um that being said this will take some time i'm the only one working on the ui ux at the moment um so it will take some time for me to post some hopefully i'll have something before christmas um and if you want to get involved feel free to just reach out to me and we can get you started um so yeah i'm passing over to marie then for the graphic design side of things yeah i think that's a pretty exciting part to contribute get volunteers for as well um putting a new fresh paint uh coat of paint on fedora badges would be really nice for someone's portfolio so i'm going to talk about the graphic design the badge art part of the revamp so you can go to the next slide so you know why update the art right i talked a little bit about it at the beginning but basically graphic design standards have changed over the years since we first kicked off badges fedora's brand has changed and evolved and the people contributing to the project have also changed um i'm still here but there's lots of newcomers who want to do new things try new things so these are all reasons to update the art we've also learned things like about what we want the standard to be um we've also learned that you know really diving into that old template if you're vector artists you might be a little bit sad about some of the choices that were made in there so we've made that now very clean and fresh um and like i said the badge aesthetic has grown over the years we can go to the next slide so last summer i mentored an outreach intern nakita uh hopefully maybe you've met her at last year's flock um and she worked on fedora badges so she took our template and modernized it so on the right you can see the new version of what our fedora badges template looks like so it's more focused on the graphic it's simpler it's also compatible with dark mode um and it's nice and visually balanced we can go to the next slide um she also started nakita also started a new style guide to kind of go with this updated template and all the learnings that we have made over the last 10 years so this is an example page we can go to the next slide and this summer i mentored two interns oh i also co-mentored with smiracle um uh chris and roland who did an amazing job all the interns doing the amazing job but they did so much work on bringing the old artwork into the new templates that nakita created last summer so here's an example of a variety of the badges you're probably familiar with them and how they look now in the new template so we won't be implementing these in the old website because it would kind of uh we've made some changes to the padding around them and it would kind of overtake the space on the current website um so we're waiting to implement these until we get the new website up um but as you can see they're modern and they're gorgeous and i love them let's go to the next so just going to talk very quickly about what's left to do i'd love to have a chance to get some of the q and a so excuse me if i rush through some of this so chris and roland got through about half of the badges we have around 600 badges actually probably a little bit more now so they got through 300 badges in three months which is monumental but there's still about 300 to do so we need badge artists as well to get through this but we're talking about putting together some design sprints to kind of really make it happen um we have some new things to put into the style guide that nakita started last summer because chris and roland learned things while implementing into the new style guide um and there's some small design improvements so myself and smira are working through the changes there and which we hope to have it done in the next month or two next slide please uh once the style guide is finished and the badge art is complete and implemented we will then update all of the documentation updating it right now doesn't make sense because we're still using the old system and all of the documentation we have up is still valid for that old system um and then implementation will work in sync with other folks on the team to make sure that you know the specifications and how we put those templates together will work with the new website next slide and that's it so we have three minutes for questions hopefully we can maybe go like two minutes over um just so we can get through some of these uh I see that we do have some replies in here but just for the video's sake I think we could quickly respond to them so the first one is would the 2.0 system have badge series for example sequentially ordered series of badge earned in an order do you want to take that akash yep so uh in short yes we will we call them collections over here not series because um well some badges are not in series so let's just say if you voted for fidel in x35 and then you were busy so you could not vote for the coming two times and then you come back for fidel in x38 then uh these can be in a collection while series can be like long life to pagore if you're making multiple comments to pagore it's quite likely that you would be able to reach the hundred mark only if you have made the 15th comment so that would be a series but the other thing will be a set so we just call them collections in the newer system over to you Marie cool all right next question would historical data i.e. people's existing badges and who has earned them be preserved yes they will be and we're trying to you know reuse the older data set and kind of transform it to a newer data form where a bunch of things which were specifically for open badges won't be required anymore so of course we'll have them we'll be trying to make these uh databases a lot more optimal so let's make sure that we keep stuff that's necessary and nothing more over awesome i think the last one might be for you too so just stay with me uh is there work going into the back end side to eclipse or solve the currently broken badges right so a bunch of badges are broken right now which has has a lot to do with the fed message compatibility layer that we make use of right now uh badges is one of the last uh applications that makes use of fed uh fed message we are using fedora messaging in most of the tools like at at this point almost all the tools but uh we need to fix badges first not to be able to make it use fedora messaging and while we are not using it right now or while we're not working on it right now but we definitely plan to do that with the consumer project and i have sent a link over there if you take a look at that it's definitely in the pipeline it's just not something that we're working on right now thank you akash so i don't see any more questions in the q&a so i'm going to take this last like 30 seconds to say please come join us please keep this beautiful wonderful nostalgic and hopefully now modern two um project alive for fedora like we don't don't want to lose this every day that goes by the old system breaks down a little bit more we get more tickets opened with people saying i didn't get this badge or didn't get that badge and we want that for people and if we can make this happen we'd love to do even more with it we'd love to like get badges for some of the areas of fedora that don't have them yet um we'd love to be able to you know rework some of the how how the events badges work versus community and there's lots of things that we could do but we really need folks to pitch in and i know people are always asking for contributions but this is a really it's at the heart of fedora and we need folks to join in to make it happen so thanks for listening thanks for being here we really appreciate you and we hope that you enjoyed our presentation bye folks hi everyone