Re: [Technical Board?] Project Ideas, and beginning GSoC 2023.

[Manav Agarwal]

Hii All!

I am a Google Summer of Code 2021 Student and have contributed to
The schema editor project.
I would be happy to mentor a project this year.

On Tue, Jan 17, 2023 at 8:23 PM Carlton Gibson 
wrote:

> Hi All!
>
> Thanks for your earlier replies, comments and ideas!
>
> The organisation application period for GSoC begins next week, so I've
> pulled them together to begin the ideas page:
>
> https://code.djangoproject.com/wiki/SummerOfCode2023
>
> It's not 100% — not least I need to go over the WIKI formatting, and make
> it consistent (but ignore that, or make clean ups :)
> *Please have a look *— see if the descriptions make sense.
> (I want to add a few more links and such, and tweak the descriptions —
> again, happy to take edits :)
>
> If you suggested an idea I put you as a *Possible Mentor*.
> That doesn't mean you're committed to anything — but equally we do need
> mentors… :)
> What's involved? Not too much: being available to comment on a PR on your
> project is the main bit.
> If you know you're not happy to mentor, you can remove yourself: if you're
> the only person, please put me instead.
> *(*If you *didn't* suggest an idea but might like mentoring do feel free
> to do the opposite :)
>
> It's Google *Summer *of Code — so there's ages before anything much else
> happens.
>
> Thanks again.
>
> Kind Regards,
>
> Carlton
>
> On Tuesday, 15 November 2022 at 10:11:45 UTC+1 Carlton Gibson wrote:
>
>> Hi all.
>>
>> Google Summer of Code (GSoC) for 2023 has just been announced.
>>
>> https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html
>>
>> Django has participated many times, and it's been a real boon. Recent
>> successes include:
>>
>> * The django-stubs mypy plugin.
>> * The cross-db JSON field.
>> * The Redis cache backend.
>> * Per model-class (field instance) custom lookups
>> * Setup of the django-asv benchmarking project.
>> * ...
>>
>> Application deadline for Orgs is February 7. I'll begin working on it
>> after the New Year.
>>
>> Main bit is an ideas list for projects. The GSoC guide has a Writing a
>> Good Ideas List
>> section.
>>
>> > Projects should take ~175 hours or ~350 hours for GSoC contributors to
>> complete.
>>
>> i.e. "short" or "long" projects.
>> https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list
>>
>> I'm writing here *to solicit input on project ideas*.
>>
>> I put "Technical Board?" in the subject because we're short a list of
>> project
>> ideas for the technical direction of Django going forward, and maybe
>> thinking
>> in terms of GSoC could be a way of bootstrapping that. The "?" is because
>> that's not
>> meant to exclude other input.
>>
>> Here's last year's list for reference:
>> https://code.djangoproject.com/wiki/SummerOfCode2022
>>
>> - Some of those were done: benchmarking (but that could be built on) and
>> per-instance
>>   field lookups.
>>
>> - Rate-limiting is a no-go I think: we couldn't come to any decent
>> agreement on scope,
>>   so it's better to live as a third-party package.
>>
>> - I've tried to include folks from the wider ecosystem in previous years.
>> Two years ago
>>   we had both Wagtail and django-stubs projects. Wagtail then (last year)
>>   applied in their own right, to great success. I'd like to offer that
>> help
>>   again to e.g. Jazzband or other established projects, assuming
>> maintainers
>>   feel they have the capacity to mentor. (It's a minor increment to my
>> effort
>>   for a good return I think.)
>>
>>
>> No urgency but, can I ask you to put your grey cells into action? 🙂
>>
>>
>> Thanks.
>>
>> Kind Regards,
>>
>> Carlton
>>
> --
> 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/58bf890d-28be-49b2-827e-a7cbe1f9587en%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/58bf890d-28be-49b2-827e-a7cbe1f9587en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Regards
Manav Agarwal

[image: https://www.linkedin.com/in/manav-agarwal-982553190/]
<https://www.linkedin.com/in/manav-agarwal-982553190/>

*"If your actions inspire others to dream more, learn more, do more and
become more, you are a leader.”*

-- 
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/CACbxD0CRGU_Wh_mabK8FBREYwg4TtmCheNc2kcx45K4KATDf6A%40mail.gmail.com.

Re: I want to contribute to Django

[Manav Agarwal]

I think this may help

https://docs.djangoproject.com/en/3.1/internals/contributing/

On Tue, 10 Nov, 2020, 1:24 am Gaurav Mitra,  wrote:

> Hello there , i am have recently took a course and finished Django and
> Django rest framework , i want to explore more into the Django and also
> contribute to Django as open source , Can anyone Please suggest me what
> should i 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/5b35b8f3-b45f-4230-9f80-f92027765167n%40googlegroups.com
> 
> .
>

-- 
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/CACbxD0DZZo3%3DJZ%3Dhbg0VzFZGw9%3DSATR8vyPVk9TvLfXTTOfeSA%40mail.gmail.com.

Integrated python shell in browser

[Manav Agarwal]

Hey everyone,
I am Manav and I am contributing to Django for the last few months. I am 
developing projects using Django for the last 2 years. Currently, I was 
working on a Django based project and was facing a problem. Sometimes, I 
had to use the python manage.py shell along with the server running in the 
other terminal window. It was a hard job for me to maintain 2 shells 
running simultaneously though the other one which had the server running 
was nothing to do with but still it was open in the background and also had 
to manage browsers with them. Is there any functionality in Django to solve 
the problem? 
If there is not any, I may raise a ticket for this on trac and would be 
happy to work on it.

Benefits of the feature would be as follows :
1. Admin would be able to work on a shell and database directly using a 
command-line interface integrated within the browser like the SQL shell we 
have in phpmyadmin.
2. No need to open a separate terminal for database management and shell.
3. the shell instance would be user-specific as per the permissions of the 
respective user.
4. A complete command-line interface to manage admin.
5. No need to move the mouse, again and again, to add entries to the data 
fields from the browser.

-- 
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/3a828653-afb8-42fa-9912-fde32f5f7f09n%40googlegroups.com.

Getting initial parameters of inline admin model formset using URL

[Manav Agarwal]

We may pass initial Model admin form parameters using URL, visit 
https://docs.djangoproject.com/en/3.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.get_changeform_initial_data
 
for more details. 
#26607  introduces a hook to 
customize the initial parameters or kwargs for Django admin inline 
formsets. As per the discussion on the ticket and on the respective PR 
, It seems that adding a 
function to initialize formset parameters from the URL would be complex. 
The purpose of starting this discussion is to have some good suggestions to 
implement the same and also to confirm that whether we shall implement such 
function or not.

-- 
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/1a82ee03-4dbd-493e-ad94-6a74165184aan%40googlegroups.com.

Re: New to GSOC

[Manav Agarwal]

Hey,
IMO you should be familiar with How to contribute to Django. For that, you 
may refer https://docs.djangoproject.com/en/dev/internals/contributing/ 
.Then, you can select a topic/Project Idea for your proposal from 
https://code.djangoproject.com/wiki/SummerOfCode2021 .
Hope that helps.
Regards,
Manav Agarwal

On Monday, March 29, 2021 at 5:01:33 PM UTC+5:30 sumekag...@gmail.com wrote:

> Hello sir,
> I have a firm grip on DJANGO framework. I have contributed to open source 
> (Girlscript summer of code) and still contributing to it. I have used 
> DJANGO as the backend framework and had quite good results using it.
> Now, I want you to suggest me whether I should first have some 
> contributions in Django organization or shall I directly apply for the 
> proposal?
> Hope that I get a response quickly and positively.
> Thank you, Regards.
>

-- 
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/153ba68c-ba6e-4eb7-b6b4-00add2d3e260n%40googlegroups.com.

GSoC Proposal: (Migrations) Adapt schema editors to operate from model states instead of fake rendered models.

[Manav Agarwal]

Hello everyone,
My name is Manav. I’m a Computer Science and Engineering junior at Dr. 
A.P.J. Abdul Kalam Technical University in India.
I started contributing to Django in October 2020 and have solved many issues 
on trac 
<https://code.djangoproject.com/query?owner=~manav014&status=assigned&status=closed&status=new&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id>
.
I read through the GSoC Idea List and the Migration topic stood out for me. 
I found the idea to adapt schema editors to operate from model states 
instead of fake rendered models really interesting.
I am working on this for the last 1 month and I have made myself familiar 
with the whole migrations framework codebase. I drafted a basic proposal 
<https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> in 
which I would be updating the complete solution after some discussion to 
make the solution more concrete, practical, and effective.
The problem with the Migration framework is briefly described in the 
proposal <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> 
itself. 
After understanding the problem I came up with a few solutions which are 
listed below:

   1. As Suggested by @MarkusH <https://forum.djangoproject.com/u/markush>, 
   A central registry to store all dependencies in django.apps.registry.Apps
   
   Or
   
   2. Designing a new metaclass for ModelState just like we have ModelBase 
   
<https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/base.py#L72>
 
   for Model. As then we would be able to use Options 
   
<https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/options.py#L64>
 
   with _meta in ModelState which will help in fetching the field details.

Personally, I found Migration Framework damn interesting. I would love to 
optimize the Migration framework. Just need some more points which I can 
add in my proposed solution to make it more concrete.
I request fellow developers to please help me with their respective 
suggestions, thoughts or feedback, so that I may develop a better and 
practical proposal.

Regards,
Manav Agarwal

-- 
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/057f80c3-93c1-4d05-868d-89a9eaa40ceen%40googlegroups.com.

Re: GSoC Proposal: (Migrations) Adapt schema editors to operate from model states instead of fake rendered models.

[Manav Agarwal]

I have added the proposed solution in the proposal. 
I request fellow developers to please help me with their respective 
suggestions, thoughts or feedback, so that I may develop a better and 
practical proposal.

Regards,
Manav Agarwal

On Friday, April 2, 2021 at 3:09:46 AM UTC+5:30 Manav Agarwal wrote:

> Hello everyone,
> My name is Manav. I’m a Computer Science and Engineering junior at Dr. 
> A.P.J. Abdul Kalam Technical University in India.
> I started contributing to Django in October 2020 and have solved many issues 
> on trac 
> <https://code.djangoproject.com/query?owner=~manav014&status=assigned&status=closed&status=new&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id>
> .
> I read through the GSoC Idea List and the Migration topic stood out for 
> me. I found the idea to adapt schema editors to operate from model states 
> instead of fake rendered models really interesting.
> I am working on this for the last 1 month and I have made myself familiar 
> with the whole migrations framework codebase. I drafted a basic proposal 
> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> in 
> which I would be updating the complete solution after some discussion to 
> make the solution more concrete, practical, and effective.
> The problem with the Migration framework is briefly described in the 
> proposal 
> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> 
> itself. 
> After understanding the problem I came up with a few solutions which are 
> listed below:
>
>1. As Suggested by @MarkusH <https://forum.djangoproject.com/u/markush>, 
>A central registry to store all dependencies in django.apps.registry.Apps
>
>Or
>
>2. Designing a new metaclass for ModelState just like we have ModelBase 
>
> <https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/base.py#L72>
>  
>for Model. As then we would be able to use Options 
>
> <https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/options.py#L64>
>  
>with _meta in ModelState which will help in fetching the field details.
>
> Personally, I found Migration Framework damn interesting. I would love to 
> optimize the Migration framework. Just need some more points which I can 
> add in my proposed solution to make it more concrete.
> I request fellow developers to please help me with their respective 
> suggestions, thoughts or feedback, so that I may develop a better and 
> practical proposal.
>
> Regards,
> Manav Agarwal
>

-- 
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/af62fe52-96d7-4c95-a9ed-16d16832e001n%40googlegroups.com.

Re: GSoC Proposal: (Migrations) Adapt schema editors to operate from model states instead of fake rendered models.

[Manav Agarwal]

Link for the proposal - 
https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae

On Monday, April 5, 2021 at 8:41:32 AM UTC+5:30 Manav Agarwal wrote:

> I have added the proposed solution in the proposal. 
> I request fellow developers to please help me with their respective 
> suggestions, thoughts or feedback, so that I may develop a better and 
> practical proposal.
>
> Regards,
> Manav Agarwal
>
> On Friday, April 2, 2021 at 3:09:46 AM UTC+5:30 Manav Agarwal wrote:
>
>> Hello everyone,
>> My name is Manav. I’m a Computer Science and Engineering junior at Dr. 
>> A.P.J. Abdul Kalam Technical University in India.
>> I started contributing to Django in October 2020 and have solved many issues 
>> on trac 
>> <https://code.djangoproject.com/query?owner=~manav014&status=assigned&status=closed&status=new&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id>
>> .
>> I read through the GSoC Idea List and the Migration topic stood out for 
>> me. I found the idea to adapt schema editors to operate from model states 
>> instead of fake rendered models really interesting.
>> I am working on this for the last 1 month and I have made myself familiar 
>> with the whole migrations framework codebase. I drafted a basic proposal 
>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> in 
>> which I would be updating the complete solution after some discussion to 
>> make the solution more concrete, practical, and effective.
>> The problem with the Migration framework is briefly described in the 
>> proposal 
>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> 
>> itself. 
>> After understanding the problem I came up with a few solutions which are 
>> listed below:
>>
>>1. As Suggested by @MarkusH 
>><https://forum.djangoproject.com/u/markush>, A central registry to 
>>store all dependencies in django.apps.registry.Apps
>>
>>Or
>>
>>2. Designing a new metaclass for ModelState just like we have 
>>ModelBase 
>>
>> <https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/base.py#L72>
>>  
>>for Model. As then we would be able to use Options 
>>
>> <https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/options.py#L64>
>>  
>>with _meta in ModelState which will help in fetching the field 
>>details.
>>
>> Personally, I found Migration Framework damn interesting. I would love to 
>> optimize the Migration framework. Just need some more points which I can 
>> add in my proposed solution to make it more concrete.
>> I request fellow developers to please help me with their respective 
>> suggestions, thoughts or feedback, so that I may develop a better and 
>> practical proposal.
>>
>> Regards,
>> Manav Agarwal
>>
>

-- 
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/6bcbfb8d-f5a3-409c-b5f9-a5faa3f5151en%40googlegroups.com.

Re: GSoC Proposal: (Migrations) Adapt schema editors to operate from model states instead of fake rendered models.

[Manav Agarwal]

Thank You Carlton for the feedback.

As per your suggestion, I have increased the clarity of the proposal
<https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> with
some code and implementation. I will try to maximize the clarity as much
as possible.

Till then, May you please suggest, that Shall I share my proposal as a
draft at GSoC Portal <https://summerofcode.withgoogle.com/>.

Also, it would be great if you may suggest the possible improvement areas
in the proposal
<https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae>, or
does it seems fine?

Regards
Manav Agarwal

On Tue, Apr 6, 2021 at 7:09 PM Carlton Gibson 
wrote:

> Hi Manav.
>
> Sorry for the late reply.
>
> Your proposal looks very good, and your previous contributions are
> noticed.
> You’ve obviously taken time to look at it in depth.
>
> I think just going over it this week as time allows to maximise clarity is
> worth it. That’s always time well spent. (Generally there are a lot of
> applications, so making yours stand out as focused and to the point both
> demonstrates your capacity and makes the reviewer’s job easier.)
>
> I hope that helps.
>
> Kind regards, Carlton
>
> On Mon, 5 Apr 2021 at 05:12, Manav Agarwal  wrote:
>
>> Link for the proposal -
>> https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae
>>
>> On Monday, April 5, 2021 at 8:41:32 AM UTC+5:30 Manav Agarwal wrote:
>>
>>> I have added the proposed solution in the proposal.
>>> I request fellow developers to please help me with their respective
>>> suggestions, thoughts or feedback, so that I may develop a better and
>>> practical proposal.
>>>
>>> Regards,
>>> Manav Agarwal
>>>
>>> On Friday, April 2, 2021 at 3:09:46 AM UTC+5:30 Manav Agarwal wrote:
>>>
>>>> Hello everyone,
>>>> My name is Manav. I’m a Computer Science and Engineering junior at Dr.
>>>> A.P.J. Abdul Kalam Technical University in India.
>>>> I started contributing to Django in October 2020 and have solved many 
>>>> issues
>>>> on trac
>>>> <https://code.djangoproject.com/query?owner=~manav014&status=assigned&status=closed&status=new&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id>
>>>> .
>>>> I read through the GSoC Idea List and the Migration topic stood out for
>>>> me. I found the idea to adapt schema editors to operate from model states
>>>> instead of fake rendered models really interesting.
>>>> I am working on this for the last 1 month and I have made myself
>>>> familiar with the whole migrations framework codebase. I drafted a basic
>>>> proposal
>>>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> in
>>>> which I would be updating the complete solution after some discussion to
>>>> make the solution more concrete, practical, and effective.
>>>> The problem with the Migration framework is briefly described in the
>>>> proposal
>>>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae>
>>>> itself.
>>>> After understanding the problem I came up with a few solutions which
>>>> are listed below:
>>>>
>>>>1. As Suggested by @MarkusH
>>>><https://forum.djangoproject.com/u/markush>, A central registry to
>>>>store all dependencies in django.apps.registry.Apps
>>>>
>>>>Or
>>>>
>>>>2. Designing a new metaclass for ModelState just like we have
>>>>ModelBase
>>>>
>>>> <https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/base.py#L72>
>>>>    for Model. As then we would be able to use Options
>>>>
>>>> <https://github.com/django/django/blob/9ee693bd6cf4074f04ec51c6f3cfe87cad392f12/django/db/models/options.py#L64>
>>>>with _meta in ModelState which will help in fetching the field
>>>>details.
>>>>
>>>> Personally, I found Migration Framework damn interesting. I would love
>>>> to optimize the Migration framework. Just need some more points which I can
>>>> add in my proposed solution to make it more concrete.
>>>> I request fellow developers to please help me with their respective
>>>> suggestions, thoughts or feedback, so that I may develop a better and
>>>> practical proposal.
>>>>
&

Re: GSoC Proposal: (Migrations) Adapt schema editors to operate from model states instead of fake rendered models.

[Manav Agarwal]

Hey Carlton.

I have submitted the proposal.
Also, Your suggestion of adding tests with the introduction of a new
central registry seems great and I have implemented the same in phase 1.
Also, I already added all the points suggested by Simon Charette from the
discussion(
https://groups.google.com/g/django-developers/c/_ohBzsuomqw/m/cEI8eoK7BQAJ).
Last but not least, I will try to make my proposal more clear in the coming
week till the deadline.
I understand that as the proposal is detailed you will have to sit down
with it more fully but you don't have time for the same and It's totally
fine.

Thank You for your suggestions that always help a lot.


On Wed, Apr 7, 2021 at 7:09 PM Carlton Gibson 
wrote:

> Hi Manav.
>
> You should definitely submit. Your proposal is quite detailed, so I'd need
> to sit down with it more fully than I have time to comment on this week.
> (But that's OK — even if your implementation idea needs revision, THAT
> you've considered it is important.)
>
> Having said that:
>
> * You have "testing & docs" tacked on at the end in your schedule.
> Identify the phases and include time to write the tests as you go. In phase
> 1, how will you know that your central registry is correctly tracking model
> relationships unless you write tests? (You won't...)
>
> * Maybe you did this already but, review the points Simon Charette made in
> the thread on this topic last year:
> https://groups.google.com/g/django-developers/c/_ohBzsuomqw/m/cEI8eoK7BQAJ
> — There are large parts of a solution to this problem there. It would be
> good if on review your proposal uses Simon's suggestions.
>
> Please do use this week to make your proposal as good as you can and
> submit. (I can't see that I'll have capacity to review another draft, but
> equally you should have enough to go on now.)
>
> I wish you luck!
>
> Kind Regards,
>
> Carlton
>
>
> On Wednesday, 7 April 2021 at 08:13:54 UTC+2 dpsma...@gmail.com wrote:
>
>> Thank You Carlton for the feedback.
>>
>> As per your suggestion, I have increased the clarity of the proposal
>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> with
>> some code and implementation. I will try to maximize the clarity as much
>> as possible.
>>
>> Till then, May you please suggest, that Shall I share my proposal as a
>> draft at GSoC Portal <https://summerofcode.withgoogle.com/>.
>>
>> Also, it would be great if you may suggest the possible improvement areas
>> in the proposal
>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae>, or
>> does it seems fine?
>>
>> Regards
>> Manav Agarwal
>>
>> On Tue, Apr 6, 2021 at 7:09 PM Carlton Gibson 
>> wrote:
>>
>>> Hi Manav.
>>>
>>> Sorry for the late reply.
>>>
>>> Your proposal looks very good, and your previous contributions are
>>> noticed.
>>> You’ve obviously taken time to look at it in depth.
>>>
>>> I think just going over it this week as time allows to maximise clarity
>>> is worth it. That’s always time well spent. (Generally there are a lot of
>>> applications, so making yours stand out as focused and to the point both
>>> demonstrates your capacity and makes the reviewer’s job easier.)
>>>
>>> I hope that helps.
>>>
>>> Kind regards, Carlton
>>>
>>> On Mon, 5 Apr 2021 at 05:12, Manav Agarwal  wrote:
>>>
>>>> Link for the proposal -
>>>> https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae
>>>>
>>>> On Monday, April 5, 2021 at 8:41:32 AM UTC+5:30 Manav Agarwal wrote:
>>>>
>>>>> I have added the proposed solution in the proposal.
>>>>> I request fellow developers to please help me with their respective
>>>>> suggestions, thoughts or feedback, so that I may develop a better and
>>>>> practical proposal.
>>>>>
>>>>> Regards,
>>>>> Manav Agarwal
>>>>>
>>>>> On Friday, April 2, 2021 at 3:09:46 AM UTC+5:30 Manav Agarwal wrote:
>>>>>
>>>>>> Hello everyone,
>>>>>> My name is Manav. I’m a Computer Science and Engineering junior at
>>>>>> Dr. A.P.J. Abdul Kalam Technical University in India.
>>>>>> I started contributing to Django in October 2020 and have solved many 
>>>>>> issues
>>>>>> on trac
>>>>>> <https://code.djangoproject.com/query?owner=~manav014&status=assigned&

Re: GSoC Proposal: (Migrations) Adapt schema editors to operate from model states instead of fake rendered models.

[Manav Agarwal]

Hello everyone,
I am so very thankful to everyone who helped me out with my project idea 
and proposal. The proposal is accepted and I will give my best to 
accomplish as I have promised.
On Thursday, April 8, 2021 at 7:17:58 AM UTC+5:30 Manav Agarwal wrote:

> Hey Carlton.
>
> I have submitted the proposal.
> Also, Your suggestion of adding tests with the introduction of a new 
> central registry seems great and I have implemented the same in phase 1.
> Also, I already added all the points suggested by Simon Charette from the 
> discussion(
> https://groups.google.com/g/django-developers/c/_ohBzsuomqw/m/cEI8eoK7BQAJ
> ).
> Last but not least, I will try to make my proposal more clear in the 
> coming week till the deadline. 
> I understand that as the proposal is detailed you will have to sit down 
> with it more fully but you don't have time for the same and It's totally 
> fine.
>
> Thank You for your suggestions that always help a lot.
>
>
> On Wed, Apr 7, 2021 at 7:09 PM Carlton Gibson  
> wrote:
>
>> Hi Manav. 
>>
>> You should definitely submit. Your proposal is quite detailed, so I'd 
>> need to sit down with it more fully than I have time to comment on this 
>> week. 
>> (But that's OK — even if your implementation idea needs revision, THAT 
>> you've considered it is important.) 
>>
>> Having said that: 
>>
>> * You have "testing & docs" tacked on at the end in your schedule. 
>> Identify the phases and include time to write the tests as you go. In phase 
>> 1, how will you know that your central registry is correctly tracking model 
>> relationships unless you write tests? (You won't...)
>>
>> * Maybe you did this already but, review the points Simon Charette made 
>> in the thread on this topic last year: 
>> https://groups.google.com/g/django-developers/c/_ohBzsuomqw/m/cEI8eoK7BQAJ 
>> — There are large parts of a solution to this problem there. It would be 
>> good if on review your proposal uses Simon's suggestions. 
>>
>> Please do use this week to make your proposal as good as you can and 
>> submit. (I can't see that I'll have capacity to review another draft, but 
>> equally you should have enough to go on now.) 
>>
>> I wish you luck! 
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>> On Wednesday, 7 April 2021 at 08:13:54 UTC+2 dpsma...@gmail.com wrote:
>>
>>> Thank You Carlton for the feedback.
>>>
>>> As per your suggestion, I have increased the clarity of the proposal 
>>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae> 
>>> with some code and implementation. I will try to maximize the clarity as 
>>> much as possible.
>>>
>>> Till then, May you please suggest, that Shall I share my proposal as a 
>>> draft at GSoC Portal <https://summerofcode.withgoogle.com/>.
>>>
>>> Also, it would be great if you may suggest the possible improvement 
>>> areas in the proposal 
>>> <https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae>, or 
>>> does it seems fine?
>>>
>>> Regards
>>> Manav Agarwal
>>>
>>> On Tue, Apr 6, 2021 at 7:09 PM Carlton Gibson  
>>> wrote:
>>>
>>>> Hi Manav. 
>>>>
>>>> Sorry for the late reply. 
>>>>
>>>> Your proposal looks very good, and your previous contributions are 
>>>> noticed. 
>>>> You’ve obviously taken time to look at it in depth. 
>>>>
>>>> I think just going over it this week as time allows to maximise clarity 
>>>> is worth it. That’s always time well spent. (Generally there are a lot of 
>>>> applications, so making yours stand out as focused and to the point both 
>>>> demonstrates your capacity and makes the reviewer’s job easier.) 
>>>>
>>>> I hope that helps. 
>>>>
>>>> Kind regards, Carlton 
>>>>
>>>> On Mon, 5 Apr 2021 at 05:12, Manav Agarwal  wrote:
>>>>
>>>>> Link for the proposal - 
>>>>> https://gist.github.com/manav014/9b0feb734e4d140eef1913340602d2ae
>>>>>
>>>>> On Monday, April 5, 2021 at 8:41:32 AM UTC+5:30 Manav Agarwal wrote:
>>>>>
>>>>>> I have added the proposed solution in the proposal. 
>>>>>> I request fellow developers to please help me with their respective 
>>>>>> suggestions, thoughts or feedback, so that I may develop a better and 
&

Re: How to get started with contribution

[Manav Agarwal]

Hey Sudhanshu,
Start with Git/GitHub and then Have a good hands-on with Django. After
that, you may visit Contributing to Django | Django documentation | Django
(djangoproject.com)
<https://docs.djangoproject.com/en/dev/internals/contributing/> to get
started with contributing to Django.
Let me know if I can help in any other way.

On Thu, Oct 28, 2021 at 11:37 PM Sudhanshu Gupta 
wrote:

> Respected sir/madam,
> I am Sudhanshu gupta, a electronics undergrad, Ihave just entered my
> second year at bangalore institute of technology (BIT). I am new to open
> source contributions but I am well aware of python and django. I
> would love to contribute to your organisation but could you please tell me
> how to get started?
> Hoping to hear from you soon.
> Regards
> Sudhanshu
>
> --
> 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/bc727963-c842-4141-9544-b6c9c7025e41n%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/bc727963-c842-4141-9544-b6c9c7025e41n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Regards
Manav Agarwal

[image: https://www.linkedin.com/in/manav-agarwal-982553190/]
<https://www.linkedin.com/in/manav-agarwal-982553190/>

*"If your actions inspire others to dream more, learn more, do more and
become more, you are a leader.”*

-- 
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/CACbxD0DgKoeu-9pnuk1ePNnDQ6RuH_uXddmYbDeJ4n-vW0LQhg%40mail.gmail.com.

Re: How to get started with contribution

[Manav Agarwal]

I think this link may help:
https://docs.djangoproject.com/en/dev/internals/contributing/

On Wed, Nov 24, 2021, 7:33 PM shahil ramchandani <
shahilramchand...@gmail.com> wrote:

> Respected Sir/Madam,
> I am Sahil Ramchandani, a Electrical Engineering undergraduate, I am in
> Government Engineering Collage - Rajkot(GTU) in my second year. I am new to
> open source contributions but I am well aware of python and currently
> learning Django framework. I would love to contribute to your organization
> but could you please tell me how to get started?
> Hoping to hear from you soon.
> Regards
> Sahil
>
> --
> 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/84bebe4d-5a57-4957-8341-ef811ad0115an%40googlegroups.com
> 
> .
>

-- 
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/CACbxD0CvRX%3D9CcP6w_Fq-myihjx5YEok%2B417V7%2BVJj7sTnHaLA%40mail.gmail.com.

Re: How to find good first issue

[Manav Agarwal]

You may find the Django Issue tracker at
https://code.djangoproject.com/query .
Also, for Good First Issue/ Easy Pickings Django issue tracker has a
separate tag with the name "Easy Picking" (
https://code.djangoproject.com/query?status=assigned&status=new&easy=1&desc=1&order=id
)

Regards,
Manav Agarwal

On Wed, Mar 9, 2022 at 7:32 PM CE003_Omi _Kakadiya <20ituos...@ddu.ac.in>
wrote:

> Hii djangoians, I am newbie in Open source and I wanted to ask that how I
> can find good first issue for documentation on Django
>
> Please someone help!!
> Regards
> Omi
>
> DISCLAIMER: The information transmitted is intended only for the person or
> entity to which it is addressed and may contain confidential and/or
> privileged material which is the intellectual property of Dharmsinh Desai
> University (D.D.U., Nadiad). Any review, retransmission, dissemination or
> other use of, or taking of any action in reliance upon this information by
> persons or entities other than the intended recipient is strictly
> prohibited. If you are not the intended recipient, or the employee, or
> agent responsible for delivering the message to the intended recipient
> and/or if you have received this in error, please contact the sender and
> delete the material from the computer or device. Dharmsinh Desai University
> does not take any liability or responsibility for any malicious
> codes/software and/or viruses/Trojan horses that may have been picked up
> during the transmission of this message. By opening and solely relying on
> the contents or part thereof this message, and taking action thereof, the
> recipient relieves the Dharmsinh Desai University of all the liabilities
> including any damages done to the recipient's pc/laptop/peripherals and
> other communication devices due to any reason.
>
> --
> 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/0a0109fb-d96a-437e-8bee-a1672f13da65n%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/0a0109fb-d96a-437e-8bee-a1672f13da65n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Regards
Manav Agarwal

[image: https://www.linkedin.com/in/manav-agarwal-982553190/]
<https://www.linkedin.com/in/manav-agarwal-982553190/>

*"If your actions inspire others to dream more, learn more, do more and
become more, you are a leader.”*

-- 
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/CACbxD0D2u-9AJOhxqPDkBYnDkGDC_c73%3DxGM3Nq1Nf3nOhFpxQ%40mail.gmail.com.

Re: Proposals of GSOC.

[Manav Agarwal]

You may find them on django developers mailing list in conversations and
search for gsoc there.

On Thu, Mar 10, 2022, 9:03 PM CE003_Omi _Kakadiya <20ituos...@ddu.ac.in>
wrote:

> Check out on the GSOC website . In that there is a section of past
> programs ==> select the year , select the organisation and you will get to
> know
> Regards
> OMi
>
> On Thursday, March 10, 2022 at 9:04:59 AM UTC+5:30 sarthak...@gmail.com
> wrote:
>
>> Can anyone share me old proposals of GSOC for django software
>> application.
>>
>
> DISCLAIMER: The information transmitted is intended only for the person or
> entity to which it is addressed and may contain confidential and/or
> privileged material which is the intellectual property of Dharmsinh Desai
> University (D.D.U., Nadiad). Any review, retransmission, dissemination or
> other use of, or taking of any action in reliance upon this information by
> persons or entities other than the intended recipient is strictly
> prohibited. If you are not the intended recipient, or the employee, or
> agent responsible for delivering the message to the intended recipient
> and/or if you have received this in error, please contact the sender and
> delete the material from the computer or device. Dharmsinh Desai University
> does not take any liability or responsibility for any malicious
> codes/software and/or viruses/Trojan horses that may have been picked up
> during the transmission of this message. By opening and solely relying on
> the contents or part thereof this message, and taking action thereof, the
> recipient relieves the Dharmsinh Desai University of all the liabilities
> including any damages done to the recipient's pc/laptop/peripherals and
> other communication devices due to any reason.
>
> --
> 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/2b2e6dba-2859-4cd0-b6a5-a1a4bb8d011bn%40googlegroups.com
> 
> .
>

-- 
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/CACbxD0Cxa7YTK2O2bRtn%2BhLCj_gxYHG703C9-PdRgCH0mu32sA%40mail.gmail.com.