Hi Carlton, I posted my question on the original ticket #32340 <https://code.djangoproject.com/ticket/32340> about 10 days ago and still haven't received any response. I was wondering if there were any particular norms regarding how long I should wait for a response before starting some work on the ticket that I should adhere to. Really sorry to bother you with this, but I am keen to contribute and can't wait to get started.
Thanks, Surya On Tue, Feb 2, 2021 at 3:32 PM Surya Banerjee <ssbanner...@gmail.com> wrote: > Hi Carlton, > > Thanks for the directions. I have posted my question on the issue tracker. > > Thanks, > Surya > > On Tue, Feb 2, 2021 at 1:05 PM Carlton Gibson <carlton.gib...@gmail.com> > wrote: > >> Hi Surya. Welcome >> >> Do comment on the ticket. Thibauld and Tom should be able to give you >> more specific advice. >> I'm not sure if Thibauld is already planning work, but there should be >> room to collaborate. >> >> Kind Regards, >> >> Carlton >> >> >> On Tuesday, 2 February 2021 at 02:25:10 UTC+1 Surya wrote: >> >>> >>> Hi team, >>> >>> I am a new contributor and working with Django as a Junior Developer. >>> After looking into issue tracker, I see #32340 >>> <https://code.djangoproject.com/ticket/32340> as a ticket that I would >>> love to work on if nobody else is working on it. >>> >>> In case I get to work on this, I had a couple of questions regarding >>> what needs to be done. >>> >>> 1. For the suggestion of having explicit instructions on the Django >>> documentation about the format of the form fields, as described in the >>> ticket, should I focus on mentioning the default formats for the following >>> fields - >>> >>> - Date and time fields – DateField, DatetimeField, TimeField, >>> SplitDateTimeField, DurationField >>> - More technical fields which have very specific formats: SlugField, >>> JSONField, UUIDField, RegexField, GenericIPAddressField >>> >>> 2. Should the changes in the documentation extend to issues such as >>> #32339 <https://code.djangoproject.com/ticket/32339> or #32338 >>> <https://code.djangoproject.com/ticket/32338> on why it should be >>> avoided? >>> >>> Please forgive me if I have not been able to understand the ticket >>> responsibility the way it is intended, and I would be very grateful if the >>> scope of the changes required could be pointed out to me by any senior >>> member of the community. >>> >>> Thanks, >>> Surya >>> >> -- >> 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/4d49125a-61b0-43a7-9698-3ed7e78e6b06n%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/4d49125a-61b0-43a7-9698-3ed7e78e6b06n%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/CABgd%3DVLZrdO_O%3D5juAr_zY5SJ%3DFMKvuwXF4QSRV09j1gz3kqVA%40mail.gmail.com.
