 Hi, I'm Joseph for the ones that don't know me. I work for Red Hat at Federa QA and we try to make Federa as great as possible and Sadly, our best colleague is not here because Adam Williamson, which you already know, I guess from the demo list is the robotic monkey that makes it all possible Anyway We don't only do release validation. We also try to Get people to join the awesome community help us with the testing hopefully getting joined into the whole process and maybe if we do our work right they will get hired by IBM now and That's why we're here like some of the work we do is engaging the community, especially high school and university students and we try to Give them work honestly because when we say hey, this is this awesome company Red Hat, which allows you to do open source You can do all some stuff in your free time You can get stuff on your resume and then you'll get hired probably if you're getting known and they ask wow That's okay. So weak. What what can we do? What can we do and? Then the hard part begins because as much as Federa has an awesome set of documentation put together Well by Adam mostly We I think we have problem because it's walls of text the text is awesome It's complete, but that's the problem right because the text is complete and you need to grasp it in the whole Eternity of the text and you need to understand all the details in order to participate efficiently and Camille and I and especially lucash my We decided that we want to lower the barrier and we want to Make it more accessible So the problem we came up to was the wall of text and the thing that we The control freaks that we are if you're a QA try to do things in the best way always like be the most correct be the most complete and That's awesome But it's also problem. So we sit down and we identify some of the processes that we always try to engage people with and it's stuff like Manual testing right because everybody can install Fedora and everybody can Put a mark in the wiki page everybody can submit a bug but Not that many people know what should you actually put in the bug report? So it's helpful and you don't get chased by the developers You don't get chased by the QA saying hey like nice work. We are grateful that you've came But like we need the details. We need to know how it happened We need to have some data and the people don't have it like they don't remember because they didn't know There's stuff like testing updates like you don't feel like submitting bug reports fair point You can only install Fedora. You can only use it and when you use it you can submit your Experience in a simple way you can use karma. It's easy, but you need to know it exists And it's written there like there's thousands of lines of text is written there But you necessarily don't need to Identify that this is the thing you can do easily so we had an idea originally we want to we Wanted to make this part of the federal hubs seemed like the best place, but sadly It is gone now, so We've spent a couple of days with JavaScript the new hotness and put together a webpage There's two facets to all of this the more important for now I think is this one, so these are the tasks that we identified that are easy to get people engaged that are easy that are easy to describe in their Fools maybe and That are specific to federal QA so release validation Testing body karma and then easy fixes because easy fixes is an awesome page, right? But for me personally, it likes something. It's just a list of projects It doesn't tell you much more than hey the project exists. And if you want to know more pink somebody and That's awesome, but you know still still something to be done there, so What we wanted to do is get the expert knowledge distill it and put it in a easy accessible list of steps, so Save it federal release validation. Is there somebody who haven't seen the testing matrices? All right Maybe the internet is working, so look me. So the thing is that we have this huge huge list of test cases basically and Each of the test cases well defined you can read how to test where to get all the stuff, but It's tons of data, right? And if you want to be the most helpful you probably want to Check something that's empty like this thing with the VNC because nobody tested it you want to Be helpful so you find something But it's still not the best way like the best test cases you could help us with are those which weren't tested for a long time and This is test for Rohit from couple of days ago, maybe a week, I think and there's a compose Every day sometimes and you shouldn't necessarily have to go through all the history and say, okay So I've seen that somebody tested this one today But it's the first one after a couple of months So maybe I should help there because it doesn't really have the coverage, but you don't necessarily have the data so This is where this thing gets to because we can Take the wiki pages we can parse them and we can get the get the knowledge from them So we say okay, so if you are interested in testing Cloud that means that you might be able to work with OpenStack You might be able to work with EC2, but you can also do it locally. Don't be scared So there's crossing the barrier and then you can see okay, so there's these test cases like I know They start up. I'm interested and you get a list and easily is that you can follow Maybe or you know some of these tests, but you forgot maybe you don't and if you need to know more it's just At your grasp like I don't know where to find an ISO for example, that's how see it like but sure What the environments can be because we have server we have Silver blue we have tons of stuff like there's tons of stuff to get and we try to like see Which is the best way? To approach it, which is the most helpful way for you to test and you get all the information And then again like if you found the back Not everybody knows what should they write into the back of the light so there's a list And that's what you like this is with all of the tasks that we With all of the tasks that we identified we try to distill it down We try to make the best decisions for the people because we did it bunch of times like every new person Ask the same questions right like it's always the same questions and we have it documented You all do I guess but then again It's like one of one bullet point in the middle of the other bullet points that are necessarily not the most important one So that's the idea we want to identify tasks that are accessible for beginners meaning that Most anybody should be able to do it with some skill set Like you cannot hop on Fixing vaccine kernel without some see-knowledge. I guess but then again there can be easy fix it in kernel Why not there there can be some but you should be able to say okay? I know see show me all the project that have some C sources and show me the descriptions on one place and give me The emails or the handles or the back pages and that's what we did with the easy easy fixes Like the page is awesome, but we wanted to enrich it and In the end like I'd like to get all the information directly into easy fixes right so it's not just in this one place, but it's more like a hub But I still didn't get to there, but I'll do it, but at the moment. That's the information we missed and we collected it we've shown it Here's where I want something from you honestly because with federal QA We did it and now we want to scale up and he'd like to hear from you. What's What are your pain points? Like what's the thing that you tell to each newcomer? so we can Distill it down we can show it and we can then say Okay, all the great people in the in the university who came to let's start with Fedora Let's start with Knicks. What can you do? Just hit this web page There's most of the information and if you're not sure just pick a random name because you want a program You were a program in C. Well, think someone you're not programming Python Just there's me like you will get to the person directly and now I guess it's a new like Where do you come from? What do you do and do you think you have something like that? Do you have something? Okay So I See this is a lot really interesting and awesome Project and and all the how it feels it's it's really nice But I see the problem of scalability here So people cannot come to you every time they want to add the information to the portal and something like you Should be there so the question is how to integrate it into other Interfaces we have so have you thought about like Creating a generic common easy fix for Fedora tag for example in Paguru So people all people across different projects can use it consistently in their issues tracker and you get kind of representation of it in this portal Okay, so if I understood correctly you are asking whether we can do Some kind of tagging on the same level as easy fixes I guess why not honestly like it just didn't occur to me It would be awesome the thing is what I love about easy fixes right is that anybody can just say hey This is a any easy fix there and the application. We will get it and we'll just show it like sure thing is we obviously do this an open source way and So All the data is shown. It's just grabbing some Jason's and showing them like we can easily you don't necessarily need to even like Go into the project you just if you have the right Jason the stuff will be shown But at the moment this is a proof of concern. So The idea is awesome my question would be like Do you see at the moment some specific let's say, I don't know what your risk is will be but let's say there's some speaking of the easy fixes, so let's say do you think there might be something like a an activity tech in a wiki for example that could be tagged with something like that or what was the idea like In wiki or in Paguru because like we have multiple Fedora projects Which are using Paguru to track via work and zone and also Tiger. Yes So we have several resources where people do they work and I think it's nice to be able to connect to those resources and get the information from there rather than expect developers to come to in our resource and market Yeah, exactly. So maybe Awesome, so maybe I wasn't really clear Might have been my English might have be that I slept for hours But thing is this is really just a front. Honestly, it collects data like it collects the data from easy fixes It collects the data from the web pages. So What I've seen with easy fixes, for example, there's tons of projects that are not programming right there's Project on a pecker pecker that is documentation for example like How there might be something like they might be outreach stuff like that. So There are also easy fix projects tagged in there But at the moment, I've missed them because I wasn't really sure how to Properly discern them, right? How do you tell an easy fix for a community issue from an easy fix? Kind of based on programming. So maybe we can add another tech like for the social activities, which would be awesome I think we need to like come up with some naming schema from maybe namespace for tags So that's all projects which share which are on pagore can share and then in this naming schema You can have like an easy fix prefix and then categorization like in which category this easy fix Belongs to so for non categorized. It will be just generic easy feet But if you want to be more specific, you can add something. So I think it's more about Discussing with owners of those pagore post what what the naming convention They are can agree with and then we just can implement this naming convention is a source of Data for for this service. Yeah, yeah, absolutely. Awesome idea. Thank you so So yeah, there's that like I love it because I've came to the same issue, right? Like I've seen easy fixes that are Documentation that are problems that cannot be solved by coding can especially those easy fix like the easy fix page Like I was talking about enhancing the experience like straight to the point because if I get to the easy fix page I probably would miss that I can just write documentation I can translate I can help organizing even straight That's all easy fixes for it's taking bigger like easy fixes. So awesome. Thank you for that. So anybody else has some idea Like do you think you for the new cameras? Do you think that you have some processes, you know? teams or communities that are always repeated like for example when you get to a Group of students from a high school and say hey We are from this awesome team and we want your help you can do X and then you Realize that you're always saying like to do X you need to Download this thing you need to make a decision based on some prior knowledge and the people get back to like I'd like to down for example, I'm from Fedora so they say like which ISO should I download which Fedora release should I install which which which which So that's the expert knowledge and then it's where like where should I find the most recent bucks? Where should I find the blocker box for what our blocker box? Like tell me tell me We want to Make a hub of information, but not only information you want to make a hub of simple processes. So if you have some ideas for examples We glad to hear it because this is not really about me telling you what we did I'd like to get the input and make it better make it awesome. Hello. My name is Alberto. Actually, I'm Part of the Fedora join seek Is a group of people Looking for new contributors in a lot of parts of the project the basic idea is was a hub of Singular interpoint to the project I have a Couple of questions we This page is linked to the what can I do for the Fedora project? page Yeah Sure, you mean you mean I mean if we point some people to the What can I do for the Fedora project page? And okay QA is awesome. I and click the There the link Open this page. Yeah, the link is here Not sure if this began, but like in this area if you didn't find anything Okay, I I mean But I might be misunderstanding, sir The opposite direction. Oh, yeah, okay. Okay. Okay. Sure. Sure because for the Fedora join team is the This one right is the entry point. I don't know what can I what can I do? Okay, check this and maybe you can find something to do or But the question is if okay If I go to the QA session of this page This pointing to the new page The new page of the QA team Yeah, absolutely. Why not? I honestly didn't bother any of you with it because it's like it's living on an URL that's probably temporary a domain and then With me Thinking like maybe too big from the beginning. I wasn't sure that it might Like I wasn't sure it wouldn't just end up being like with all the project in the end like with all the project being like if you didn't find Something like here. Maybe go check on the other page So I didn't want I didn't come up with a reasonable solution to just not pollute the whole ecosystem But I'd love to work on it with you, especially if you like it like Absolutely, okay This is my second coming Actually used the RIC Protocol is a little difficult for newcomers maybe You have a telegram bridge for the RIC channel Honestly don't know Yeah, yeah, it's what we do. So maybe it's a good idea put that in the in the page because it's all One of the single points with the people. Okay. Are you gonna hold who do that? No Matrix also works both a Telegram when we have a solution for the telegram Bridge is very pretty easy use Use that go into the group and you start talking This is a great idea put it that I love your page The joint seek will be very appreciate a lot Than the six and another is the parts of the project document very well their process to to the newcomers newcomers, so maybe Okay, we We will do a promotion of the site of course We will study that And Maybe we come for that Because sure it's a great idea. Thank you. Yeah, absolutely. Yeah I'm glad to like it. Honestly. So promotion of this thing wasn't my the top of my to release because once again still proof of concept, but yeah, like absolutely for willing to just Add a link somewhere like with the telegram. I love it like I Don't use telegram that much, but I guess it's something like the IRC chain loans something like that when you join you just get hey I've seen you've joined For the first time after a long time. Maybe this is important to maybe you check it up something like that Sounds awesome. Love it. I Have a couple of more suggestions like This format of describing the activity. I really like it, but I feel like Again projects will not come to you to describe the process in this format So I think it's better to if you will would share the Best practices or dog how people how to write such a nice document for people and then projects can use your Approach as a template and so I I would feel my data in the fields, but I will get the same Behavior and so that like I'm not a JavaScript person. Yeah, I have no idea This manual is so if you just say me if I put this Was tech text like file if I put in these lines my text when it will show up nicely like this This would be already linked an awesome tool for every project will have a Format to describe their newcomer process in a nice way So we can join this and then we just would aggregate it on the on the on the certain front end But like every project will maintain his own like page for this kind of data So share share we template basically and Also, I don't know if you heard Fedora infrastructure team will go going to provide an open shift for community projects Finally, that's yes, so it was announced yesterday and you can actually already get the access there So you can migrate to pod in an open-shift community community open-shift instance of Fedora project They are sitting in another room right now But you should you should just find Kevin and ask him for access and he will add you to is an early access For this project. Yeah, that's great news. But getting back to your previous one. Yeah, that's that's a great idea like I Have been thinking about templates But what do you like I didn't get all the way like I was still thinking about the templates on the data level like engineer, right and What you say makes much sense like if we Especially in combination with some of the beggar tags for example So we can easily identify the projects and do not need to crawl the whole beggar for just this one specific file that makes a lot of sense to me and Honestly, some of this is Static data, right? I know the body karma. It's just describing the process. It's exactly what you just said some of it is like pulling and combining data and that's something on the next level where we can then work together with the people but just being able to say hey, I have damp down this process of our Sick or something like that. Can you show it for us? Here's a file sounds awesome and the template could be easy like Do you think that? The template could be just a I know structured like this structure text something like that saying hey feel these You know, yeah. Yeah, come commented text file with like fields and where you you need to fill in the text for me It would be it would work definitely. Yeah, absolutely love it. It's awesome. So yeah, I'll get a piece of paper and write down Also, like I see the applications for example for doc site I can add some a custom JavaScript to doc site so I can actually to my generic doc about my project I can add Pages which will be formatted in the way which the custom JavaScript will show like this So it will be nice addition to doc's engine basically if we get get it to these besides also We will render this pages like this as a part of a documentation pages Yeah, yeah, I quite like it. It's what I know mostly that's why I wanted to do the because Would you just that is so simple yet so complicated for somebody like me to come up with So So awesome. Thank you. Thank you for input. That's absolutely doable. Like I'm not saying I'm gonna do it on the way back to the window but I think it's on a scale where it's super easy to do and the work is more in Communicating with people and trying to decide like maybe we can Enrich the easy fix taking bigger some bit and maybe we can put together some standard for a Community information file something like that. So also, so it would be like optional, but we will have a possibility for projects to easily expose their like public interface to people Absolutely, thank you so Thank you for coming I Honestly hope I'll get at least an out of ideas, but then again, there's more of you that I expected when I found out that It's 9 a.m. Sunday. So thank you. Thank you very much for coming. I'm glad you came. This has been super helpful for me Like I'm glad that you like it. I'm especially psyched for the new ideas and I'll put some kind of Smallish presentation to shed. I'll put them at least Yeah And There be come there be contact information. So for you that forgot my name already you could you can ping me and hopefully we'll Push this further. So thank you much