OK, guys. Thank you for being here. So just a technical note. I don't know if you've seen
but I actually read the talk that was planned for now at 4 p.m. I've been consulted by the speaker
and for trying to figure out how to make it today with us. So we placed it by the
Ok team, the Open Research Organization team panel. So we'd like to take those 15 minutes.
We have heard of us to just discuss about what is like to have this space of discussions
about academia and open source software and any open data practices. So the first
goal is to show you what the team is like. This is a bunch of us. So we've been doing that
for five years now, I think. And we have new people coming in every year. So the first
very message I have to give to you, either you're here in the room or there on the web. Please consider
joining us. It's quite fun to do. It's not a lot of work, but yeah, you need to do some work on
reviewing and also communicating about the CFP called for proposals. But yes, that was the first thing.
And the second one is what is your feedback or review anything that you have in your mind about
what we're doing here. If you have any comments on what we do and how we can do that better,
it will be quite the time to take the mic and share with us. I don't know if you are other
people in the team want to say something. I'm totally improvising this. So does anyone has any
comments or something to say? I heard it over there. We take the love. What?
The question was, we love what you do. Thank you. Thank you. I'll give you the mic. It's
computer. The question was, how we are doing? I'm okay. I had a good night asleep, which is
pretty rare. But yeah, some of us are. You look great. I'm doing the
the Macedonian coverage and it's intensive. Yeah, I was drunk yesterday, I see.
No, there is not much of work in general, but there is quite a lot to take into account.
Let's say. So yeah, a much has been covering life tweeting, life,
must do the event and that's quite a lot of work. How are you? I'm okay at the moment. I think
a few hours in the future. I might sort of crash and fall asleep. But I'm running on a
adrenaline. It's my first year helping, I presented at the death room last year. So I think to
add, it's been quite fun. It's not a lot of work. There's a lot of people
so I get splits. I think to be fair, Sarah and Matt, who do most of the work.
Yeah, so I'm just trying to do bits and pieces around the edges. And yeah, see what's fun.
Okay, something like that. Anyone else has to do this? If you consider joining,
do you have to say this? Because we are many, it's not a lot of work. And if you have,
if you need to miss any meeting, you're never really necessary. That's really important.
But it's really good to have a lot of people involved when we have to assess all the proposals of
everyone because, you know, it's always better to have more eyes on all of this.
Yeah. So it's good if we are even more. That's what I want to say. Yeah, especially for
opening to even more context in different disciplines in academia or different kind of technologies.
And it's because, of course, one of the main role you will have, what we have in
no teams, just to try to track people to go, to come here and to speak. So it's also nice of a nice
balance of any kind of personality or backgrounds. And that's also why we need new people,
because we've kind of exhausted our close network. So we also actually unlearn some good things
that we had learned in the past. We forgot to put a pose in between talk this year. And you might
notice, yeah, it's a bit tough. I mean, I realize this today at 10.30. Anyone has any,
how are you guys doing over there? Victor is actually working? Yeah, one of the
objectives. So we have at this one technical problem, meaning one of the speakers have
developed a picture. So I'm fixing that right now, but apart from that, oh good.
See, we fixed people's problem. Do you want to comment on anything? The question was very
simple, if you want to repeat. My question is for the public, just to add an idea with academia
related here, because it's a kind of specific devroom, because a lot of people coming from academia
related to academia and I think it's a mix. And so it's very nice to be here and to discuss
as a bother of the different fields. It's very, very interesting to hear everything you presented,
all of those worry presented and to hear the discussion.
Okay. I can give you, I wanted to ask how many submissions did you have and how difficult
was it to choose? And do you have any criteria on which you selected the talks?
Do you remember how many were there on the 1986? I'm, I remember playing okay.
So last year we got really a lot. We got like around 80, 90. So it was very hard, for example,
to make a decision. I think this year we got a bit less around 54 to something like that.
The nice thing that we have is because we're organizing an unofficial devroom online,
we can always propose to the very nice talks to come also to the online session. So they're not
completely declined, neither. So that's one good way of doing it in a way. Because I mean,
the extraordinary thing I think that every time it's very, very hard to make a decision because
all the talk proposals that we get are extremely good. I don't know if there's any way that we
just a, just a, just a, just a criteria question. It's, it's a, it's a tough one, but I actually,
sorry. So the main criteria is, it's really simple. It is, it is in scope with what we want to
to speak about, which is like basically open something into a research something. So this
is basically to main words of, of the, of the, of the devroom. So, but you try to to keep that
seal that everyone is open source. And it's actually not the case. We have proposals that are not
open source. So we refuse to. Yeah. And, and a, and a, a submitting a talk, saying that this tool could
be used in research is not enough. For instance, it, it, it, and we really like we like to push
talks that has a little bit of reflections about what does it means, what, what is, what does it
do to developing all the research to, to do the other thing, right? So this is like a friction,
an interaction between the two activities that are interesting for us, I think. I hope it is for
you too. We have a question. Yeah. So I come from research and then I move to the university library
space to do training and we try and push for open, open source tools for doing that analysis
and also some things. I'm wondering if you have in the panel an opinion on how do we promote
those tools best, how do we get people to use them? Because there's a very on the proprietary side,
there's a lot of, you know, marketing funds and there's also a lot of culture that stays in academia
and you just use whatever tool the person who, you know, your, your colleagues use, right,
or the oldest person in the room uses. So then it's a bit, you know, two-fold questions.
How do we push for using those tools to improve open research practices, but also how do
we like them most sustainable? So they're still around and maintained and get better over time.
Big questions, sorry.
One idea that comes to my mind, there is a, there is a product that is called
RSD, research software directory. This is developed by the Netherlands eScience Center.
And what we do with this tool is that is a directory of research software in which you can see
what is the product and what is the intention, what are the capabilities and also how is maintained
and you can cite it, you can track it. Yeah, but it's really focused on research software directory.
The thing that I do now when I start a project with the research areas, have you looked in the
research software directory, if there is anything that may be adapted for your project? And I think
just having everything a little bit collected there helps a lot. So this is, this is one side
of two answer this. And then the other thing that researchers have tendency to do is they
want to build everything from scratch. They do not want to reuse things. So this is also a
culture that I think we, if we can, need to change, just reuse things, don't try to reinvent
them, we'll ever tend that you have an area. Yeah, they just, just kind of to conclude and I've
been a student as a non-ropolologist, the community we are, it's a long-term battle, it's complicated.
I don't have the time to have the discussion, but it starts with having that space. So having
another space is where as a community we can discuss of the actually quite tough position of
whoever that's open source software in academia, but actually many people are working on this
finding solutions and so on. There is no single bullet for this, but we need to be better
of a network and to coordinate better and to know each other better. This is a good place to start,
it's not enough, you know, very starts like this.
So hi, very important question and it's so important that my organization OLS, we're actually doing
this project in partnership with the digital research academy and it's basically to do research,
find out how researchers, that's a lot of research in one sentence, but how researchers can better
markets the work that they do and it might be helpful to keep an eye on that project is called OSPAC
or SPAR cake or SPAC so it will be useful to answer your question in details in a couple of weeks
months.