Picking a Ticket

One of the hardest things about contributing to Django is picking a ticket. Sarah Boyce has a great short video on a method that she recommends and it's a great bit of advice. As part of the Djangonaut program I work to help my Djangonauts find a ticket to work on.

A few queries I recommend are * Sarah's Vulture * Needs Documentation

Using the Needs Documentation I was able to filter down to just this and identify three tickets that seemed interesting:

Picking a ticket can be challenging, but using the filters can really help get you down to a smaller list of things to try and work on.

Djangonaut Space - Session 4

Next week starts session 4 of Djangonaut Space and I've been selected to be the Navigator for Team Venus with an amazing group of people. As has happened before I go into this with an impossible amount of imposter syndrome lurking over me. While this will be my third time doing this it still feels all new to me and I'm constantly worried that I'm going to "do it wrong".

I have the start of a plan to help with my navigator duties, and I need to get that all written down so that I don't forget what needs to be done and when it needs to be done by! I'm hoping that I'll be able to pick up a ticket and work alongside my Djangonauts as I have done before, but the seasons of life can, and do, have a way of changing quickly.

Perhaps I can just try and focus on getting my one current In Progress ticket wrapped up before diving into a new one 🤔

Anyway, I'm super excited about the prospect of Session 4 and can't wait to "meet" my Djangonauts on our first call next week.

Here's to hoping my imposter syndrome doesn't get the better of me 🚀