On Thursday, April 4, 2019 at 10:02:01 AM UTC+5:30, Asif Saif Uddin wrote:
>
> I checked your contribution Parth, really good one!
>

Thank you :)
 

> once you improve your proposal, try to focus more on 
> form/formfield/formset/widget/admin/ related issues so that you have a 
> better insight into what your proposal going to improve in those areas. And 
> popular and useful extensions could be benefited from x features to be 
> implemented in that way etc. triaging the related area based tickets and 
> fixing some more related issues not only improve your chance to get 
> selected but help you understand the related areas much better. good luck 
> for GSoC this year.
>

Thanks again for the advice, I'm trying to compile a list for tickets that 
can be directly or indirectly fixed by my project. Also trying to find 12 
weeks worth of work in the formsets.
My main focus right now is:-

   - Making the request variable available throughout the formset
   - Handling relation fields in ModelFormSet  (* new)
   - declarative syntax for formset (#10403 
   <https://code.djangoproject.com/ticket/10403>)
   - adding pagination option / pretty print 

*Feel free if you would like to add something to this.*
 

> On Wednesday, April 3, 2019 at 10:06:26 PM UTC+6, PARTH PATIL wrote:
>>
>> Yes sure I will try to update my proposal by tomorrow (4th April) night 
>> (IST +5:30), So  please have a look at it once again, and suggest changes.
>>
>>
>> Best Regards,
>> PARTH PATIL
>>
>> On Wed, 3 Apr 2019, 9:23 pm Carlton Gibson, <carlto...@gmail.com> wrote:
>>
>>> Yes, just pseudo code — so when reviewing your proposal next week it's 
>>> easy to see that it'll be the right approach. 🙂
>>>
>>> On Wednesday, 3 April 2019 17:51:18 UTC+2, PARTH PATIL wrote:
>>>>
>>>>
>>>>
>>>> On Wednesday, April 3, 2019 at 8:58:26 PM UTC+5:30, Carlton Gibson 
>>>> wrote:
>>>>>
>>>>> Hey Parth. 
>>>>>
>>>>> Right. So, thanks for making the effort so far. Good. 
>>>>>
>>>>> Can you add more detail about yourself. You've not contributed to 
>>>>> Django right? So the concern at this point would be whether you're able 
>>>>> to 
>>>>> fulfil the project. 
>>>>>
>>>>
>>>> I have contributed to Django (see #30189 
>>>> <https://code.djangoproject.com/ticket/30189>), I have mentioned it at 
>>>> the end of my proposal, I would try to highlight that. 
>>>>
>>>>  
>>>>
>>>>> What's your experience with Django? (and if you want to implement a 
>>>>> declarative formset syntax, Python more generally?)
>>>>> (Perhaps you said this, but it needs to be in the proposal.) 
>>>>>
>>>>
>>>> Sure I will add some of my projects in the proposal. 
>>>>
>>>>>
>>>>> You don't necessarily need to have ideas for the final code, but what 
>>>>> does e.g. the usage look like with your idea (i.e. adding the request 
>>>>> parameter)? 
>>>>> (So the formset gets the request and this is available where...? and 
>>>>> so on: can you SHOW in your proposal that this WILL address the issues?)
>>>>>
>>>>
>>>> I'm a little bit confused here, What you mean by "SHOW that this 
>>>> works"? 
>>>>
>>>>    - Do you just write some pseudo code, and say this will work?
>>>>    - Or I have to prove in some way that this will work??
>>>>
>>>>
>>>>> HTH.
>>>>>
>>>>> Kind Regards,
>>>>>
>>>>> Carlton
>>>>>
>>>>>
>>>>> On Monday, 1 April 2019 21:29:33 UTC+2, PARTH PATIL wrote:
>>>>>>
>>>>>> Here is a link to my GSoC proposal
>>>>>> Its a first draft so you are open to comment and suggest changes
>>>>>>
>>>>>>
>>>>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>>>>
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> PARTH PATIL
>>>>>>
>>>>>> SOFTWARE DEVELOPER, AUV-IITB
>>>>>>
>>>>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>>>>
>>>>>> [image: Image result for FACEBOOK ROUND ICON] 
>>>>>> <https://www.facebook.com/parth.patil.77> [image: Image result for 
>>>>>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> 
>>>>>> [image: 
>>>>>> Image result for linkedin ROUND ICON] 
>>>>>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>>>>>
>>>>>> -- 
>>> 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-d...@googlegroups.com.
>>> To post to this group, send email to django-d...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-developers/deae8484-5a5c-4158-b5ef-f262f30eb6eb%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/django-developers/deae8484-5a5c-4158-b5ef-f262f30eb6eb%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/e1546d9e-4856-45fd-ad58-356d8f34045c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to