 Hello, I'm Gabriel Trombini, so I'm a member of the S.I.G. Fedora Giolli. Today we talk about the rescue of Mary, who is married in the Fedora Sea. Why not? Because if you have to surf the wiki, you probably get lost. In the general part, we talk about the target role, safety, workflow, and get it help. Then there is another target. It is the process you need to find the common parts of the group's joint steps. Well, every group has a joint page with some steps which probably can be unified in one. As I say, help people to be less cared of the wiki. I think it doesn't need any explanation. Stop people escaping because of wiki issues. It's the same. Leading recruiting to higher rates. What is this? The general group tries to get the recruiting. The recruiting is a bad word, but I don't see anything else to say the same meaning. Probably the joint group can unify the common parts of the joint process. Have more contributors than before because we see later. They are following, they are instructed, they are more less confused than they go to the wiki themselves. It's okay. I don't know if you know my slides on my FPO account. I use always to join the dora workshop. I have all non-technical contributors as one page. It's designed, of course, so you have a little boy or girl who makes this truck. Then you have the description of what you have to do for getting part of this group. It starts with the name of the wiki that they are, or different. Then some steps are different. I agree totally that this has been unified, but the point I have that the joint group exists since five years. And we have talked definitely since five years to do this and nothing happened. The joint group is for me personally a bunch of people who are sitting in an IOC channel and doing nothing. The joint group has been renewed because Pete, me and Ankur take care of the joint part. We have the great joint pages and we can remove them from the joint pages. Maybe you're right though. Is it a lot easier to talk about it than it is to actually go out and do things? No, it's not heavy to do things. Just do it. It's not heavy to do things. You can always talk, we have to improve, we have to improve. You can talk this, but nobody of us will stand up and do it. You have to do it by yourself. If you have the feeling, do it. You might get some fights about this when it comes to unifying because you have to speak to the other groups that you have to unify it. So you have to start doing it. That's the whole point and joint group. The idea is nice, but they are not in the opinion to help. From the SIG we keep page, the goal. It's a part of communication channel between existing contributors and prospective e-contributors to us. This is clear. We take care of the contributor's questions and speak with the group's leaders or members. There are some groups that need mentorship. We can create an easy way to go to the mentorship. Give a communication channel to converse among themselves in the joint channel, for example. You can talk, you can ask everything. Make it easier for the new people to learn by getting them started on simple tasks. We have a track where we can create some tasks. I don't know how, but we can do that with our tech. Using our tech for helping people. Can that take away from the teams? That's not possible. They will never agree to that, that you define how they make their things. That you have to definitely move up to them. If you talk to the teams, it makes the processes they have with the teams. They make totally sense from their perspective. This point is more about we have the easy fix app. All these groups have a track. Nobody knows really about easy fix. We have to make easy fix more prominent. I don't know if you remember Max Spielberg. He was in my home town in 2008. He gave a talk there. It was about innovations of the world project. It was not about innovations, it was about how we fetched contributors. The problem is only they have to get this data. From a consumer to a contributor. You have to just make something. Something can be a so-called low-hanging fruit. Like this supplemental wallpaper. It's a low-hanging fruit. It's your first contribution. Then you realize, if they have realized, that can be easy. I'm now doing something for the world. I want to do more. Then you guide them in. That's the way how it's done. It's not just unifying. Nobody comes out. Yeah, I want to start contributing to Fedora. Normally they are users. They have to be transformed from the user to a contributor. It's not that somebody out of a black mask comes and says, I want to contribute to Fedora. We have to make our low-hanging fruits like easy fixes more prominent. So that our users find them easier. And we have also to create some low-hanging fruits to make the first step out of consumer to a contributor easier. I'm afraid that we can unify the next three steps. You can look to my chart. If you look, there are only on two or three teams something different and that makes really sense. And what can be unified is finding the steps individually to unify the URL. The discussion we've had about unifying isn't saying everybody is going to go through the exact same process through the same mechanism. And then at the end it just spits you out in different groups. It's not that kind of unification. It's more saying that as a SID, we should be looking at what the onboarding experiences for each of these other groups identifying common things, identifying what each group is doing well and seeing how those successes can be applied in other groups. So it's not a wholesale taking that process and saying you all have to do this thing now. That will definitely also never work because you cannot demand the teams what they have to do. And hopefully the teams are purchasing as well. One of the things that we identified for this was the introduction even. Every group says we have a mailing list. Please introduce yourself where we're all friends. We're all people. Let's say hello. And some of them have templates that end up getting filled out and I am Charles and I work at the bank and I like the door because it is fun and I like the result and they spit something out that's very... It's not very engaging for the reader but some groups have something that's a lot more engaging and so we can take that and make that idea of engaging on an introduction, share it and have the engaging questions reasonably different for each group. I think the best idea is... Saruk can... I don't know if you have ever seen the Mozilla engagement pages. How many... I don't know... Economic? Yeah, I don't even know how you define that. There's no activities that we declare that this is the door of joining and this is what we did as part of the joint. That's the problem. I have the different door of joining. The idea I go ahead there is a very nice one but it totally fucked up to give it life. That's the problem. They changed it a little bit but that's a nice overview page how you can contribute to Mozilla right now. You have the different kind of things you can look what I have to do there and then you find out that's something that I could do but I think I can do and then you look up for the process. How do I get to that? I was just going to say that for a lot of people that are interested in joining it's probably a really good opportunity that I could throw two out and just set a framework for people with it. If I had my way I would still spend another two or three months just to see more on Mozilla. You can't just drop in to be a known user. You need to establish very much a problem. I've been walking on eggshells trying to figure out I think I've got a decent set of tools in the toolbox and Fedora joined as a SIG it's been around for a while I know there are people at this point I'm excited. I think I've got some of these problems at least some ideas for proposing a three-year-old album you need to find and develop a new kind a new base of contributors because like you said there are a lot of people that are primarily working on it I think that there are a lot of things Oh you have a problem with how it comes right? It's the right one. Is it right? No it's Fedora people in our process. With the hubs I think we are going to achieve this and actually as the people are saying this activity is for me and seeing a button or an app and receiving some kind of mentoring or leadership from those people who are currently in the joint SIG you're going to guys are going to be also with the mentoring team and with this way I think we can recognize everything because mentoring for a team and mentoring for ambassadors as we have these who will revolutionize everything and will result a proper contributor a proper ambassador and a proper coder and we are tying together with the right informations into the hubs and building up from to talk to the leadership to the council and so on and from the top to downwards also I really would like to see also some corporations like when I would like to have a hiring desk on the events that really people have noticed that hey this is right Fedora guys have you had your best coder for the WFI I think the person would be right Flox 2015 as the some of the problems that I have had so far Flox 15 I know there are some mailing lists and I know there are some groups but like when you want to put out where is the place where we announce is there like an over so that's where I'm hoping the commops can try to do but at the same time in the practical sense right the really important part we made it right now the problem is storytelling and organizing talks talks talks and their characters like and talks talks talks talks talks talks and say, I can't program, I cannot contribute, so I have only the jobs on this slide which have nothing to do with programming or packaging. The packaging I have in it, so the point is, I did five years ago for the join pages, that's the time we talk about it, five years ago. Over here, we're here. We have to, I'm saying, because those look good, and they are, that's exactly what I'm talking about. I mean you can read it in my blog, there was a lot of people against it because it looks too childish. You might have some slides further down the line here that answers some of the topics. So if you look through, I have then always the points, what you have to do, what the team do, and then what you have to do. And if you look through the points, they are not that much different. It's just on two or three teams, like we, as the design team, we want to have them make a ticket. The infrastructure team wants to have the apprentice group, makes totally sense, because you have not all right to our infrastructure in that role, because you can do a lot of damage if you would have, and you have not experience. So that's a very good thing to do. But they are already unified. So the point we have, one of the points we should do, first thing is make really good joint pages. So we are, we built our whole bad pages right now, so we have to convince Mo and robots to make us nice joint pages again. And if we really invest some time to units, and it's really, we have to speak to the teams, so that we can unify it in the most of the parts, to make it easier for the ambassadors to communicate it out. And one thing we have to do, we have to create more low hanging fruits. I use easy fix, make a ticket about an easy fix book. I know, that's the point there. Getting people to recognize that is difficult, and they are really easy close, they go really quick. It also abstracts the experience from where the work is actually getting done. So you start with an easy fix, and you think, okay, well I've got all of this set up, and now I'm ready for the things that aren't so easy, and you have to learn a whole different level of tools now. So route the execution. So route this last year, flog, and talk, the name was the experience of a fellow on UV. And exactly this came up, and Matthew was in this talk, and he made it out that it makes already more work for an experienced developer to really mentor a new contributor as if he would do it himself, but it is worth it. So that's what the Fedora join would have to communicate to our developers. And one of the points is, you have also to find mentors, because mentoring cannot be done from everyone. Mentors, ambassadors, but I think it should be, actually who are educating, running the club, and the ambassadors, actual people, and the mentoring, that way, you get the hubs, you jump on the wave, and we are solving the solving. I think we have enough ideas to probably come up with something actionable. You've got size, I know we may go back a couple of hours. I'm going ahead. At the moment, it's up to you. Contributors, me, Pete, and Hank Ursina. The wiki page, the join-sig wiki page, not the join wiki page, we have a mailing list, we have an ERC channel, the charity system, as we said. I go faster. So, contributors, contributors can be, the one who has a FAS account, and the ones who have not a FAS account, everyone can continue. Okay. No, it's not possible without FAS account. You can't contribute without selling a DCL or a FDCA. You can't contribute without it. It's not possible. In the join-sig, it's energy. Yes, you can. No. How do you join-sig without having a FAS account? It's not possible. There are a lot of... So, you put in this kind of content. Yes, it's a kind of contributing. Yes, but you cannot make a FACCILOV and drink without having a FAS account. You can join the ERC channel. There are a lot of people working for Fedora that haven't a FAS account. There are stages of participation at this point. We want to give you a piece of advice. Yes, I know. I'm totally aware that it should be... If you talk about low-hanging food, they should not be depending on a FASCILOV. Right? From the legal point, you cannot have a contribution without signing the license agreement. So, the only thing you can do is just join a channel and have a conversation with us or join a mailing list and have a conversation. I don't say that you have a perspective in terms of signing it. I'm going to send it to Fedora's joint page, the main joint page and the SIG joint page in the community. Actually, we are actually Fedora's joint page as a joint from Fedora Project. It's easier to remember as Fedora project slash Vicky slash John. It works as each mailing list in the project. The Fedora joint channel, for the ones that don't have the IRC, there is a weekly page, the web chat, directly from FreeNode. We will install, we chat, we chat and the specific project. Okay. It's actually a statement that works exactly as the others do. You create a ticket, someone takes care of it, then you work on it. No other tracks in Fedora work the same way. I can tell you, there is a lot of structure that we've set up that's not introducing people contract is within that same. This is our workflow. Join in this through the joint Vicky page. The groups with the page, I think, are so clear. Then if you go deeper in the Vicky, you can get lost. If you're not sure what they want to do, take care to understand the skills, the advantages and interests when we see later this point. Join in them step by step along the joint process because it's not... This is my experience. When I joined to the ambassador group, I had some difficulty to understand which step before, which step later, which step how to ask for mentor and so on. I think every joint page test is difficult, this issue, somewhere. Of course, if there is a mentorship, the last part of the joint process because we can substitute the mentor. Who is Mary? Mary is a fantasy girl that wants to join somewhere in the Fedora project. We have to know why Mary is my name, understanding Mary and then rescue a class. We have a new contributor. This is Mary's steps. Take a look at the Wiki. Try to follow pages. When you are on the joint page of each group, you can follow simply. When Chris knows this problem, when you search something about marketing, for example, hundreds of pages of Wiki, you get lost for sure. So get stuck. Then, okay, I go to sleep. This is Mary. Understanding Mary, Mary is a newbie. She is shy because she doesn't know. She has some issues to relationships. This is a fantasy man. He is not you. You expect a shy girl to open the IOC and question you in Fedora joint general. That's a problem not only I have in the joint group. There are a lot of people who are... Why not? Is this way to ask for some help? Self-made. She works as a account or in the marketing or his other factory. But her only is to play with fear. When I started, I had fear to talk with Sierco because Sierco is an institution. So it's difficult for someone talking... Sierco, how are you? I'm fine. I'm German. I'm the answer of this stuff. The consequence is that the newbie is feeling alone. How can I... How consequence is turn off the PC and go away for me? This is what happened to me. Okay. How we can rescue Mary? Lead to Fedora joint IOC or many links. Don't take track of history. Make her feel comfortable. We need people who have relationships in relationship capacity. Help her pick an area she'd like to work in. What do you want to do, Mary? I want to work with design. Sierco, come here, please. Sierco. Then people can become friends. After keeping touch, meet a confere and just have fun making Fedora better. This is the consequence of the journey steps. For a skill. At the moment, we don't have anything that lead the people to Fedora joint. Actually, user have somewhere as well, maybe perhaps hoping in a mail. I write a mail. Maybe someone will reply me. This is actually that people want to join Fedora. Is correct. I answer some points of brainstorming. Increase visibility of the target and make more people aware of it. What do you say there before? Robert. Robert. You had to link Fedora joint into the FPU. This is one moment. Means more before said that probably they have will be, I don't know, they have or Fedora project? We have unified a lot of sources we have. And a better overview is that you have not took out your project to follow up what is going on. That is what happens. Or at least make it better. Informing ambassadors. Magic group, joint process. Informing ambassadors. Why? They have a meeting at all. They link the people to Fedora joint. Okay. You want to become part of the Fedora project? Well, start with Fedora joint. And then things will go ahead. Mary has skills and expertise. She has an ability to interact, I think. And we have two more important. Understand Mary's interest. She is working, as Pete said. She is working in a bank. But she hated her job. Also if she works on the PC. But she would like to have some interest with respect to the everyday job. So, the important part of this is the interest of Mary. She likes to draw. Presenting is for you. I go ahead. Then we can talk about. Okay. We can suggest the best choice for Mary. I am not able to understand in which group she can work on. So, we can explain the list group and choosing with her the group of interest. Okay. When Mary chooses the group we can ask to a SIG member if there is one member in the SIG on the SIG. If there is a member in the SIG to take care of Mary or we can ask other groups if there is one person to take care of her. Then we can check Mary's integration. Okay. After these steps, Mary is a new contributor fully integrated. We should keep in touch with Mary because we don't know how the transition will end. We don't have to make Mary a step to help the NSW. And then check Mary's certification just like this. When installing, this is the end. Okay. We have to encourage each fedora team to have a present in the joint SIG. It's an SIG. It's easy for us. Yeah, it's fine. No, you are a member of the joint SIG. I'm not a member of the joint SIG. No. Tomorrow you are. Yeah. I have an opinion not to get a member of this group because of something special. I have a problem. So I will stay out of it. I will definitely contribute without getting a member of this group. That's okay. Yesterday we heard that the mentorship is also the same thing. Then the SIG also wants to do the mentoring and teaching thing. So what would be that just actually unify these two of one group and let it allow to have a staircase. So campus ambassadors can be the ambassador junior category just the first level. Then the second one can be the ambassadors and the mentors who are just leading teaching and more. That makes sense. One problem I have been joined with is the idea is nice. But are you really responsible as joined group to get the in touch with the potential contributor itself or is your responsibility not more to watch the Fugora as a project that all the teams making it easy to join that would be more a job for you as taking care of each person who wants to contribute. You know, the idea is good but it's not fall to the end. This job I will say is a big job, is a huge job you would have with that person not enough personnel to really watch all the teams if they make it easy. You have to think about knowing through how can you create them how can you make them very visible. That would be your job not to fetch each contributor personnel that is the job for your teams and you have to watch again so the teams that there are mentors there and that there are mentors who really can be mentors that's the context for a lot of the stories behind the presentation we're thinking about campus ambassadors who go out and they go to at fest or at school and they say when they talk about Fugora Fugora is great for me there are a lot of things you can do and some people get really fired up about it okay I want to contribute to Fugora where do I get my kernel patch how do I commit to the kernel I want to see a better widget and know and they've got no idea how all of these pieces fit together where their contributions would fit and the campus ambassadors can't scale or maybe I just don't know enough about what these other groups that are definitely part of it but if you meet people in person and you fly to Cambodia and you talk about Fugora depth design and then they need somewhere to go if they want to carry on I have a different understanding of mentoring means mentoring cost me really a lot of time and I do it over a year or two years even over five years it's necessary I'm still also always responsible for the people I mentor they still come with all the questions to me I'm the first person they speak with so I can tell you in person some experiences how people try to join Fugora and find their role in Fugora if you talk about Cambodia you can talk about Misa Ban and how she tried to get responsible for the Kimya translation which was only with the help of Jared Smith to make her responsible inside trans effects for the translation so that she can get users in the role of translator it took one year to get her in this role and that is this encouraging and that would be the job I think of to join Fugora to find such stories and find out where we fuck up and solve this problems I think that's a lot of stories about Cambodia stuff too and there's a lot of common onboard and it's not this encouraging to try to get to become a country figure one of the things that figuring out the better idea wasn't the best idea I think making for each step a batch so you have to unify it for that but you have for a lot of things already batches yeah so maybe instead of not creating a series of onboard batches for every single group taking the ones that are common for the other groups we have already batches so it's just as we have come up with some batches more for all the crews but well including onboarding the people I see on the slide right there so having that process be clear so that people can find it