 Okay. Hello. My name is Mattausz Kuzak. I'm a committee manager at the Netherlands eScience Center. And at the eScience Center we work with researchers and we develop research software to help them move forward their research that requires some more expertise in research software development, data handling, efficient data computing. And over the past years we have developed over the 100 research software packages. We have published over 100 research software packages. But we do realize we actually don't have that many contributions from the outside of the projects and not many users from the outside of the projects. We collaborate closely with the researchers that we already know that we work in the projects but there is not much interaction with the outside. And that's something that we would really like to change and I will be talking about it today. And this is, my perspective is how can we improve it for research software but actually the things that I will be talking about I think can apply to other software. It can also apply to other things not only research software but some things in the research culture and how do we perform research and how do we collaborate. So why open and inclusive? First of all I think it's the right way to do it but also being more pragmatic we want to attract more diverse group of contributors and we also want to have more diverse group of users and people who work with our software. So I've been thinking about how we can improve it and I've been lucky enough to be involved in a lot of amazing projects in past years and I want to give some summary or lessons learned from my interactions with those projects, communities, initiatives. What I have learned from what I really appreciate about what they're doing and how that can be applies to improving the to making research software community and software community collaborative communities more inclusive, more open and leading to my more diverse communities. So first of all we do always like we start with encouraging open open software, open source software but this is definitely not enough and I think we're all getting better in developing research software and being more open using open platforms and the more projects add her to standards they provide very good readme files, they provide contributing guidelines, they also implement code of conduct and there are more and more resources available how to do it, we can learn from each other and this is very important. For example on github you can now see you can go to the insights tab and you can learn how your project is doing, does it add her to standards, community standards which are there and how you can improve those things if you're missing something. You can learn how can you add this information, how can you help your contributors interact with your project. There are also projects like chaos which develops the metrics that measure community activity contributions and help of your community and I think like this is really the the step in the good direction because you did at the same time I realize in the work I'm doing that this is really not this is the passive way it's there if people find your project they will see it but it does not necessarily mean that if they see a beautiful very well written readme file in your project that's enough for them to join the project and feel comfortable and feel invited to join the project. What can we do better? I think we can be more proactive in what you're doing with attracting and interacting with potential contributors and one way of doing it is participating in sprints and I will have some examples not every sprint is equal I have some good examples but sprints in general are a very good way to pitch your project to make it more visible but also to infect others with your passion for your software for the for the project that you're working on and also just for like starting this human interaction which I think is it's very important we shouldn't be forgetting about it. So good examples are Biohackathon European edition there's also Japanese edition that haven't participated in so I cannot say anything about it. Last year I have participated in Bioinformatics open source conference co-fest which is stands for Collaborative Festival E-Life Innovation Sprint and in the past years I also contributed and collaborated in the Mozilla Global Sprint. So these are the the examples of the sprints that allow you to submit your project and then you can find contributors to your project and work with them. And there are also other similar events I think the nice example is the Turingway which is about the Turingway book which is the guide to open and repressible research so I have to give the shout out to Malfica who is in the audience somewhere there. If you if you don't know about it you should check it out. The Turingway book dash that the sprint that I have participated early this year was focused on helping people to contribute to the Turingway and even though this was about the project itself the Turingway project it really was about helping new contributors bring their own ideas into the project and developing those ideas and then becoming part of the community. And of course you can organize your own sprint. And so before you join the sprint I think it's very important that you think about what are the different ways that people can contribute to a project and what are the different skills and expertise that you're looking for and being able to describe it and to be able to attract the people who can contribute to the project but also and you want to be able to accommodate people with different backgrounds and with different expertise so you you want to be able to support them in that if there might be contributors that not necessarily use github or they don't know gith how do they still are valuable contributors how are you going to support them but also people have different styles of work and you have to think about in advance how to support this how maybe there are people who are not they're not comfortable working in in large spaces with a lot of people with a lot of noise you can talk to the organizers maybe there is a silent room that you can they can work in or maybe you can bring the headphones and provide the headphones so that they can work in the way that they feel comfortable in because there we all have our different styles of work and that should be supported and also I think it's important that the event organizers also think about it and the the events that I have been participated in they really emphasize this and they make the project owners think about it in advance how they're going to accommodate contributors the next step when you find the contributors to your project is doing the onboarding onboard them into your project and I think it's very important not to forget how important it is that the human interaction and that the best documentation and that the best processes will not replace that so think about how you can contribute how you can onboard your contributors because most likely contributing to your project is much more complicated than you think it is and so you can learn with them what are the barriers to contribute to your projects what what are their experiences and how you can adapt the processes to make it easier and one example is from the carpentries community the maintenance onboarding project so the you can so the next step is supporting and helping the community grow and that's you can do it with the like increasing the opportunities to interact of interactions with community and with the project leads and who can organize community calls and through those calls you can meet and get to know your contributors which is very important you can learn about their challenges working with the project and also you you will again learn how about how they work and I have two examples of that one is the carpentries discussion sessions so I have been involved for a few years now in the carpentries but actually through the discussion sessions there are kind of community calls organized by the carpentries back then it was the software carpentry organization and through participating in those calls I have became the part of the community I learned more about what the community is doing what are the projects how I can contribute to them and that helped me grow within this community and then the research example is the Turingway collaboration cafe and I also mentioned it here because this is a great example of learning how people are working and helping people finding the way in the project so the the Turingway Malvika and Christie who are leading the project are organizing regular online meetings where you can come in you can say hello you can discuss potential contributions contributions to the project you can also collaborate working during so it can be a working working session when you can work either from the from people from the project or with other contributors on something that you would like to contribute so I really like that because I've been recently joining those calls a few times when I think about something that I might have I think that I can have that I can contribute I can join in the call I can discuss it and see how the my contributions can fit in and also how we can make it more usable within the project and then that can be actually extended into the more structured mentoring program and mentoring is very important to help your community grow to explore the opportunities within the project and mentoring can be organized through the community calls but I think it's also worth considering more structured mentoring with the mentoring teams with mentors parent mentors and mentees and it also helps the the participants to adopt the growth mindset everyone is learning in those projects it's the contributors are learning the experts are learning the project pis are are learning there and it also helps with fighting the imposter syndrome okay so how this is a lot of things then this this requires a lot of skills and so and very often the people who developed research software are researchers who have been trained to work in the wet lab or they have trained to analyze data but they have not necessarily been trained in working with the communities with building communities managing them and interacting with people and leading them so I wanted to give a shout out to two projects that have are still running and one is open life sciences and the other one is life innovation leaders and they provide mentoring and training of on open science related topics and I think what so I've been participating in this program and my takeaway is that that's equally important that the the expertise that is provided and the learning experience it's equally important as gaining the connection with other participants with other mentors with other mentees and with mentors and so I think that that's one of the ways to approach this that's how we can learn and one last thing we have to remember is a journey so we have to embrace the growth growth mindset we have to keep learning and we're not necessarily going to get it right from the beginning but we can improve and we should keep the conversations because if we want to improve we have to talk to our contributors or potential contributors and learn about what is their experience and also the technology is not everything it's there for to help us but we it cannot replace the human interactions okay thank you and if you have any questions feel free to ask yeah so thank you for that we do have a few questions and just for those that are joining we also have a slack channel a slack workplace that's available and there is a slack channel set up for csv q&a and so Matias will be available there to continue the discussion after this yeah so if you if you haven't already signed up for that slack channel please go and do that now and then you'll be a bit able to communicate with all the speakers throughout the event so yeah so I think some of the questions that were coming in were really about learning more regarding some of the initiatives because it's like I mean one of the great things about the presentation is how you're leveraging other initiatives like the Carpentries or the Turing Institute for elife sprints and really just trying to figure out more I think one one big thing was just learning more about sprint-based work like book sprints or book dash these types of things I'm familiar with the book sprints model and the book sprints organization but maybe you want to just explain a little bit more about how people could learn more about that a process about how to run those or yeah I don't have a good yeah so I think you should talk to people who organize those those events so you can talk for example to Emmitsank who is also there in the audience and Don Slack who organized the elife sprint last year and she organized the the sprint this year talk to Malvika who organized the book dash I think that it's a steep learning curve to organize yourself the sprint but you can start small you can you can organize I mean the sprints most of the sprints that I mentioned are like multi-project sprints but you can start with something around your person that's probably what you'll be interested in yeah um in the first place so it doesn't have to be big you can you can organize a small event you can even start with with like a informal cafe event where we even invite people to come and discuss the project and see how people can contribute although we cannot meet in a cafe for now but maybe you can organize online meeting we're told yeah and I think I actually put a link in the chat to the next global sprint so or the elife sprint sorry um and so there is information there for people who are interested yeah I would like to link to the to this another presentation here in the chat in a second oh great thank you very much yeah thank you um and we can continue the conversation over in Slack um and as Nitya said all of the sleds for all of the presentations are being presented are posted up to Zenodo so we'll be sharing those out as this be put them up so thank you Matisse thank you Phil and thank you everybody for joining the um first uh session zero of the csv v5