 Well, hello everyone, I am Juanita and I'm going to talk about the scientific Python project and a little bit of what I've been doing with them. So a little bit about me. I am a Colombian. I am a mathematician. I finished my undergrad in Colombia. I'm also a former developer for the Spider IDE for Python. I used to work at Quonsite before. Currently I'm a PhD student at UC Santa Cruz and I am the community manager of the scientific Python project. And a fun fact is I'm also a singer. I love singing. This is my contact information in case you want to reach out. I love to talk about documentation and community. So scientific Python gets confused for the sci-fi project. It's not the sci-fi project. And it's also not the sci-fi conference. So the scientific Python project is meant to support the ecosystem and grow the community. So there's the scientific Python community of developers and maintainers that use the tools in the ecosystem. And the whole ecosystem is the Python packages that we use for research, data analysis, data science. So our goal as a scientific Python project is to unify this ecosystem and pretty much get communication between the projects that are part of the ecosystem and create a joint future together. So one of the first things that we started as the scientific Python project were specs, which we call scientific Python enhancement. Okay, I forgot. But they are basically cross-project policies. And they are meant to pretty much help the ecosystem trying to find a way to do stuff together. So there are some minimum supported versions. So the goal of these is basically if, for example, you are a person who wants to create a new library and you have no idea on how to take a decision regarding a specific thing, then you can see some of our specs and be like, okay, maybe we can do these because these other libraries have been doing it before. So that's kind of like the goal of the specs. But in, well, this short talk, I want to talk mostly about community building and community outreach, which is what I have been doing as part of the scientific Python project. Why? Well, because open source is more about communicating, teaching and collaborating that it is about the code itself. Like we all love the open source community because of the community itself, not necessarily the code. So the scientific Python project is composed of a community of volunteers, mostly from the scientific Python packages of the ecosystem. So we have developers from NumPy, SiteBuy, Map.lib, Pandas that are part of our community. Some of them are part of the specs steering committee, which is the ones that are working currently on writing the specs and proposing these specs. And these are the core projects that we are currently working on. That doesn't mean we can't include more. It's just like this is what we are starting off for our current work. This is the specs steering committee, as I mentioned. These are the people who work on the specs. And, well, the way that we want to do this kind of unifying the first thing, which is what I'm trying to work on right now, is documentation. So we have a website which we wanted to be a central place for information and basically provide resources for many of the projects. Here we have orientation for newcomers, interviews for community introductions, and some demos for problem solving. We have this learn website that we wanted to have a contributor guide, a maintainer guide, and a community guide. So there's a lot of resources that you can find in the documentation of different packages. For example, a contributor guide. There's a contributor guide in NumPy and SciPy and Maplodev. So what we wanted to do with this website is pretty much unify that resource to have it in a central place. And maybe, as Tim mentioned in a little bit, one of the problems is the duplicated efforts on things. So we want to minimize that by having a central place for information that we can share with all the projects. This is something I've been doing for the Scientific Python Project and it's trying to do orientation from newcomers. So if you're a person who doesn't know what the Scientific Python ecosystem is, then, well, this is the place you will find information for. So I've done videos on why to contribute to Scientific Python, five ways to contribute without coding, and how to choose a project if you want to start contributing. And then there's also these interviews that I've been working on with maintainers from different packages in the ecosystem. And, well, I like to say that this is a way of bridging a gap between the users and their developers of this community. I feel like most of the times, if you're a user and you use NumPy, you have no idea who's behind it. So this is a way to show people who's behind that and also show them that we're not aliens. We're normal people who have lives. We have pets. We have kids. And it's just kind of like a fun way to show people who's behind the packages. I also tried this revolutionary idea of doing videos on TikTok. So this is a demo that I did for how to, like, getting set up your development, like, stuff you want to contribute. So forking and cloning are repository. This is a very short video that I posted on TikTok. This is screenshots of it. And I guess it was kind of like a way of extending our community more than on Twitter, which is where I've seen most of the communications from developers happen. I kind of want to explore new venues. So I decided to start doing TikTok stuff. And the other thing that we want to, well, promote a lot is our blog. So we want this to be like a central place for people to share thoughts and ideas on the whole ecosystem, not necessarily like a specific package, but just like general things. There's stuff about the GSOG, people that have done internships on different packages, or even people that post work that they have been doing with different packages there. And then this is the other thing that I do a lot, which is social media outreach. So currently we are using Twitter mostly for, I guess, news and updates. And I think this is like the best way to directly interact with the users and developers. I explored things like the YouTube videos that I already talked about a little bit, and Instagram posts, which, again, it's just like a new way to expand our community and find people in more places that might be interested to join us and have no idea that this community exists and is there for them. This is like an example of a post that I did on Twitter about how to contribute to Scientific Python without coding. And I think this is kind of like the information that you would maybe give to, I don't know, someone that is in their undergrad degree and have no idea that they can contribute to open source in their Instagram, because everyone's on Instagram now. So I guess one of the, like, the main idea where I started to do this was, well, I started, like, I started thinking about the future and how, like, the future maintainers of the projects that we are working on right now are people who are in high school right now, who are in their undergrads and CS right now, and they use these things to communicate. So we have to start communicating in their language if we want them to come to us and help with, like, good maintainers for the future. Okay, and I had a video to show you, but it's unable to play, so... Let me try. Yeah, so this is just an example of what I did in TikTok, which was, like, different advice from Scientific Python developers, and I think this is a great way to just talk to people directly and get them to come to you and be part of the community. Hopefully I can play it. Okay, it doesn't work. Well, in the meantime, if you want to be part of the Scientific Python project, we have a Discord server that you can join. We have conversations about everything there, the community, documentation, outreach. There's channels for, like, pretty much a lot of the core projects in the Scientific Python ecosystem, so if you have a question about NumPy, you can go there and just ask people for that. And, well, of course, we are on GitHub. We have an organization with a bunch of repos. There's a lot more that we are doing, but this is kind of just, like, the community side of things, and all our social media handles. We also have a discourse forum, actually, where we have, like, discussions that are more, like, offline kind of thing. The discourse is more like for synchronous communication. The discourse is for more asynchronous communication. So, yeah, you will come to join us if you are interested. And that's it. Yes, you have a question. Oh, sorry, yes, questions. Have you seen LLMs pop up in your world? Are people talking about LLMs yet? No. Well, at least, for example, the Discord server that we have, like, mostly is discussion between maintainers. So it's whether, like, can we merge this VR so that we can do this release? So, but I guess, like, they might pop up in, like, some discussion that I might not be part of, but not from what I've seen, but probably because we haven't made a space for it yet. Okay, thanks. I have a question regarding which foundation is governance of this project? Which what? Foundation. Do you have any governance body? Governance body? Yeah. So not yet. So we actually, so the project started with, like, a grant from the, like, it was awarded to BITS, the Research Institute in Berkeley, to Stefan van der Waalt and Jared Millmond, who are, like, the starters of the project. So it started with a grant. Right now we are part of the non-focused sponsored projects. And I guess, yeah, that's, that's how we've been working. But we, we... The other question actually is similar to team. How we actually, if we run into the, this L or M, large language model, like a TensorFlow part-touch, how does that can be integrated or, you know, together with the project under this scientific PISA? Well, I guess there's a lot of, a lot of people from these, like, libraries that are probably working on that. And I guess a good way to find, like, cross-project conversations would be this place because there's a lot of people from different libraries who are doing different stuff. So you might actually find people from PyTorch, I don't know, and TensorFlow that are part of these, of these community. So I guess that, that, that would be my, my guess. Okay. All right, thank you. Any other questions? No? Okay, thank you.