Best status to start to contribute

85 views
Skip to first unread message

Sarah A

unread,
May 14, 2021, 10:43:59 AM5/14/21
to Django developers (Contributions to Django itself)
Hi,

I'm a new contributor to Django project. 

I've tried to contribute to a ticket by using the query "easy picking" from the documentation but unfortunately I didn't pay attention to the triage status which is different to the status. 

Is there a status for easy ticket which are ready, or something ?

I found only assigned tickets or tickets which are not ready. I may miss something, I'm happy to get information to be in right direction.

Thanks,
Sarah

Adam Johnson

unread,
May 14, 2021, 11:07:18 AM5/14/21
to django-d...@googlegroups.com
Hi

The search linked from the contributing docs is to: https://code.djangoproject.com/query?status=!closed&easy=1

If you uncheck the "assigned" flag you'll find those tickets that have not been claimed by anyone.

That said, often tickets are claimed by people, by assigning them to themselves, but then they stop working on it. The best way to figure out if an assigned ticket is ready to be worked on is to read its description and comments, and see if work has stalled. If there's an attached PR, also check there. If a ticket has not been touched for months, it may be appropriate to take it over. I think this is why the documentation links to this search, with "assigned" allowed.

Thanks,

Adam

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/06b83790-3d75-4238-985e-c4befb164cd9n%40googlegroups.com.

Carlton Gibson

unread,
May 18, 2021, 9:34:11 AM5/18/21
to Django developers (Contributions to Django itself)
Hi Sarah, 

Welcome!

Beyond the “easy pickings”, another good approach is to filter by component. The framework is so big, no-one can take it all on. 

Here a filter for the GeoDjango tickets. If you adjust the component at the top, you can see other. Maybe you like forms, maybe you like templates, … 37 tickets, in the case of GeoDjango, is a lot more addressable than 1000+ if you take them all. 

Most tickets require a bit of time to get into them and understand what’s going on. (The dual of that is that, pretty much every ticket is “What on earth is that about?" to begin.) That’s normal. It’s part of the fun. 😀

Have a browse. If you get stuck do reach out, either here or on the forum as you prefer. 

I hope that helps. 

Kind Regards,

Carlton


Sarah A

unread,
May 18, 2021, 9:59:00 AM5/18/21
to django-d...@googlegroups.com
Hi,

Thank you Carlton and Adam, I really appreciate it!
Both answers help, I'll check that.

Kind regards,
Sarah

You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/Cs5GuVHUcrU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/34BB7D51-AFEC-42C9-8567-EBF574E365A5%40gmail.com.


--
Sarah Abderemane
SARAH ABDEREMANE
  
FULLSTACK DEVELOPER+33 6 67 51 46 80 
sarahab...@gmail.com
Twitter LinkedIn
Reply all
Reply to author
Forward
0 new messages