Hi Vibhu Thank you for your documentation improvements. There are certainly many more bigger improvements that can be made. For similar small typo fixes in the future, you can just directly submit a PR rather than do all the paperwork of adding an issue.
Yes, "easy pickings" tickets get resolved fairly rapidly. There are many eyeballs looking out for such issues. As fran says, you can look for older issues on which work seems to have frozen. But beware - the older the issue, the harder it likely is to be! Thanks, Adam On Thu, 6 Feb 2020 at 01:01, Fran Hrženjak <fran.hrzen...@gmail.com> wrote: > Just a quick note: issues that have an owner but weren’t updated in a > reasonably long time are usually open for taking. It is probably polite to > ask the owner first, because maybe they just resumed working on the issue > yesterday :) What is “reasonably long time” is probably open to > interpretation, but I’d say anything that is counted in years has to be > fair game. > > I’m wondering if it would make sense to have such tickets automatically > unassigned... > > > > > On Thu, Feb 6, 2020 at 1:41 AM Vibhu Agarwal <vibhu4agar...@gmail.com> > wrote: > >> Hi! I'm Vibhu, currently an undergraduate. >> I've been working with Django for over a year now. >> And for a long time, I've been wanting to contribute to Django as well. >> >> So I followed a few links shared repeatedly in the mailing list, like: >> - >> https://docs.djangoproject.com/en/3.0/internals/contributing/new-contributors/ >> - https://docs.djangoproject.com/en/dev/internals/contributing/ >> >> Through those, I followed other links and thoroughly read the guides like: >> "Reporting bugs and requesting features", "Triaging tickets", "Submitting >> patches" and "Writing your first patch for Django" >> >> I even tried to get familiar with the process through #31222 >> <https://code.djangoproject.com/ticket/31222> and #31226 >> <https://code.djangoproject.com/ticket/31226> and looked through some >> closed PRs as well. >> Then I tried to find 'easy pickings' which are directly related to the >> codebase, but I couldn't find any which is new or un-assigned. >> >> I just need to get started with understanding the codebase and its >> structure. >> If anyone could help me look for an issue which involves writing tests or >> changing code in any way, it would be great. >> Any beginner-friendly issue will do. >> >> -- >> 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-developers+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/8489e521-d8b4-44b3-9569-3068dd14256d%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/8489e521-d8b4-44b3-9569-3068dd14256d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAM2o%3DwNBkdPV89JOoCizeKzOG%3D8uarHAnU8FbH08TA_v2L2y9w%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAM2o%3DwNBkdPV89JOoCizeKzOG%3D8uarHAnU8FbH08TA_v2L2y9w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1O8tyV3GEW5ir5h76k-g5iL7h3kRoFhPScPxNzs0kcgQ%40mail.gmail.com.
