WEBVTT 00:00.000 --> 00:13.280 OK, guys. Thank you for being here. So just a technical note. I don't know if you've seen 00:13.280 --> 00:19.520 but I actually read the talk that was planned for now at 4 p.m. I've been consulted by the speaker 00:19.520 --> 00:25.960 and for trying to figure out how to make it today with us. So we placed it by the 00:25.960 --> 00:31.960 Ok team, the Open Research Organization team panel. So we'd like to take those 15 minutes. 00:31.960 --> 00:38.520 We have heard of us to just discuss about what is like to have this space of discussions 00:38.520 --> 00:45.720 about academia and open source software and any open data practices. So the first 00:45.720 --> 00:51.080 goal is to show you what the team is like. This is a bunch of us. So we've been doing that 00:51.160 --> 00:57.480 for five years now, I think. And we have new people coming in every year. So the first 00:57.480 --> 01:03.160 very message I have to give to you, either you're here in the room or there on the web. Please consider 01:03.160 --> 01:11.160 joining us. It's quite fun to do. It's not a lot of work, but yeah, you need to do some work on 01:11.160 --> 01:20.280 reviewing and also communicating about the CFP called for proposals. But yes, that was the first thing. 01:20.600 --> 01:27.640 And the second one is what is your feedback or review anything that you have in your mind about 01:27.640 --> 01:33.320 what we're doing here. If you have any comments on what we do and how we can do that better, 01:33.320 --> 01:38.440 it will be quite the time to take the mic and share with us. I don't know if you are other 01:38.440 --> 01:48.440 people in the team want to say something. I'm totally improvising this. So does anyone has any 01:49.400 --> 01:55.080 comments or something to say? I heard it over there. We take the love. What? 01:58.120 --> 02:10.040 The question was, we love what you do. Thank you. Thank you. I'll give you the mic. It's 02:10.040 --> 02:28.040 computer. The question was, how we are doing? I'm okay. I had a good night asleep, which is 02:28.120 --> 02:35.480 pretty rare. But yeah, some of us are. You look great. I'm doing the 02:35.480 --> 02:40.680 the Macedonian coverage and it's intensive. Yeah, I was drunk yesterday, I see. 02:43.000 --> 02:50.360 No, there is not much of work in general, but there is quite a lot to take into account. 02:50.360 --> 02:53.640 Let's say. So yeah, a much has been covering life tweeting, life, 02:53.640 --> 03:02.360 must do the event and that's quite a lot of work. How are you? I'm okay at the moment. I think 03:03.080 --> 03:11.000 a few hours in the future. I might sort of crash and fall asleep. But I'm running on a 03:11.000 --> 03:18.200 adrenaline. It's my first year helping, I presented at the death room last year. So I think to 03:18.680 --> 03:24.680 add, it's been quite fun. It's not a lot of work. There's a lot of people 03:25.720 --> 03:30.440 so I get splits. I think to be fair, Sarah and Matt, who do most of the work. 03:32.760 --> 03:39.480 Yeah, so I'm just trying to do bits and pieces around the edges. And yeah, see what's fun. 03:39.640 --> 03:46.840 Okay, something like that. Anyone else has to do this? If you consider joining, 03:47.400 --> 03:51.080 do you have to say this? Because we are many, it's not a lot of work. And if you have, 03:51.080 --> 03:56.840 if you need to miss any meeting, you're never really necessary. That's really important. 04:00.840 --> 04:05.560 But it's really good to have a lot of people involved when we have to assess all the proposals of 04:05.640 --> 04:10.600 everyone because, you know, it's always better to have more eyes on all of this. 04:12.120 --> 04:15.800 Yeah. So it's good if we are even more. That's what I want to say. Yeah, especially for 04:17.160 --> 04:23.480 opening to even more context in different disciplines in academia or different kind of technologies. 04:23.480 --> 04:28.760 And it's because, of course, one of the main role you will have, what we have in 04:28.760 --> 04:35.720 no teams, just to try to track people to go, to come here and to speak. So it's also nice of a nice 04:35.720 --> 04:41.640 balance of any kind of personality or backgrounds. And that's also why we need new people, 04:41.640 --> 04:51.320 because we've kind of exhausted our close network. So we also actually unlearn some good things 04:51.320 --> 04:56.840 that we had learned in the past. We forgot to put a pose in between talk this year. And you might 04:59.000 --> 05:08.360 notice, yeah, it's a bit tough. I mean, I realize this today at 10.30. Anyone has any, 05:08.360 --> 05:13.640 how are you guys doing over there? Victor is actually working? Yeah, one of the 05:13.640 --> 05:20.280 objectives. So we have at this one technical problem, meaning one of the speakers have 05:21.080 --> 05:25.560 developed a picture. So I'm fixing that right now, but apart from that, oh good. 05:25.640 --> 05:33.640 See, we fixed people's problem. Do you want to comment on anything? The question was very 05:33.640 --> 05:38.520 simple, if you want to repeat. My question is for the public, just to add an idea with academia 05:38.520 --> 05:45.160 related here, because it's a kind of specific devroom, because a lot of people coming from academia 05:45.160 --> 05:50.360 related to academia and I think it's a mix. And so it's very nice to be here and to discuss 05:50.360 --> 05:56.440 as a bother of the different fields. It's very, very interesting to hear everything you presented, 05:56.440 --> 06:03.160 all of those worry presented and to hear the discussion. 06:03.160 --> 06:24.440 Okay. I can give you, I wanted to ask how many submissions did you have and how difficult 06:24.520 --> 06:29.960 was it to choose? And do you have any criteria on which you selected the talks? 06:35.480 --> 06:40.520 Do you remember how many were there on the 1986? I'm, I remember playing okay. 06:41.480 --> 06:47.320 So last year we got really a lot. We got like around 80, 90. So it was very hard, for example, 06:47.320 --> 06:51.960 to make a decision. I think this year we got a bit less around 54 to something like that. 06:52.840 --> 06:58.360 The nice thing that we have is because we're organizing an unofficial devroom online, 06:58.360 --> 07:02.440 we can always propose to the very nice talks to come also to the online session. So they're not 07:02.440 --> 07:07.800 completely declined, neither. So that's one good way of doing it in a way. Because I mean, 07:07.800 --> 07:12.200 the extraordinary thing I think that every time it's very, very hard to make a decision because 07:12.200 --> 07:18.520 all the talk proposals that we get are extremely good. I don't know if there's any way that we 07:19.160 --> 07:24.840 just a, just a, just a, just a criteria question. It's, it's a, it's a tough one, but I actually, 07:24.840 --> 07:32.680 sorry. So the main criteria is, it's really simple. It is, it is in scope with what we want to 07:33.320 --> 07:39.320 to speak about, which is like basically open something into a research something. So this 07:39.320 --> 07:44.120 is basically to main words of, of the, of the, of the devroom. So, but you try to to keep that 07:44.120 --> 07:48.360 seal that everyone is open source. And it's actually not the case. We have proposals that are not 07:48.360 --> 07:55.160 open source. So we refuse to. Yeah. And, and a, and a, a submitting a talk, saying that this tool could 07:55.160 --> 08:00.840 be used in research is not enough. For instance, it, it, it, and we really like we like to push 08:01.560 --> 08:06.840 talks that has a little bit of reflections about what does it means, what, what is, what does it 08:06.840 --> 08:12.440 do to developing all the research to, to do the other thing, right? So this is like a friction, 08:12.600 --> 08:18.040 an interaction between the two activities that are interesting for us, I think. I hope it is for 08:18.040 --> 08:32.040 you too. We have a question. Yeah. So I come from research and then I move to the university library 08:32.040 --> 08:40.360 space to do training and we try and push for open, open source tools for doing that analysis 08:40.440 --> 08:47.560 and also some things. I'm wondering if you have in the panel an opinion on how do we promote 08:47.560 --> 08:52.600 those tools best, how do we get people to use them? Because there's a very on the proprietary side, 08:52.600 --> 08:59.000 there's a lot of, you know, marketing funds and there's also a lot of culture that stays in academia 08:59.000 --> 09:05.800 and you just use whatever tool the person who, you know, your, your colleagues use, right, 09:06.120 --> 09:12.120 or the oldest person in the room uses. So then it's a bit, you know, two-fold questions. 09:12.120 --> 09:18.280 How do we push for using those tools to improve open research practices, but also how do 09:18.280 --> 09:23.480 we like them most sustainable? So they're still around and maintained and get better over time. 09:24.680 --> 09:25.880 Big questions, sorry. 09:26.200 --> 09:39.800 One idea that comes to my mind, there is a, there is a product that is called 09:41.960 --> 09:47.720 RSD, research software directory. This is developed by the Netherlands eScience Center. 09:48.440 --> 09:54.760 And what we do with this tool is that is a directory of research software in which you can see 09:55.720 --> 10:01.480 what is the product and what is the intention, what are the capabilities and also how is maintained 10:01.480 --> 10:07.320 and you can cite it, you can track it. Yeah, but it's really focused on research software directory. 10:07.320 --> 10:11.400 The thing that I do now when I start a project with the research areas, have you looked in the 10:11.400 --> 10:17.160 research software directory, if there is anything that may be adapted for your project? And I think 10:17.160 --> 10:23.320 just having everything a little bit collected there helps a lot. So this is, this is one side 10:24.200 --> 10:30.600 of two answer this. And then the other thing that researchers have tendency to do is they 10:30.600 --> 10:35.400 want to build everything from scratch. They do not want to reuse things. So this is also a 10:35.400 --> 10:42.120 culture that I think we, if we can, need to change, just reuse things, don't try to reinvent 10:42.120 --> 10:52.520 them, we'll ever tend that you have an area. Yeah, they just, just kind of to conclude and I've 10:52.520 --> 10:59.480 been a student as a non-ropolologist, the community we are, it's a long-term battle, it's complicated. 10:59.480 --> 11:05.880 I don't have the time to have the discussion, but it starts with having that space. So having 11:05.880 --> 11:11.560 another space is where as a community we can discuss of the actually quite tough position of 11:11.560 --> 11:17.160 whoever that's open source software in academia, but actually many people are working on this 11:17.160 --> 11:23.560 finding solutions and so on. There is no single bullet for this, but we need to be better 11:23.560 --> 11:28.680 of a network and to coordinate better and to know each other better. This is a good place to start, 11:28.680 --> 11:33.160 it's not enough, you know, very starts like this. 11:37.800 --> 11:46.760 So hi, very important question and it's so important that my organization OLS, we're actually doing 11:46.760 --> 11:54.520 this project in partnership with the digital research academy and it's basically to do research, 11:55.080 --> 12:02.840 find out how researchers, that's a lot of research in one sentence, but how researchers can better 12:02.840 --> 12:09.160 markets the work that they do and it might be helpful to keep an eye on that project is called OSPAC 12:09.240 --> 12:16.920 or SPAR cake or SPAC so it will be useful to answer your question in details in a couple of weeks 12:16.920 --> 12:21.160 months.