 Hi, my name is Marie Norden. I am Fedora's Community Action and Impact Coordinator. And here with me is Alessandra. Would you like to introduce yourself? So, I'm a member of Fedora Console, so my position is not to do anything but be part of it. Awesome. I mean, I think you're involved in a little bit more than the council, but yes, that's the title we have, I guess. I actually started with Fedora in like 2013. I feel all reminiscy from that Fedora Project, Fedora Project leader session. All right, so we're here today to talk about the survey. So, we ran our first contributor survey in the month of June, and it went really well. So how did that come to be? So, Fedora Council issue one on Peugeot was a survey. Yeah, that's the point I added. Like, we had the issue for Fedora Survey filed as the issue number one on Fedora Console project, which was seven years ago and the issue was filed by Matthew Miller. I think when he was naive and just started his role as FPL and he filed an issue like, we want to know more about our community. And yeah, we revived this conversation. For me personally, the reason to revive this conversation was the recent debate about the default text editor. I'll talk a bit more about it later. But yeah, this topic was revived and we started to think about how to actually do that. And then with Marie, we got many teams involved and Marie, you can cover this maybe. Sure, sure. Yeah, so actually Alexander wrote up a draft like right away. And everyone was like, yeah, let's just pull the trigger and do it. And I was like, hold on a second, everybody. Let's try to figure out what we're trying to accomplish with this. First of all, people, I mean, get offered to take surveys all the time. We do surveys within Fedora and CPE does surveys. So we wanted to make sure that we weren't like just sending out a survey that wasn't going to get us the answers that we wanted. We took a step back and we said, okay, you know, we're not even quite experts on this. So let's like take a minute to figure out all the different things that we want to learn and get some input. So we spent some time documenting what we were trying to learn and we checked in with multiple stakeholders on that. So we worked with the revamp team, community outreach revamp to help guide us because they're the ones that are kind of up to date on the outreach efforts in Fedora. We also reached out to the mind share committee to help us review. And obviously the council was kind of like stewarding it all along. But then we're also like, okay, how are we going to get people to take this. You know, sometimes we all be a little bit of incentive. So, of course, one of our first ideas was badges. So we needed to coordinate a badge and then I was like, you know, I think we need to put a banner out there. I don't know who came up with the idea first, but we're like the banners the way to go and actually with the help of a newly formed websites and apps team, we got a banner up on five or six to our websites and we also got it up on the community blog, etc, etc. So that was another team that was like pretty instrumental in making sure that this was going to get the exposure that it needed and we're going to get those responses. So we had a ton of people helping and obviously, we also had CPE helping us with Fedora infrastructure getting those banners up as well. I don't want to leave them out. So we had over 1200 responses total. And we had 800 complete responses like 798 the day before and there was 800 and we're like, what? Okay, I guess we're going with this. So, we had 800 complete responses. We were thinking around 500 and we guessed that from registrations we had seen at the release parties, etc, etc, like, okay, we think it's going to be around this number. So we were thrilled to see it at 800. And so I think one of the things we're definitely very excited about is running it again next year right and seeing what kind of comparisons we can do that'll that's going to provide us some very interesting information on the progress that we make based on this. Okay, so who responded to the survey so people could choose multiple things in this situation but this is our breakdown. It was mostly users that there could be users and these things, but we had a lot of users actually responding to the survey so that was awesome. And then the next biggest is going to be package maintainer I think that that's no surprise to anyone that that would be the next one up. And then I think it's going to be QA also important testing and right around there that's ask fedora probably is the support their documentation infrastructure. So those are also outreach was pretty high so there's a nice distribution to see. So, I'm going to talk a little bit about community related insights, and then Alexandra is going to go ahead with some of the more technical and coding related insights. So, first thing we want to I want to just highlight was we had an accessibility 3.6 out of 5, which is not the currentest I think we can improve that I would like to see that number over for next time around. So, we divided up the responses by contributors and users and unsurprisingly contributors do find it easier to find those docs resources and people that they need to find. And for those who are having trouble with it search ability of the content is the main issue. So I think we can do some concrete things to probably improve that over the next year. Next thing I wanted to point out was, we asked questions around who do folks go to for swag and event support. And the top three answers were local regional ambassadors, which is actually very great answer, local user groups, which is like, makes sense but okay. And then the council, which I'm like, definitely not. So, there's some commentary in there and I'm trying not to get distracted by it but basically the answer the correct answer in this is, is the mind share committee. The mind share committee is the one who improves event swag support all that kind of stuff. So, they were ranked fifth or something out of all of these. So, that is definitely a place in which we want to improve the visibility of mind share and what it does and we actually see that in other places and through data that people don't really know exactly what the mind share committee is or does for example, elections. We have a lot less folks voting in the mind share election than best bill or council. So, we know that the visibility is not the greatest on the mind share so we're also doing, we're doing things like the presentation we did here at Nest, which was informational. So hopefully we can promote that around. And we talked a lot about how people can be involved like it can really like anyone could be involved in mind share I'm not going to go off on that too much but anyway. And that also, if people are reaching the mind share committee, they're more likely to reach out individuals. Instead of the group as a whole, which understandable people know me people know other folks on the committees that will go to them, but we're all doing a lot. We're all doing a lot for fedora. And if people knew this process, a little bit better, it would be ideal for us. So, on to the next. So we did want to test a little bit about or try to get an understanding of the knowledge of community standards of behavior like do people feel comfortable to feel people feel like they speak up to people feel like there's things holding them back etc etc. So we did get I think that on this question there was the highest rating of people were saying I feel comfortable so people are feeling comfortable with the code of conduct being in place. We received commentary that there's so many different channels that people feel like it's a challenge to really enforce that code of conduct and I would agree as the person feels the code of conduct. It's definitely tough. We are only a couple people and we're thinking and looking and planning about what we can do about that. So we're looking to training. We're working on a set of moderator guidelines that's going to go across all the fedora so that's something I'm drafting and we'll put forth to the community and you know it'll be a conversation. When the time comes but these are issues that we're kind of already aware of. And then, last but not least, to contributors feel recognized are appreciated, and we got a 4.32 out of five for how likely are you to recommend out. Matthew's breaking down stats for us as we speak I think how likely are you to recommend friends contribute to the project. So that that's an amazing stat right there. Pretty happy about that. That means that there's a good community culture like overall, even though we have, you know, things to improve upon the experience that folks are having is overall that positive. So that's it for me for now. And just let me know when you need the next slide. Okay. So yeah, I'm going to continue with some more like data about the other questions we have I obviously cannot cover everything so I want to cover some maybe most like typical holy word topics. Not to trigger the holy words, but it will maybe some in some places, but it's just to give you the idea of any data we got and also like to as it easier for what can be done later. So, the whole survey story for me has started with this nano versus vi conversation on my list that's why I one of the issues I wanted to check was like how many. This whole nano the default as a default editor conversation triggered the chain of thoughts was the thoughts were like, do we really know what people are using and what is the most comfortable tool and what is the most common tool and how how this all things work in the community and how would we get the data like this so is the name attempt here was to do a survey and the obvious question like what's our preferred text editor. I also supported this question for question to a small tech edits and the ID type of question and probably not surprising that the I beam and no beam and whatever you flavor you use actually wins with much like we've a lot of people chosen it over others. And yeah, probably also not surprising that nano wins over emacs though I had hoped for some slightly different result there. But it's not something which we can interpret exactly right now. I think that we're maybe more interested in the trend and to compare this results with next year because then we will see that is a change of defaults changed the way people use the editors or not like what was the impact and what it can be. So, covering this original question let's move on to the next slide we have the next question about feed or models this was also interesting for me because, of course we had a lot of controversy. The conversations on fedora developmentalists about modularity are not always fun. Let's say like that, but if this was interesting for me to see the result that we do have a usage of feed or modules. It's, it's not like more not really a lot but it's really visible. And we have almost the same amount of people are recommending using models and fedora so there is like really it doesn't look as grim as it might be for some people it's an interesting technology which I think still worth looking into. And if we go to the next slide also like some very obvious questions of which desktop environment we use the norm of course wins we've larger much larger number we have KDE one thing maybe worth noting is when we prepare the survey we really put answers as some of us were thinking about the different variants so I was adding the variance basically based on my understanding of the system and being not very deep in the desktop environment cases I missed a lot of the interesting variants which people added. So for example this way, as an answer was added in the other field of the survey, which may impact the numbers there but it was added like right enough time to be added to this graph in the end so this way is now here. And yeah this maybe we can compare using sway with matter or we've seen them on or we've I free the MWM in this case so also looks interesting for me. Let's move on to the next slide and that's your preferred media player this was targeting the desktop users. The desktop user users. Once you've, when you fill the survey you were able to skip the desktop section as a whole but if you decided to answer it if there was a question there. And the interesting fact is that VLC wins as media player, while VLC is not actually Fedora package is a package in the RPM fusion. I mean, it's not a surprise probably but I think it's good to know that yeah we still have most of our media players coming from RPM fusion thank you mural MPV is also the RPM fusion things, and we can see that RPM fusion is still important and covers the needs of the media players for our contributors and users. And we can go to the next slide, which I think is also quite interesting. Again, some of the variants were provided as possible answers, some of them were added to the other field. And yeah mirror. Hello to you. Biden wins. Probably not surprising we also have C sub C++ JavaScript Java go Rust. I apologize to like all the Ruby PHP fans and others who I forgot to add in the list it was honest mistake I didn't mean anything bad about it. Well we got some answers about PHP in the other field which said like, sadly PHP or like unfortunately PHP, but I hope you guys still enjoy recording PHP on Fedora. And also, I had a bit of a thinking about Ansible and puppet in that list because you know it's not really programming language but we've the way world is going I decided we keep it there because programming in YAM is a thing now and should keep it on the list. So this is how our distribution of languages looks like now, and it would be interesting to see how it evolves over time. I think we can go yet to next steps. The next steps for this particular server results would be to publish community blog article with more detailed explanation. We also want to maybe have a Fedora podcast with the highlights of the survey. We will definitely publish publish this sanitize data set with the answers probably will remove all the free form comments but leave the fields which are like yes or no in the types of packages and languages and so on. And we definitely need to run the survey again we learned a lot from doing it this time this first time it wasn't easy. We learned about design we learned about the content and as you see there are many still mistakes in the questions themselves and the way how he stated and the variance which we suggested as a as a possibility for the answers. So I would really try the next time to bring the questions before running survey to more public discussion we did it in public but we didn't do like wide announcements for asking people to review this questions more in a wider audience I think the next time we would do that better. And yeah maybe Marie back to you to for me. Sure. Yeah, I would agree. There's definitely room for improvement on our process basically. And we have a better understanding of how a lot of the different pieces will work, but I'm interested to see what folks do with this data and what it might, you know, instigate for people like maybe we could change the question like this or that. The real barrier to improvement is people time resources. Alexandra and I probably could have totally beasted this thing and made it amazing. If we had all of the time that we would love to invest in it so if there are more people interested in getting involved in the development of it I mean it's pretty much ready to be improved as it is. And as Alexandra mentioned, we're going to be publishing the data for folks to to play with and figure out I did see the mirror that you asked if they're going to be available for download and the answer is yes. So you'll probably see that on the community blog. So yeah, I don't see any other questions in the Q&A, but I'm wondering if folks are holding them for us. I also want to add a comment that I am really thankful to the community who participated. I mean, this was a survey like obvious first attempt, which had some issues inside, but we really got so many responses which made this whole effort, like, to make it made sense now with this amount of results and so on. We now realize that this is actually the thing which we can use and we can really get some valuable information out of it. And I'm glad that people were able to provide the feedback and like help us on the way rather than just complain or ignore this. This is this means that having this as a first try was a good thing. We will do it better next time and we should do it next time. I realize we didn't put in an overall satisfaction rating in there, but I believe it's 4.23. I don't think we got that one in there. And a lot of the answers in the, what do you want to tell Fedora kind of thing at the end was that people love the friends and love the community and think that we're doing an amazing job. So seeing that feedback on its own was pretty cool to see. Of course, there's the flavor that's mixed in between all of that, but yeah. Yeah, maybe maybe worth also saying there were comments, negative comments in and this is okay. This doesn't mean like we feel bad about it. There should be comments which complain and we should be calm comments like this. We listen to them and we try to address them as well. So there are some comments about the code of conduct also with negative opinions. We think that it can be resolved and addressed and we will, we will do something about it. Yeah, so I think it's really a show. There is a good tool to have this feedback and to listen to the community in this anonymous way. I think maybe what made you can add on that. I think Matthew you already used some of the data from the survey in your talk as well. So you see like very different applications also. Cool, I think I see we have another question. Yeah, will you ask networking questions. This is also like an interesting conversation we had about the survey is what is the scope of this survey like what kind of questions we want to have there. For example, like when I'm asking which languages you use it kind of makes sense because it's it's fedora content and we can understand like how many users of which fedora packages are present in the community. When I'm thinking about networking. It can be related to fedora or like, maybe we can have a conversation about it like how do you see the impact of this question on fedora community. What do you want to get from this information related to the community because what I would avoid is just asking generic question about people's lives or work or whatever if it's not relevant to us in some way. Networking can be relevant right we can consider what we set up by default on fedora workstation so this is a good question. But we should have this conversation about new questions and I would be willing to have this conversation with anyone who has ideas so bring them in and we will discuss it. I think an important thing came up in the chat. Somebody asked about asking for people's countries, which honestly is data that we would love to have, but we do not want to touch. So there's personally identifying information and that is something that we're pretty much are avoiding at all costs because that's very sensitive data. And it comes with more responsibilities to handle. So we actually don't, we would ideally be nice to know those types of things but the resource to manage the other part of it is really not there. So that might I, if Red Hat were ever to want to know more and get involved in the survey if it was we're really getting some interest right they might potentially put some resources into it, but otherwise it's going to be us. Yeah. Yeah, it's, I think it's not even about a personally identifying info. But it's also about an information which can trigger certain like deep and complex conversations which we are not ready to have. So we need to be careful about sensitive topics here and think a little bit about is this data is really useful for us as a project and we just collected to trigger some unhealthy conversations which we won't be able to manage normally. And Miro, I totally agree with your comment. I mean that the question on what you use right now and also like what contributors use right now doesn't really reply answer the question what should be the default for the next release and so on. So it's not, it's not a direction like how do to answer these questions for engineering committee or for console. So it was just an attempt to collect data and then we may think how to how to interpret it and how to deal with this. So, for example, what I said like I would be interested in the trend. So to compare the data of this year while we must still was the most mostly default for the last year to the next year in and see how it changes it would be interesting results for me. And things like that. Cool. Well, we are right at the top of our session. Time. So thanks everybody for coming and hanging out and keep an eye out on the community blog or updates and the data. The download question. Oh, yeah, we're going to make it available. It's not quite ready yet. So it will be coming. And I'll make sure to send you a link Miro. You got it. Cool. All right, thanks again. Bye everybody.