Djangonaut Showcase Session 3

Speaker 1: Hello everyone. Welcome to the Django Not Showcase. We have two events today. We have this event and we have another one in a few hours at 6. 30 p. m. UTC. You're more than welcome to attend both. To give you a little bit of background on why we are having this event, the inspiration comes in two parts The first part, we heard feedback from you. Many of you expressed that you wanted to share your learnings and experiences with each other. And hopefully this is just a starting point to get you to do that and to build connections with each other and find ways to collaborate when you're contributing to open source. The second part is trying to give you an opportunity to practice speaking.

Speaker 1: If you're trying to share your ideas and thoughts, speaking is a good way to do that. So we're going to have this. It's going to have a similar format to lightning talks at conferences. Each person speaks for up to five minutes. I'll be keeping track of time. And if you go over, I'll interrupt and I'll let you know that it's time to wrap up. So just to set the tone, this is a really safe space and we're here to support each other and celebrate our achievements. If you feel that you've made a mistake or said something wrong, don't sweat it. We're all here to learn together. So let's jump right into it. We have three speakers for this event.

Speaker 1: We have to Abdul Vasil from Team Mars working on Django CMS. We have Daniel from Team Saturn working on Django Core, and we have Suyoung from Team Venus working on Django Core. So first up, Abdul, why don't you take it away?

Speaker 2: Hello everyone. I just want to I'm sure Not um can you hear me?

Speaker 3: Yeah we can hear you loud and clear.

Speaker 2: Oh okay. Right My name is Abdul Wasiu. Um a little bit about myself and me recent um Company graduates. When I'm not coding, I love to read books and um lately I've been dabbling into article. I'm a member of um team mass of the third session of the Django Not Space and That means I mostly worked on the Django CMS ecosystem. So this lightning talk is going to be about some of the issues I worked on. My first issue was a documentation fix. So I have like a so what I like to do with any open source project I come in contact with is to get like a copy from Git and um install it locally.

Speaker 2: Going via the like documentation guide or installation guide or anything that is on the documentation page. So um I noticed that Django CMS did not have like an installation guide. And so I raised an issue to Fabian, which is um the navigator that okay I would like to like write uh an installation guide for people that just come into the project to be able to like get a copy and um have it working locally. Yeah, it gave the good idea and I um worked on the issue. So it it was really um It was a really nice um initial addition to the project. Uh it allowed me to To understand um Sphinx, which is like the documentation, like

Speaker 2: uh one was mostly used for like making documentation in Python. Uh Then I walk and then after that, I wanted to work on something a bit more technical. And so when I was um going through the project, I noticed that the um the CMS command. So basically when you run Python manage the PY then CMS, um it throws like a Python error, like an attribute error or something like that. And I think I read somewhere in the past that Uh for CLI, it's always better for the um error message to be handled and um instead of like throwing like a Python error, it should uh um give something more like um Easier on the eye on the user's eye, basically. Um, so that was the second issue I worked on. And um albeit the the fix was not elaborate, like it was maybe like two lines of code, but it allowed me to understand um how like management commands worked in Django, like

Speaker 2: how to add um more CLI, like how to add more commands to to manage. py and how to like say for example in in Django you can have Python many. py uh then run server then a position argument maybe the port or something like that Right. But in Django CMS, they have like uh two levels of command. So basically you have so for example, you can have Python many. py, CMS, then a cannot that command, uh maybe copy then before you have position argument. So it was are really nice to see how to add like that extra level of um command to to like to a python project. Then I worked on A couple more doc fixes to the user guide. And currently I'm working on uh an

Speaker 2: on an issue on the Django file. So basically, Django File is like a third-party app for managing files in Django. All right. This project, this Django File project has really opened my eyes into like how to add custom model feeds to to a project and how to um How to customize it so the way it appears in the in the admin channel. So you know, for example, foreign keys, when you add foreign keys to a model, it's um it's By default it comes in select boxes, right? But then you can edit it in the admin to come in different forms. So it was really nice to see um how that works. And that's basically everything about what I've been working on. And I'd like to thank Rahmat for the weekly meetings. Fabian for is um

Speaker 2: his guides throughout the project and the UJ organizers for uh for the ideas. Thank you very much.

Speaker 1: All right, thank you, Abdozul. That was amazing. Up next we have Daniel from Team Saturn. Take it away, Daniel.

Speaker 4: Okay. Sorry, I didn't mean to start with a cough. So I am Daniel. I'm also known as Mr. Rios in various platforms on GitHub. my Gmail, Twitter, Faustedon , in a lot of places. So it's sort of, you know, the identity that I've chosen for myself because my father was not Mr. Rios. I decided to be Mr. Rios. Um so my history with Django actually starts in 2016 when I started um developing in Django professionally. Um and a couple years later in 2019, and this is why I have 2019 as a significant date, I actually contributed to Django. And back then it was just uh Carlton and Marius, and those are the only people I had contact with.

Speaker 4: Carlton I already knew uh from a couple Django cons and Marius I'd met, you know, because he was the other Django fellow. But the process itself was just very I don't know, it just seemed very sparse. You know, it seemed like those are the only two people, you know, who were doing the whole project. Um and then after that um the pandemic happened, I started working at a company where we didn't use Django so much and uh So I essentially uh stopped contributing. But um recently, I think it must have been in September. Um Whenever the deadline was, I saw a post by Rachel Calhoun on LinkedIn saying, you know, the the third Django Nut

Speaker 4: session is happening, and I remembered to an email I'd gotten Last year about the first session of where I opened it up, I read it, I said, Oh, you know, maybe I'll do this, and then I never saw the email again. So my question, um, especially since I have a lot of years of experience, um, you know, was should I even apply to the program? Um I've been going to Django, uh DjangoCon Europe since 2016. Uh, when I go to a Django meetup in Berlin, I know half the people. Um, I'm I'm very into the community. I've worked in Django a lot. um you know i've i've done three contributions so is this program for me um and rachel said you know after consulting with everybody that she seemed to think so and if i

Speaker 4: um wanted to you know like have a beginner's mind again I could apply. So I was like sure I applied. I thought the application would take five minutes. It took much longer than that. But I had a very, a very good feeling because it was one of those applications that really like challenged you. So I was uh I was very much looking forward um to the program if I got in. And then I got the email that I got in. So I was uh really happy about that. Um the first few weeks were a bit difficult for me, uh partly because it seemed like my team, um uh Yash and Sarah, um Sorry, from Dublin, um, not the Django Fellow.

Speaker 4: Um, it seemed like they were just doing pull requests left and right. Um and I was like, oh my god, I'm so behind. It's set to start with a documentation ticket. And the documentation ticket is for um It was for custom uh start project and start app uh structures, like file structures Which when I pulled the ticket, I was like, oh, I don't know if I want to do this. And an hour later I was like, oh, I didn't know I cared so much about this. Um so Because it took me so long and because you know I w I thought I'd have three PRs by the end of the program, like completely merged. I realize at some point that it's not a sprint. You know, I'm not here to

Speaker 4: do to, you know, just get a lot of PRs like done. It's a big process and instead of being a sprint, it's a marathon. And for me, I had the mindset that my contributions to Django are not just within this program, but um as the program intends that they'll stretch out even after this program. And I'm very thankful for uh all the resources. Um in the uh the Django Nut worksheet. Um it's just been really incredible to um to get a lot of information, a lot of input, um, and sort of have that be the education uh for becoming a a a Django contributor. So um thank you to my team

Speaker 4: who's um uh even if they didn't know it they've been pushing me along. Um and I also wanted to have uh um also a special mention to the Django fellow uh Sarah Boyce who's also been um sort of nudging me along. And she uh got me to get my blog finally done. Uh I have one post, but uh rest assured many more are coming. So thank you to everyone and that's it.

Speaker 1: Thank you, Daniel. That was amazing. It's a good point that you made that it's not a sprint. Sometimes it could feel like it's a race, but it's not. Um, alright. Up next we have Su Young from Team Venus. Su Young, let's hear from you.

Speaker 5: Oh hello. Uh can you hear me?

Speaker 1: Yes, we can hear you.

Speaker 5: Yes Ah yes. So I'm Soyang, a new Jiangun from Team Business, and I'd like to share my little insight about the documentation. It is I'm a little bit worried at the start because it is not a whole topic related to entirely entirely related to Django, but I think documentation is still an important topic to all developers, so that's why I decided to start with the title, Documentation is All You Need And uh I think there are three reasons that we should, yeah, write some document

Speaker 5: or some simple note. Because first, sharing memories, uh documentation helps us to share memories and feelings of the moment. And as a Django note, I highly recommend you all, not only me, but also all of the developers to write especially the first moment of the contribution as a Django note because uh as the contribution process follows uh I think writing and writing that s writing only a few sentences helps us to remember the feelings of that moment. And that can help us to keep up what

Speaker 5: we have done and keep up the good work and also and yeah and also the documentation helps us uh prevents us from being a perfectionist Uh because uh as the contribution process goes, sometimes uh some perfectionists like me uh said uh thing tend to think that Oh, I could do better or I I should or I must do better. And uh but by writing some documentation or what you have done, we can prevent uh from being too yeah harsh on ourselves. Yes. So that's the reason I think

Speaker 5: that documentation is important. And the third reason is about connecting the dots Because not only as a developer, but also as a human, we all all of us have different lives and different stories as an individual. And yeah, writing the documentation helps us to yeah, build our own stories. And that's why I yeah, I sh I think I decided to, yeah, recommend you guys about the documentation. And also, yeah, I really recommend the other jungunas to yeah share and just write a few sentences of their

Speaker 5: uh our first contribution because that can helps us to yeah keep up our pace and as a contributor and as a Django net. And here are the links about our my a little post about Dango note reviews and some little posts. So if you're interested in yeah and yeah you can see some links on it. Yeah and yeah. So thank you for oh yeah thank you for supporting and Um sorry, my English is not very good, but uh thank you for making this uh warming and welcoming atmosphere to

Speaker 5: yeah, Jangonas and other contributors Thank you.

Speaker 1: That's amazing, Su Young. I feel that that was great advice and I feel inspired just to give everyone a look at what Su Young's um blog post look like. Her writing is amazing. There's a lot of content there. So I just wanted to give you guys a look of how much she's been writing throughout this whole time. It's really amazing. Very inspiring. All right, let's move on to the Q<unk>A session. And so if anyone has any questions that you want to ask, raise your hand and we'll call on you. Or you can drop your questions into the chat and I'll read your questions out.

Speaker 1: Any questions for the speakers? I guess I'll have one. Um For all of you speakers, let's start with Suyang. What was one of the major hurdles that you encountered when you started contributing?

Speaker 5: Actually my the biggest difficulties that I encountered was about the as a psychological huddle that some or stereotypes that contribution is an big and uh something that not not the beginners or newbies or amateurs can do. And that's the yeah, that stereotype is the biggest difficulties that I first encountered. And after the first contribution, actually the first contribution was fixing some

Speaker 5: uh yeah, fixing uh fixing some parameters and removing it. And but uh it was kind of simple. But after that first contribution I I kind of realized that, oh, oh, anyone can contribute and even if they are a beginner or a newbie Yeah, they can still part of the community. And I think that's the major hurdle that first contributors may face.

Speaker 1: Thanks for sharing. Um any other speakers want to add to that? Daniel?

Speaker 4: Um I think my biggest hurdle, um and um I want to say sorry to Maria for getting your name wrong. Um Maria and Yash are probably like sick and tired of me complaining about this, but my biggest hurdle is about picking a ticket. Um and uh You know, in in in some of the talks that I've seen over the years, they say like, oh, you know, there's these perfect for beginner like flags or whatever. And um You don't really find a lot of tickets that way. And when you're on the first page of the track, you know, you got you get to the end of it and it's like, oh. The tickets here are three years old already, and then there's tickets that are even older.

Speaker 4: Um, so I um my teammate Yash was like, oh, you know, I have three tickets that uh I was thinking of working on CFN. You can take any one of them, any that you want. One of them was okay. The other ones are a bit more advanced because he's working on the ORM right now. Um and it you know, he's also discovering it's a marathon as well because it's not as quick as uh as uh as you as you think it is sometimes. Um but my strategy going forward is, you know, if I see something vaguely interesting, I will start on it. And if I'm still working on it an hour later, then I will um I will just take the ticket.

Speaker 4: Um I did this with one about decimal rounding uh in the database And uh when I I think I was like two hours into it and I hadn't assigned it to myself and I was like, I I can't believe I'm still doing this. Like, you know, it's it's I can't believe I would find this interesting. Um the ticket's a couple years old. Um You know, but um and it's still probably gonna be a big hurdle, like you know, looking through eight-year-old tickets and being like, uh But For me, that is probably the biggest hurdle to overcome is just sort of actually finding tickets to work on. Because, you know, is my Team has heard me say, when you're at work, you have refinement, you have the product manager.

Speaker 4: By the time you get to work on the ticket, you already know the ticket. And here it's sort of the opposite. It's almost like a You know, what will we find now?

Speaker 1: That's very interesting. It's definitely it feels um it can feel overwhelming sometimes.

Speaker 4: Yeah.

Speaker 1: Does anyone have any questions? I want to hear from someone else.

Speaker 6: I have a question for Abdul Waisu. Uh do you the installation guide that you added to Django CMS. Does Django Core have a similar one or do you think that's something that would be would also be benefited in Django?

Speaker 2: I think Dango called as, I'm not sure, but I think so. Because um when you apply for Django Note space, I uh maybe I don't get the question, but when you apply for Django Note Space, you actually have to um submit like a Django, like a pull request. Um Yeah, I think so. You have to submit like a pull request, right? Against no we're not against Django, but you have to submit a pull request and link it to the application process, right? So I I think that's basically Django's installation process. process right from like taking it from git and so basically the something like that that's what I did for um jumbo CMS I think.

Speaker 6: Okay cool very good

Speaker 1: All right. Well, that was awesome. Um great question, Sarah. Um I think Let's thank our speakers and yeah that was amazing everyone. Thanks for sharing all your insights Alright. Hello. Welcome to Django Not Showcase. To give you a little bit of background on the inspiration for this event. This event was inspired by two things. The first thing is we heard a lot of feedback from you Many of you expressed that you want to share your learnings and experiences with each other. And hopefully this is just a starting point for you to do that and to build connections with each other and find ways to collaborate when you're contributing to open source.

Speaker 1: And then the second thing is we're trying to give you an opportunity to practice speaking. If you're trying to share your ideas and thoughts, speaking is a good way to do that. So we have a similar format to lightning talks at conferences. Each person will speak for up to five minutes. I'll be keeping track of time. If you go over, I'll interrupt and let you know that it's time to wrap up. So just to set the tone, this is a safe space. We're here to support each other and celebrate our achievements. If you feel like you made a mistake or said something wrong during this event, don't, don't sweat it. We're all here to learn together. All right, so let's jump right in. So we have four speakers for this event.

Speaker 1: We have Anthony from Team Venus working on Django Core. We have Josh from Team Saturn working on Django Core. We have Sarah from Team Neptune working on accessibility. And we have Maria from Team Saturn working on Django Core. So first up, we have Anthony. The stage is yours, Anthony.

Speaker 7: Thank you very much. And uh good morning from Sydney. Um so yeah, uh thank you for the introduction as well. I'm from Team Venus in session three I was working with uh Captain Kenya, uh Navigator Mariush, who is internationally famous as a Django developer. I affectionately think of him as the John Wick of Django. uh and my fellow uh cadets and tai. Um my original kind of motivations for joining the um Django North Space Program was I really wanted to give back to a community like Django, which I've taken quite a lot from, but and I only realized this this year that I was really anxious about the thought of looking foolish in public and making a mistake and ultimately

Speaker 7: not really giving much return on investment that uh the community would have in me. So um Jenkins All Space has kind of been a really cool environment for me to kind of find my voice and uh find a way to kind of effectively give back to the community. So uh to kind of talk about uh three tickets I've worked on in the uh since I've started. So the first one I had was adding support for PostgreSQL explain commands. It's like an optional parameter you can send to get the query plans. adding the memory and serialized and that was probably my first real foray into doing work on Core Django and Marish was really great in terms of mentoring me through the process and showing like, here's the ticket, here's some example work that's been done in the past.

Speaker 7: You kind of follow the bouncing ball and get up to a pull request. So having that one completed was a really cool way to kind of uh get settled in and eventually start to see a pull request getting merged, which was really, really awesome. Uh after that, uh just looking at the Django North's Discord channel, uh, there was an opportunity to update the documentation. And uh as simple as what might appear to be like a one-line fix can strike up a lot of conversation with a lot of people. And one thing I kind of learned from that was even though your pull request might be approved and everything like that, you still need to be patient. Um You might be sitting there waiting for this thing to be uh merged, but the community kind of takes it can take a little time to kind of merge. So it was a important lesson for me to kind of just be patient

Speaker 7: And the ticket I'm currently working on now is to validate the valid model validations at boot up time when you check whether or not there is a foreign key uh name but also have a subaction manager name and raise an error for um uh raise uh an er an error to the uh users. So Uh that was actually something I'm working on now, and this is going to be my first real foray into doing something by myself. So um I think overall the experience has been really great to start to do some coding out in public, give back to a community I've taken quite a lot of and particularly for anyone with or without coding experience.

Speaker 7: Like I've been coding since what two thousand and four. So in a varia various languages. So this is my first real time giving back to a community I take quite a lot from. That This has been great and I'm excited to kind of contribute any more uh in the future. So yeah, thanks everyone.

Speaker 1: Thank you, Anthony. That's amazing to see a variety of work from documentation to the SQL Explain and pointing out that you need a lot of patience for this Thank you so much. Up next we have Josh from Team Saturn. Josh, take it away.

Speaker 8: So hi everyone. My name is Yash. I'm one of the Django Notes in the session three. My navigator was Paulu and Uh my uh captain was Miguel and I like my lovely Django crewmates were Daniel and Maria. I had a lovely time with them, like for the past seven weeks I've been working through issues and learning a lot of stuff. So first of all Um from my slide, I will go with like my experience till now has been like a very rocket boost because I was also trying to contribute to Django before the program started. I had a PR. But when I joined the whole program, okay, so I was seeing so many guys working, I was seeing Anthony in the chats, in the, you know, texting. I will see my, you know. crewmates working and you know finding issues and stuff.

Speaker 8: So it's all it was like a I was not alone. So it's a great thing. Janganot helped me a lot to give me that boost. So I was I've been working So other and the next thing I believe is that this thing called like which is the most common thing I noticed among everybody was that you know breaking the ice between you and the track system It's a very big thing, you know, find that perfect ticket that everybody tries to find. Until now, I have like uh fixed few issues which have been merged. So from my experience to this point, I feel like it's just like you go through something You are interested, something even interests you one percent. You just go full on towards it. It's not about ever about no that finding that perfect, you know, that perfect ticket. It's more like you know just getting onto it, learning more and stuff. Just get to know that ticket better. Just sit there and just learn.

Speaker 8: That's one part of things. Then next, I this is then like one of the learnings I had. No ticket is like you know, every ticket teaches you something. Like for like even the minor documentation issues. Uh I remember and same as Anthony said, uh I picked this issue of writing documentation. I thought it will take hardly one, two days. I just wrote the whole documentation. I thought I thought like it will get merged in the next two, three days because I thought it was like very good But uh it took I guess ten days. We I and Sarah had a like really long conversation. You need to change this, you need to change that and this and that, a lot of things And then we finally came to this conclusion that yeah, this looks good. So a good documentation, like like writing a good documentation is an art itself.

Speaker 8: That's what I got to do. Even that documentation taught me a lot. Like because the research that goes to write that perfect, you know, that perfect documentation, how the objects are working. I worked around I guess DB default. Like I was working around like how the DB default and all works. So I had to write the documentation for it. So it taught me a lot on the background how Python memory is using using it. So each issue helps you a lot to learn Next, I love the Django Iron. So for the past, after from the week three, I picked this issue of like, you know, adding atomic uh upsurd support. And since that week, I've been learning so much. Uh obviously I haven't raised the PR yet because it's a very big issue. Like I've been like learning a lot. I've made so much notes. Half of my copy is filled with flowcharts and stuff

Speaker 8: how to do this because you know ORM is a bit tricky, but I I love I love because it's okay I didn't like raise the PR, but the amount of learnings I had in the past four weeks, I feel like I become more of a better Django developer. Because you know you get to know about the internal workings, how things are working inside. Because it's really good because I realize like are you passing fields when you're creating instances in the models They are having like you know all these things are converted into a field object, then how it uses PsychOPG2, you know, raises that and send that query and generates the compiler generates that query. It's going to Postgres, it's handling all the also while contributing the ORM I also got to you know chance of reading Postgres

Speaker 8: logs and how they are working, how internals everything is working. So It's a pleasant experience for a guy like me. It's a pleasant experience. So totally, I've enjoyed all of my time and working with Django Aram has been really great. Hopefully, I will raise up yeah this week Or maybe next one month. But I will try my best. So yeah, that's all from my side.

Speaker 1: Thank you, Yash. That was really good advice. It's really nice to hear your perspective of like going to finding a PR that's really interesting to you. And then also like hearing you going to this much bigger PR with the ORM. Really good work. Our last speaker is Maria from Team Saturn. Maria , that's from you.

Speaker 6: Yes. I was inspired to talk today after being to the previous talk where my teammates Daniel was giving a speech. And I just and everybody who spoke there was very encouraging. And I just feel that I wanted to share what how I felt about this. this um programme being on it. And at first I didn't think that I had anything to say because I felt

Speaker 1: um that I didn't contribute as much as as other people did. But I know that we're all working at different paces. And it is great to belong to something like this where we can we can we can take our time and think of it as the long journey. So just to start, when I when I did get in, I was absolutely delighted and I wanted to think that I would merge a lot of um Tickets, solve a lot of tickets. But very quickly on I realized that I felt a bit more like the note being Django notes in the sense that you know I felt that I wasn't uh contributing as much or as quickly as I would like. So I was quite impatient and I thought um I wanted to make a difference very quickly

Speaker 1: So um yeah, thinking you know back how did that how did I feel that way so soon was more to do with looking at the tickets and thinking, you know, the easy ones that are classified as easy. They're kind of tough for me. And I spent a lot of time reading tickets trying to decide how do I know which one I'll be able to do? And realizing that it takes a long time to you know, think about how can I replicate the issue? Will I be able to replicate the issue? So there was a lot of that. And all the time this was happening, I knew, well, I'm not doing anything. I'm just reading. So I felt, yeah, I I felt That like the note in Django notes. So, you know, but then it was the fact that we had team meetings, that we meet our team regularly, and from that

Speaker 1: I learned a lot from the people on the team. So it was great that we do meet regularly because, you know, I realize that the wins that we have, they're not related to how many tickets we solve or how many PRs get merged It's all about learning and taking that learning into the future with us. So I can say I have some wins that were visible and invisible wins as well So my visible ones would be that, you know, I did do tickets, I did do small tickets that were merged. Um and I would recommend if somebody who's starting to maybe because track can be kind of daunting to look at, Yash said it and a lot of people feel that way. You know, my first ticket was one that wasn't even on track. It was just so small.

Speaker 1: But the thing is the process to to to merge something or to get something merged is the same whether you're you've done a ticket, whether whether you've um taken a ticket off track or whether whether you don't Uh so the thing is if a ticket is so small, you can still raise a request. So that was a great thing to to know about and to do because Yeah, um you got I got through the process of merging, creating, describing what was the issue, fixing it and getting feedback and then getting it merged and just getting that process. So I did a couple of those, which was great. So I also reviewed somebody else's MR , small MR, but it meant I had to, you know, download his branch and and and replicate it. And so that was good. And that MR uh has been approved. So that's a win for me to think that I

Speaker 1: I I thought that MR was fine. So, and it was. So then my invisible winds, which I will take with me, you know, are the fact that I didn't realize this, but even though I felt kind of daunted and you know worried that I wasn't doing enough, my other team members I've heard that they 're they were like motivated by by me and other people on the team. So even though because we so we keep each other motivated. So um, you know, and it's nice to know that even if I don't have a majors major tickets to show that I'm still able that I've still been a motivation to other people. And that's what you get by being a Janganot and being on the teams So I like that.

Speaker 1: The other thing is no matter what, you're there's always new knowledge. You're I'm always learning new things. Even if there's nothing to show for it, it's it's it's I've got it and I I can use it eventually. in in more tickets as you as you do stuff you you you you bring along your knowledge to the next thing. So yeah another win for me was uh not being so skeptical of social media because I'm not used to you know blogging or even talking on channels with other people and I I I think that was that's good for me that that's something I got out of this. So yeah, I wanted to thank everybody and I like um all the help that everybody has given me on this and you know even the people on on Discord that I've never met who react to posts You know, it's just it's lovely.

Speaker 1: It's great because you might say something and somebody will give you a smile. And it's just nice to be part of that. And I think it really is helpful to have people keep going. So the So basically the thing is um my mistake at the start wasn't the very first sentence there where I said

Speaker 6: I want to have ten things merged by the time this is over. And the thing is, it's not ever over. And that's the thing to remember because everything we do It's just the start. And we should never think this is over because yeah, that's that's That's not gonna happen. You're not gonna have all these major wins straight away and just to understand that that's not a failure. Um yeah, and so that's me. Um thank you

Speaker 1: Thank you, Maria. I love hearing everything you had to share. And you know, sometimes you don't realize how much you contribute and how much you've learned until you work on a team and have people give you some feedback. So thank you for that. All right. We're gonna go into a Q<unk>A session. So if anyone has any questions that you want to ask, feel free to raise your hand and we'll call on you or drop your question into the chat And I'll read the questions from the chat. So anyone want to start us off? Um I guess I'll start this

Speaker 1: off. Um let's see. Um Um, let's see.

Speaker 6: Could could I ask a question?

Speaker 1: Yeah.

Speaker 6: Maria, could you tell us more about this 12-year-old ticket that you merged? Yeah, well, yeah. So probably the most amazing thing about it that it is that it was 12 years old. So as long as people don't ask for the detail, it's quite impressive But it was simply that somebody had asked, somebody had pointed out that they found it very hard to

Speaker 8: integrate uh

Speaker 6: Custom backends, they were doing it fine and they real they were doing a work

Speaker 8: it didn't work out for them anyway and it was something so simple they just didn't have um a feel set to active

Speaker 6: or

Speaker 8: they didn't realize the most Basic thing had to be set. So it was just to say put put it in the docs in a different place, what the basic requirements are, so that I don't have to go looking everywhere. And when I read the docs, I could see that it wasn't clear.

Speaker 6: And the other thing was it was from version 1. 3. So even just to say um okay I might add something in here. I have to go back. And check the page from that time, you know, build the docs from that time to see what had they seen at that time that wasn't Easy, you know, what had they seen? And it was actually the same as today. So I was able to say, yeah, it hasn't changed, and this is an update.

Speaker 8: You know, that little investigation

Speaker 6: was fun. Yeah, that was it.

Speaker 1: That's amazing. Does anyone have any questions to ask? If not, um I'll ask one. Um, let's see. So um Um sorry. Um, let's see. Sarah, do you want to talk about um Any accessibility PRs that you've worked on that that you learned a lot from?

Speaker 6: Yeah, I mean, um, to be honest, I'm not I am not super um familiar with CSS, I have a cursory introduction as most of my experience has been on building out the APIs. And so the whole thing was a learning experience. And, you know, kind of more generally for anybody who is going to create a um issue for Django, like you know, learning the track, like learning to create a ticket, learning the um the the specific

Speaker 6: way to you know, um the specific markup language for track the um the the digging through And then, you know, being able to run Django Core locally to create um to create a look like a to set up tests in your local project. I was really lucky. T-Bald who's also T-Bald, who's also on the DSF, has already um has already like created a entire repo that has a bunch of tests for running um

Speaker 6: you know, accessibility specific uh changes in your local so that you can test and find out. And so learning how to utilize is rebo, which is amazing to have access to that kind of those kinds of tools without that, I, you know, it would have taken me so much longer to uh be able to test the changes that I was that I'm making. Con like contrast is super important for people with low visibility or colorblindness and um the Django website is in the process of being made more accessible. And that's

Speaker 6: awesome. So, you know, just getting working with CSS and with T Ball and his his um his tools was pretty amazing.

Speaker 1: That's awesome. Yeah, I I think there were other conversations about like um getting started and there's just so much around getting started. There's like the tools, the tests, and you know, even the the topic that of the PR that you're picking. Sometimes it could be so overwhelming. So definitely good to hear that you were able to work your way through all of that with, you know, Tebow's help and your team's help. There is a really interesting question that Tim put in the chat. He's asked, has anyone else done code review? And how did it go? And I see Josh has says he has done it. Anthony says it's on his to-do. Does anyone have any advice on how to do code review?

Speaker 7: Um Marish mentioned that there was a uh pull request like checklist that is good for people who are getting started into doing reviews, which is cover some like the basic hygiene. And I think that it's particularly useful for us new contributors because it can let us know Like you kind of help get like some of the basic foundation work sorted before I guess other people come along and do some more detailed reviews based on their experience. So I I like to think that by, you know, even us like newbies can start to uh kind of help clear someone like the lower hanging fruit for a lack of better words. uh and I guess have a net decrease on the stress on the

Speaker 7: uh on some of the more seasoned uh reviewers.

Speaker 1: Thank you, Anthony, for sharing that. The checklist. I don't know if I'm too if I've ever seen that checklist, but that would be interesting to share.

Speaker 7: I'll find the link and post it in the chat and probably in the Discord as well.

Speaker 1: All right. Yeah, that would be amazing. Well, thank you to all the speakers. This has been amazing to hear from everyone and to hear all the questions. It's been wonderful and hope you guys keep contributing. Mm