 So I see people are joining. Let's probably get started. Welcome everyone to the talk about Fedora and all contributors survey. This is the second time we run it this year in June. And it's all about like how we did it again. So let me just dive in. Actually, I'm going to start with the most important slide of them all. This is the highlight of this survey this year. So this is the second run. So obviously we need to compare this run with the previous one. And if we look at the participation numbers, these are just amazing. So in 2021 we had 800 people replying to the survey. We thought it's a really good, a very big number. And in 2022, we got 1,777 replies, like module plus minus five things, which I may be missed. And this is really, I think a huge success. And I think it's really nice to see that like survey is not became boring as a topic, but rather people actually enjoyed it the first time and participated more the second time. So I really hope we will keep that friend going and we will get more people participating because this is really an interesting opportunity to get a look inside Fedora community and see what people are using, what people are doing. And this is the main reason why we wanted to run it. And yeah, we highlight also the satisfaction rate. This is the average number which is counted. So people were asked if they will last question of the survey to rate their satisfaction with Fedora project rated from one to five. And in 2021 we had four dot 23. And in 2022 we have like so many more participants and the satisfaction rate was even bigger. It is four dot 28 now. So we're doing I think pretty good with respect to those numbers. Let's keep it running, but yeah, let's now talk a bit how we keep it running. So since this was the first, the second run of the survey and you know this joke like if you do it once, do it manually, if you do it twice, like repeat the process and if you do it three times automate. So we're not fully automated this thing yet but we really tried to focus this year not on like changing that many things but on understanding the process better and making this process open and reproducible so that it's not just me or Maria who can create this survey but this is something which we would, we plan to do every year continuously and we want people to be able to jump in and do the work or change the work or participate in the open manner. So what we did to achieve that, first of all, we agreed on a fixed schedule so everyone needs to remember that Fedora and all contributors survey runs in June and this is the month when we ask questions and sometimes it's all the same questions, sometimes it's a couple of new questions but be ready and you don't even need these banner announcements. You just need to get used to that in June answer the survey and we're good. Second step, Marie actually created a step-by-step how to, in Fedora console.org, how to make story happen, to happen. So we described preparation, we described request for a bench, request for a banner, how to, we also put the estimate dates when it needs to happen so that people have time and so on and we really tried really hard to follow that step-by-step how to this year to test it and see if it works. Of course, we missed the line several times but in the end we followed the process and it was much more easy than it was at the first time so I'm quite satisfied with this description and it helped. We also put questions of the survey in the same Fedora console.org's repository and it's in markdown format so when we talk about these numbers later if you see what questions needs rewarding or questions needs different variants or you want to change it completely and suggest a different aspect of Fedora to look into you can really just go and submit a pull request for that repository and we will review that and we will talk through this and change the next year's survey to accommodate for this interest points from community. So it's everyone's open process to participate and we're welcome everyone to join us. And we already had one more person joining. Thank you actually for helping with a banner and organization work. So this was the main focus and I said I think we did a really good job to set up the next step would be automate all this but yeah, we will see how it goes next year. And now let's look into numbers, actually not numbers but a lot of bar charts. As I said, we are learning as we go and I had to learn a bit of pandas while creating these things and my level of pandas knowledge is kind of bar charts. So I will be presenting a lot of those right now. And yeah, if you have different ideas and want to work with this data, the data will be published with sanitized part of the data will be published for anyone to play. So this is like the opening question which we asked is what are your roles in Fedora project and people were able to choose multiple roles and we preceded some of those in the options to answer. But people went then creative in the comment section which maybe mean that we are not covering all the possibilities here. So this is the opportunity for you to suggest different options for that list through a pull request. Everything is welcome. But this is the current state. So we have of course users, package maintainers and all other groups. But I think that I was interested in some other aspect of this. So I tried to add some layer into this graph. So I linked this question with a question is English your first language because I wanted to check if we have like certain roles which are dominated by English speaking community and which are like hard for non native speaker to join. And from the graph, at least my conclusion from this confirms my estimations. Is that Fedora is pretty much a diverse community and we really have representatives of non native English speaking countries participating in like all areas of Fedora contributions. So which is I think a very good outcome of this question. Of course, this is our all time favorite. We what's your preferred desktop environment and this is how the questions of how the answers were given. GNOME is our default desktop environment. KDE goes second and we have various spins and possibilities. So in this slide, we can actually say, OK, GNOME rules because it is default. And this gets to us to the next slide, which is what's your preferred text editor. And I have a note here. So we had actually two questions in the survey. One is what's your preferred text editor and the other is for small random edits. And the other was what's your preferred like development environment. And the expectation was that when you do one line changes, you use one editor. But when you're dive deep into the coding, you probably use a more advanced ID thing. So this question actually asks about the small random edits, what you use for that. And we see that Veeam is winning in the nano, which is currently a default text editor in Fedora is not really getting as much attention as Veeam does. And then I also wanted to check this question with the roles Fedora has. And yeah, honestly speaking, this question is like the main reason why I even started this whole Fedora survey effort because when we were discussing like what's the default text editor, we were talking about like what people prefer. And yeah, in this graph, I would say we also don't have a strong preference for nano even though it has a preferential treatment right now as a default editor. Maybe it's too early to see I'm not trying to make really suggestions here. But this is the data we have right now. So now, yeah, the maybe interesting question would be like, why is it actually the thing here in Fedora? So how does it correlates with the existing knowledge of Linux, which people have? So the theory we wanted to verify was do people who have less Linux knowledge prefer nano and people who have more Linux knowledge prefer Veeam. So I created one more graph for Veeam on nano per Linux knowledge. And you can see that yes, of course, so we were able to rate Linux knowledge as a self-assessment. So the participants of the survey were asked to rate their Linux knowledge on the scale from one to five. Do they feel they are like beginners or they are power users? And I also linked that these answers with Veeam on nano question. And we can see that nano is used by power users as well, but it's still far from default or even on the level two. We still have people preferring Veeam over nano anyway. So I'm going to stop here because you probably see that I'm biased in this old Hollywood topic. But this is something which I wanted to show you as an application of the Fedora survey, which we can do when we're participating in all sorts of holy words and conversations and also trying to make decisions about Fedora audience and about our set of defaults and our choices in the workstation or whatever it is. So consider this as an example, but also consider how maybe you can use this Fedora survey for your own purposes and what questions you want to be answered. Because this topic was specifically my interest, so I make it so that it becomes possible for this survey. But we're open to all kinds of research topics like this. Think about it, come join us and we can do similar things later. Now, the other topics which I like to highlight is the modules and flat packs. So this is the slide about modules. Let me explain a bit. So the blue part of the graph is just all responses of all people who had to answer the question would you recommend using modules for anyone? And we see that majority of answers were that people still don't know what modules are and what's the purposes of them. And the orange line here is just representing the same kind of answers but filtered to only the people who actually at least tried modules at least once. So still like there's quite enough of no answers but also the yes answers of course appear. And the similar setup I did for the flat pack question and here we see different pictures. So flat packs are really adopted a lot among the participants of the survey. People use them, people at least try them and people also would love to recommend them for I guess certain use cases. Not everyone of course, but yeah, a lot of people enjoy flat packs a lot. What else? Yeah, of course the mandatory what programming languages do you use? This was a multi-choice question. Of course, Python wins. I mean, there are attempts to add a bash to that list. I see them when people vote other and they put bash a lot there. I'm still kind of not convinced that we should count bash as a programming language in this case. But you can convince me differently and yeah, again, we can change these options and add bash here. I actually maybe it's worth adding and we can compare if bash will win over Python or not next year. So let me know what you think about that and if it's worth doing so. And yeah, we see quite a lot of Java, Rust, Go, whatever it is. So yeah, maybe we should see changes in this over time. And this actually raises one more interesting question, which is, I hope everyone realizes that if you started to answer this survey one year, then it would be really nice if you continue to answer this survey every year next because the more we run this survey, the more we're interested in the trends and also in the changes of your answers. So don't think that if you answered it once last year, you're free and to go and don't need to participate anymore. This is the continuous effort and I hope it's not too hard for participants to just see similar questions next year and just see if something changed over time or not. And also a bit of an interesting question to me at least is what forge systems people do use now in how it also would be interesting in historical retrospective, but currently we don't have too much data about this. So this is the current state. We have a lot of GitHub, GitHub users, Pagore. We see some Garrett users also. It's nice to see fellow Garrett users in Fedora as well. And yeah, we also have quite a number of people who don't use forge systems or don't admit they use them. And yeah, this is the state of 2022. And we have more questions and more numbers to share generally, but I haven't prepared that many graphs for every question. So I wanted to show the highlights which I saw. I want to highlight one thing is that in this survey we had a lot of yes and no choose the tool questions, but we also had comment fills and I want that people to realize that these comment fills are not wasted. And Fedora console and Fedora project leader literally reads every comment you put in that survey. So it is valuable information. And I think Matthew in his talk yesterday did some reference some of those comments and addressed that. So these comment fills is not something we can share freely. I'm actually not completely sure how to organize the process around this better because when we allow free form text filled, we allow people to write whatever we want and then it becomes a privacy issue to share this outside of the very limited group which we intended it to share. So currently these comments are visible for Fedora project leader console, but maybe some kind of work can be done to make it also more public or maybe we can add an option to this comment where people can request the public feedback on their comment. Yeah, something like Mira said. So that comment can be shared and we can write in response to that in some of the public channels. So yeah, but still even now without the formal process, it's still being read and not all 1,700 people wrote comments, but everyone who wrote this was heard and read by FPL. And so yeah, the next steps on this thing. As I said this year we were focused more on documenting and writing detailed guides how to do things. I still am planning to publish community blog article with this graphs and reference in the raw data source like sanitized without text form text comments. I want also to work on some automation of the processing of this data because the first year we tried really hard to like read every like field in the other comment and use it and then transform it into a yes or no answer in a new column in the data. And it honestly took huge amount of work. And this year I was just realizing that I probably demanding too much from that process and I need to relax the expectations a bit. So we relied mostly like the other column. They basically replaced all the values in the other column with just the other. And this was the way to like formalize this process and automate it easier. And we probably need to look more into the ways how it can be done via script, not manually and reduce the manual review to the comments fields and to the search for obvious like spam trolling entries which are not useful to any analysis. Yeah, I'm also, as I said, I'm going to publish with sanitized data set for everyone to play. I'm going to iterate on questions. I'm also inviting everyone to think about it. We, of course, want to run this survey in June 2023. And if you want to participate in the process or in the design, just join this is now a documented process. And this is all going to, yeah, going to happen soon. I think I have time for questions. So if if there are questions, let's look into the chat and everywhere. If not, I can show you how I did it this time. And so you can see how much help we need really. So any questions in the chat? Okay. While you think about something, I'm going to show you my super awesome Jupyter notebook which I've created to parse this survey. So, yeah, this is basically data which we're adding. And then, yeah, this is the function which I used to draw the columns to draw the number of yes answers in the certain column. And I can show you how the survey looks, how this thing looks like. So we have responses, we have columns, and we have yes and no questions for each option for these questions. So if there is a question, what's your role in the Fedora product? Then there is the possible variance with the answer. And then there's a yes and no column. And then it becomes a bit of a magical thing to me. So this is how I am trying to do the plot format and this is how the output looks like. So this is not a rocket science. This is a very basic science. And if you, I will actually submit this Jupyter notebook also to the docs repository for anyone to look at and also to invite people to show me how to do it better, much better than it is right now. And that's all I had for this talk. And if there are no other questions, then thank you for coming. The community blog article is coming. And if you have any specific questions you want to ask and to draw the graph, you can reach out to me, ping me on matrix and say like, what if we draw this kind of picture? And I will try to draw it for you. I'm still learning, but I will try. And we actually are interested in getting these ideas like what kind of questions people may ask from this data. Feel free to participate. Thanks everyone and see you in the social events, I guess, the next time.