 Thank you. So we're recording and hope everyone is fine. So I really would like to welcome everyone. I'm really super happy because Pia, which is an outreachy mentee, will be in terms, I don't know how it's, we should say probably in terms. She will present you what I dreamed about when I started Galaxy, which was like a starting point, an entry point. I really struggled when I started as a newcomer and external to the Galaxy community and the bioinformatics. But what Pia has done is beyond, it's really for everyone. So we really would like to get your feedback on what Pia has done. And Pia, you will introduce yourself. I will leave it to you. And do you want to share your screen or? I can share. Yeah. Okay. Super. Thanks. Hi, I'm Pia. I've been working on the Get Started page with Bea and Anne since December. I'm from Buenos Aires, Argentina. I like to do pottery. I'm curious. I really have enjoyed my experience overall with Galaxy and the Galaxy community since I started. And I'm really happy that I can share my work and this has come to an end where I can show it. I will be presenting. I have made a slide share. So my project was, is the onboarding process for new communities and newcomers? Big question. Why is the onboarding of newcomers? We found there was a clash of knowledge, complexity and feelings of being lost in translation between established members and the continuous flow of newcomers to retain and support newcomers with contribution and also to attract and support new communities and promote symbiotic relationships between disciplines. Then we can see the problems with them. We'll see the solutions. Galaxy is overloaded with information and unknown terminology, which makes, which means that information could be hard to read. There was no clear starting point joining the community for both being informaticians or non-beinformaticians. And there were repeated questions found on Outreach's Gitter channel. Other Gitter channels seemed too professional, but this will be addressed later as we learn a good lesson with this problem. Communities that aren't addressing Galaxy yet may not feel welcome to use the platform. And these were some comments I found on the Outreach's Gitter channel. I really did help navigate in the project. Please help me. I have an error. It's overwhelming. There's many resources available. Another person said they haven't been able to contribute much in the lobby channel in Gitter because they see a lot of professionally inclined questions. Also, very few participants got the grasp of Galaxy. There was lots of hand-holding requiring more work for the mentors and many blank questions for baby feeding, both in channels and the issues that were created in the participation period. Let's see the solution for this problem. First, we have the guest started page. It's a guide to assist newcomers with the adjustable information. The guest a clear pathway step by step for any newcomer by understanding their needs and blockages. It will ease the onboarding by providing all the necessary information in one place only. It will avoid prestation, and it also invites and promotes participation and contributions. We have the Galaxy Glossary, which aids newcomer and overall users understand the Galaxy jargon. It provides easy to understand definition and URLs for each term. It addresses Galaxy users that may not know English as their first mother tongue, and it will have a common language and simplify getting to know Galaxy. This was also a solution that was the matrix box, which would have made the Gitter channel more accessible and approachable for newcomers. I wanted to promote and aid people in asking well-formed questions, avoid time consuming questions also, blank question, misinformation, and clear ones, the ones that I mentioned that require baby feeding, and it would automatize Gitter's admin stuff. But this is what I meant when with this solution, instead of solving a problem, it would have created anyone. We didn't check with those that intended to cooperate with the managers and the developers of the channel. They said that it wouldn't be truly workable for them, so we decided to kill this idea. It was a good process though. I learned quite a bit about matrix and Python, but it wasn't the best solution. The third solution is set your own community page. It shows different communities the path to start their own in Galaxy. It helps decide someone that is unsure of adding their community to Galaxy. It also finds the work good practices. It facilitates information, tips, and mistakes when creating a new community, and it also will avoid the creation of unnecessary tools. So let's see the pages. We have this new button upon joining the hub, which we hope will help people go straight to the point. This is the main page, the Get Started page. It has a welcome message that says this is a step-by-step suggested pathway for you to follow as a newcomer, student, an expert. I truly wanted to address anybody that would be an newcomer. It didn't matter who they were as long as they were new to Galaxy. We have four steps. The first is to get acquainted with Galaxy terminology, which points to the Galaxy Glossary. It has a short definition that it contains the terminology, acronyms, and the definition. We give a warning that as a new one they will probably skim float this list, but later on they will go back to the Glossary. There are around 30 or so definitions. We have administrator or admin API, lots of Galaxy community conference, GCC, GM and GT and lots of acronyms that are used around Galaxy. When I first joined Galaxy, I truly was confused and I wish I had this helping page. We have job open source, paper cuts, planimo, quota. Each of these definitions also, if they have a page or a URL, it points to that page, like GTN, the GMN, collective news, collective look and such. If there is any other work you may need or you may think of that could be in the Glossary, please create an issue in the chat to be added and I have also added that I go back to the top because it's a bit too long and I think it's helpful. I don't know why it doesn't work, but it works. Step number two is get familiar with Galaxy. I pointed to the public servers that we recommend using, the ones I was recommended when I first started with Galaxy, which is the US server, European and Australian server. I also pointed out they should probably create a user to keep track of their histories and workflows. Then there is a table of tutorials and tools. There are lots of tutorials and tools in the GTN and overall in Galaxy and in the Galaxy search, but I went through many and I thought these were the top-notch tutorials. I thought having slides and sound regarding interactive, so depending on your preferred way of learning, you could choose which one would be best for you. I have other events, so instead of going to Galaxy tutorials, if you want it to go a bit further, you may check the Galaxy events and see if there is any training upcoming. I pointed to the GTN, I pointed to Galaxy health and bug reports, so if people don't know how to create and are unsure of what to do, I told them to check the issues page, which are already known issues. The Github issues, the Galaxy health forum are not, if they haven't found their answer in any of those places, they may create an issue. I pointed to the mailing list, I pointed to the Galaxy publication library, if there is any other curious person that may want to know what the Galaxy community is doing, step number three is your place within the Galaxy community, so if people want to wonder what the Galaxy community is, they are part of the community, but also I pointed to the already established Galaxy communities. I have added Galaxy communities of practice in the Galaxy page, go to Galaxy slash communities, we have the regional communities, and then the communities of practice, which are topic, kind of base, ecology, metabolomics, climate, I have added the interacting communities with Galaxy via open life outreach, via conductor, Kanda was already there, but outreach and an open life science weren't. The Galaxy mental network is also here, you see, if they don't can't find themselves there or don't feel identified, I pointed to the setup your own community page, which also has a path that they should follow if they feel like they don't find themselves, which is learn the basics about Galaxy, so they go to the get started page, and then they go to the Galaxy mentorship network, they should probably learn about the development, I pointed to that also, they should get involved, so they should reach out to the working groups, they should participate in the Galaxy events, they should chat in the lobby of either a matrix, and also they could set up a mailing list when starting their own community. It has a dos and don'ts list also, so this is basically mistakes they can avoid of other communities that have already created the communities on which they knew, so they should take the time to learn the basics about Galaxy, ask if a tool for what you need already exists, request your tool to be reviewed, don't be a lone wolf, and the steps on when you happen to need a tool, make it, write the training, set up an event, avoid setting up very specific tools and avoid hearing, not hearing feedback. Number four is take part and contribute to Galaxy, so if you have already followed these steps, you can then start contributing, which points to the contributor page, you can contribute with all training materials, ideas, hosting events, helping others, and also starting your community. You can go to the working groups and participate, and you could also go the Galaxy Mentoring Network, which is the page the other interns have created. This has basically been my work with outreach. I would also like to give some of the expected benefits, basically, for our community, for the overall Galaxy community, this will speed up the onboarding process by having newcomers easily read the Foundation of Galaxy, it will increase and sustain participation and interest in the working groups, and it will boost diversity with more contributors and also communities. For mentors, which is basically, it could be mentor for the Galaxy Mentoring Program for outreach, but it's also experienced people inside the community. It's a solid place to provide more fulfilling questions and issues to create richer communications between mentees and mentors, and it will sustain participation with less hand-holding and less stress. And for mentees, it's the same case as before, mentees can be mentees for the outreach, the GMN, or also newbies or newcomers, people with less experience. It will easily digest and get to know Galaxy, it will avoid initial burnout of the learning process, which in the outreach initial period was quite a bit. It will make more relevant contribution and questions. It improved chances of being selected for those that want to participate in outreach, and it will create better matches for the GMN. Thank you for your time in being in this Zoom, and if you have any questions or suggestions, I'm open to those. Thank you, Pia. What's the right comprehensive overview of what you have done? So what question do you have for Pia? Yes, Eli, I saw a hand going up. Sorry, that wasn't my hand, various, I was clapping. But I will say, I don't have any particular question, but I am fairly new to Galaxy and trying to get it off the ground in a new community and material science. So this all looks like really interesting stuff. So thank you. So that's great. You can give us feedback. You will be able to give feedback on what has been done, because it's not like a dead document. Pia, you mentioned it several times, it can evolve. I was going to ask if you can talk a little bit more about the matrix conversation being too professional or like that kind of vibe. Are there other things that we can do in those channels to make them more approachable, do you think? When we approached the mountainous, we asked this and they said people go there with wealth from questions after investigating and exploring the galaxy. So we weren't sure if this was especially made for outreach, like if you are just a newbie without knowledge of anything basically related to Galaxy or programming or such. When they went to the leader channels, if you go back and back and back in the chat, you just see very wealth from questions, which is good because people go with very wealth from questions. But maybe if you have not such a wealth from question, not such a profound question or a very specific question, people may not feel inclined to make it. It's a bit not overwhelming, but it may stop people from asking questions. But we don't know if these people don't end up asking questions. I wonder if this has to do a little bit with how we've broken out specific channels for sort of every niche, right? So when we had one big channel, just a dev IRC channel that everyone talked in, there was always sort of just chatter and banter and it was a lot, right? So we broke things out for good reasons. But I wonder if there was just sort of more, I don't know, is the lack of informal conversation in some of these channels that's precluding people from jumping in something we should consider in sort of fragmenting our communication channels more in the future? I think it's a good idea to have and to try, both in this get started page and in other places inside the hub. We point that they shouldn't be afraid to ask questions, even if they feel it's a dumb question, if they feel it's a question they should know, they should still ask it. But I don't think it's a bad idea to maybe have a more complex channel for complex questions. Do you mean divide channels in what example of the backend channel? Right. No, I was saying we should be hesitant to divide things into more channels potentially. So like the UI UX channel is the one I spend the most time in. Last week there were days, multiple days when there are no messages. So you don't want to be the person to jump in and sort of break the silence I guess and ask something weird. But if it's a channel that seems active and just sort of people are just talking, then it's not weird to just hop in and answer questions. I'm wondering if we should, I mean, maybe it's just that we need to point more people towards the lobby and dev and have more casual conversation in those channels, saving the workgroup specific channels for just sort of workgroup business or I don't know, I don't know though, because then that's weird. That's weird too. So I don't know. I don't have a solution. I'm just going to say that's definitely been a point of confusion for me where you have these groups that are labeled as working group tools, working group UI UX. I don't know if I count as being part of the working group just because I develop tools, for example. And so I don't know if that's an appropriate place to ask my questions. And that's where I've been asking because I haven't found anywhere else to ask them. But it's always this back of my mind, is this the right place? Do I belong here? Sort of question. So would these simple things already help or not? So this was more or less a concrete question. How can we avoid that because everyone is welcome in these working groups? So would it already help if we put that as a channel description, as a channel header, that everyone is welcome here and so on? We discuss this and not all people may see that header. And Peter has a good tool that element doesn't have that upon joining a new channel, you have like a welcome or a warning pop up. So it could point to the get started page or it could point to this, don't be afraid to ask questions or whatever, which we scratch since element doesn't have it. So it depends on where people will be joining from. Is that something you could do with the bot? I know you scratched the bot, but you could have the bot sit in channels and when people join it could just send them a direct message or something and not spam the channel, I mean, or you could spam the channel and say, hey, everybody, welcome Asunta to the UIX channel or that kind of thing. Just to, I don't know, maybe that's an option. We had this idea that it would either each person joining or it would send this message every 24 or an x determined amount of hours. But the people answering those questions were like, I will get this notification if it's in the chat. So I will think, oh, somebody's someone is asking a question and they will see that it's the bot or maybe in the weekends, they will see two messages at the same time and it will be the bot. It could be sent privately, I think so. But it will, they would have to, I remember I investigated this, they would have to accept these people, this bot, sending them this message. So they won't get the message. So it's not the the overall BL solution. In element, you have to accept even, I don't know, if I go in element and want to send you a message element will be like, it's wanting to send you a message, do you understand? The bot is the same. They decline once, the bot will never send them a message again. So it's complicated. Wait, and what was the, so if the bot just each time a new person joins for the first time? We don't hear you super well or is it only me? He's a bit low. About now. This is what I was just thinking about. If the bot just every time a new person joins for the first time just puts it in the chat, that would be too much. I think this will have to be discussed with each channel. I think some will, maybe the lobby will like it or maybe GTN will like it and maybe developers or any other channel won't. Yeah. I was thinking the lobby, it might be too much because there's new people, probably new people all the time, but in the working groups. Yeah, how many people are in there? So the working, the UI UX group has, what does it say, 19, no, 40, 40-ish people in there, something like that. I feel like I don't notice new people joining in working group chats all that often. Yeah, they're fairly stable, right? Yeah, 49 people in UI UX. I personally, I don't think it'd be a, I'd like to have a message when someone joins UI UX at least. I don't think that would put me out. I don't want it repeating every 24 hours. That'd be weird. Yeah, just the first time like this is, yeah, let's people there know like this is a new person, like, you know, be nice. And also, like, you can put a message in there that like, you know, everyone's welcome to chat, not just official people, whatever. How much work, I mean, did you have the bot sort of running? I mean, I would be welcome to, I'd be happy to volunteer the UI UX channel for if you want to just test out the bot and, you know, see how it works. I'll back you on that if you want to just try it out. Okay, I had it running. I had created my own room. So I wrote the script for the bot. I had to create another user because the bot equals one account, basically. If I run the script, a message would be sent. So I would have to grab the element or matrix idea. I don't remember like the idea of someone joining. I could try it. I think that'd be fun to try. Yeah. Or we could try it in the Goat channel, since it's even more friendly. Okay, yeah. Okay, let me investigate. I can try it. I will write it down because I easily forget it. Yeah, I think that'd be super cool. Thank you. So I have one comment about this communication and the chat and so on, because that's how Eli was mentioning that one never knows where to ask the question or which question is appropriate for each one of the channels. And Pia, you have in this, in this started gets a section for mailing list. Should we maybe name that to communication and have subsection sections, one for mailing list and another one for the different matrix channels and describe what is the content that is expected that you comment on those? Do you think that would be too much? I don't think it would be too much. It would make it clear, but I think as maybe Eli mentioned, like, we describe the tools working group is for people related to tools and such, but he created maybe a couple of tools and he's wondering, am I someone that could be in the working group? I think it's not so much the topics that would define the working groups, but people feeling identified if they could ask in the working group. I think in the lobby channel, people tend to find the words where you should ask. I'm not sure if we should find the lobby channel itself. So if you have any question or if you're unsure where to go, go to the lobby and then they will punch you. But I'm not sure if that's the best approach. Yes, in particular with the working groups, I can imagine that struggle when you say, okay, do I, it's just people that are working full time on the project. Do I really have a place to us there or can I say something or even join the room? So somehow to make clear that this is a place for you to ask if you're working on a type of activity. Okay, I think a warning like that, even if you are just, is anybody welcome, even if they are working just on one tool or one specific thing about UI or web related to Galaxy, then they could go to UI, UX channel or any other working group, even if you're just making a tiny change. No, no, I just wanted to, because I think Pia has tried in the starter kit in the working group section to make it more welcoming in the sense this is not for like professional people paid in the working group, this is open to everyone. But do you mean there to add even in the description of the working group? Or maybe as a communication channel, we have on one side mailing lists on the other side, we have chats and described that we have different channels in the different spaces. But the problem that I see there is that it's going to be hard to maintain and if we create new channels, we need to be editing, but I guess that's fine. But maybe say what is expected in each one of the channels so that people feel that their questions is legitimate for that place. Okay, I think the working groups item in the get started page reads in points if you're interested in a particular area within Galaxy, then you can connect with a working group. The PinterDarkitka project Gitter channel Google Drive, so it now they read about it and with Eli's feedback, I realized it's if you want to know what the working group is working on, but not the fact that you may be part of the working group as developing a tool, for example. It's more so investigate what they are working on, and that's it. It doesn't feel open to go and ask and participate and such, even though it's in the take part and contribute to Galaxy step. I'm reading if the working group page also has kind of a mention to that, like don't be afraid to join in on us, but it just points to the current set of the working groups. And it is confusing also in that sense. I think it could be you see it in the get started page and also in the working groups page. Yeah, I would agree with that. Just like a couple of lines saying you're welcome to ask questions relating to these subjects in these working groups, even if you're not sort of formally like you're not part of the group that's like leading it making like strategic decisions, you're just developing stuff that's going to be added in hopefully. Yeah. I did feel the same feeling upon joining a working group because there aren't many people like the lobby has lots of users. So it gives the impression that the lobby is more welcoming and their working groups is more private like UI and UX has less than 50 users. So are those 50 users part of Galaxy itself? And I may not be part of it. The UI UX working group has 26. I think that's a bit scary if you aren't used to it. And if this warning isn't present also. I find reading what the working groups were and investigating. I thought I was spying on people working in Galaxy and that I was sort of that I could ask. I thought Galaxy is very open about people working there and you can see their chats and you can see what they are doing. Any other questions or ideas related to this? I want to say one thing. First of all, I really like having this newcomer guide to Galaxy. I agree that it can be really overwhelming and it's a huge project. But I wanted to mention, I feel like the title of the button on the home page gets started. I feel like that's usually the get started link on projects is usually like here's two or three steps to get it running or something like that. But I would suggest maybe like Galaxy guide or some wording like that maybe. Okay. I'm not sure. I like the idea, but I'm not sure if that point of view is more programmer based. If I'm a programmer, I wouldn't get started with installing and running my local version of Galaxy. But if I'm not someone that programs, I don't have that idea in mind. Even for non-programmers, if you're looking at youth Galaxy, get started would be like here's three servers you could use. A very brief pointer to if you just want to get going here, go here. I just thought that if I was visiting a project the first time and I saw that button, I'd click it and have a different expectation. But maybe it's just me. Maybe get started with our guide. Maybe join the community because it's more a way to join, right? Even when you're in a new camera you want to be a community lean. But there isn't just a place for community people. It's for anybody. I mean, the point is what you really wanted here and everyone wanted is to have a place where if you go on this page you know this is where you should click. Yes. Okay. But yeah, it's true. It's maybe get started. It's not the right word. But I don't know what, but it's a good point. I think this is something we need to put more attention to with other communities, open source communities to see what they, I have found some communities that have this kind of guide for newcomers. I don't remember what they wrote, so I will revise and see. But yeah, it is a good point. Or like a newcomer corner or something like that or like. Galaxy 101. I think that's already taken. But it's a good point, I think. Yes. I will revise it. Anything else that someone would like to address? I'm very interested in what Eli will find. Yeah. In this. Because it's, you know, examples of real newcomers that will not find their discipline there. So how is it going to be for you? That could be super interesting to know. Yeah. Yes, please give feedback. Yeah. Yeah, I'll let you know how we get on. If there's something missing, maybe or something unclear of the working groups chat. I don't want it to feel like any of what's written there is just for pros or the people that know it for everybody. Okay. If that's all the thank you so much for joining. Thank you all for your feedback also. I'm happy with all the feedback. Thank you. Good ideas. And thank you to Diana for being the best mentors I could have ever had. Because we were the only one. You didn't have any other ones. This is where we are the best. And because we are online. Yes. I just wanted to raise the fact that now we will have another outreach session. I don't know around. It would be very because now I think the Galaxy community has chosen to have like developers in this round. So it would be very interesting to get also your feedback after or during the round. If anything was like useful or not useful and how we can really help to onboard new developers. Because maybe that's an emphasis we haven't put much on this. I don't know if you have any feedback during the like the contribution phase. And you see that systematically the outreach she are asking the same again and again question and they are getting lost again and again with the same thing. Maybe this is something we can improve. Yeah. They will probably get stuck with something very specific. Hopefully not. But if they find a stone in their path I would like to address it. I tried to make it as open as possible. This get started guide. I. I think developers will go towards the description of the projects. Hopefully in the repositories. That's pointing in the working groups. But I know that that's something that you will get to experiment. I think soon like it's in January or so. So the next one. Our next month in the contribution period and the internships in general. Yeah. So we'll see. Yeah. I don't know. Otherwise I would like to thank everyone and especially Pia for doing the work. The hard work and for everyone else coming and giving the feedback to Pia, which I think we are very, very helpful. Thank you. Yes. Thank you, Pia, for all the work and thank you, Anne, for being a great comment or two. Yes. I'm very good. Yes, you are. Thanks a lot. Thank you.