Participation in GSOC 2020

[SaNju]

Hello Sir/Mam, 
I am Sanju  from the Rajdhani engineering college Jaipur. 
During my stay of onr and half years at REC Jaipur, I had participated in 
various roles, I have worked with different technologies in last one year: 
React*, backend development, * etc, different frameworks like *Django* and 
*flask*, databases such as *MySQL, POSTGRESQL* 
I wish to be an active participant for your organization in the GSoC 2020.
Kindly let me know about the necessary steps which I need to follow in 
order to participate and be an active developer for your organization in 
GSoC 2020

i have one year experince in python full stack developement 

Looking forward to hearing from you.

-- 
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/6d230bca-7841-4cbd-906e-751a3c4b90den%40googlegroups.com.

Re: Participation in GSOC 2020

[Kacper Szmigiel]

Bruh, GSoC 2020 has ended in August

pt., 25 gru 2020, 15:53 użytkownik SaNju  napisał:

> Hello Sir/Mam,
> I am Sanju  from the Rajdhani engineering college Jaipur.
> During my stay of onr and half years at REC Jaipur, I had participated in
> various roles, I have worked with different technologies in last one year:
> React*, backend development, * etc, different frameworks like *Django*
>  and *flask*, databases such as *MySQL, POSTGRESQL*
> I wish to be an active participant for your organization in the GSoC 2020.
> Kindly let me know about the necessary steps which I need to follow in
> order to participate and be an active developer for your organization in
> GSoC 2020
>
> i have one year experince in python full stack developement
>
> Looking forward to hearing from you.
>
> --
> 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/6d230bca-7841-4cbd-906e-751a3c4b90den%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/CAFfZ%2Bb75W6vpyqUJQPYoRJpBSUd2a-%3DCHxwLta6c%2BRKNXXRFwg%40mail.gmail.com.

Re: Participation in GSOC 2021

[SaNju]

Sorry for 2021

On Fri, Dec 25, 2020, 8:34 PM Kacper Szmigiel 
wrote:

> Bruh, GSoC 2020 has ended in August
>
> pt., 25 gru 2020, 15:53 użytkownik SaNju  napisał:
>
>> Hello Sir/Mam,
>> I am Sanju  from the Rajdhani engineering college Jaipur.
>> During my stay of onr and half years at REC Jaipur, I had participated in
>> various roles, I have worked with different technologies in last one year:
>> React*, backend development, * etc, different frameworks like *Django*
>>  and *flask*, databases such as *MySQL, POSTGRESQL*
>> I wish to be an active participant for your organization in the GSoC 2020.
>> Kindly let me know about the necessary steps which I need to follow in
>> order to participate and be an active developer for your organization in
>> GSoC 2020
>>
>> i have one year experince in python full stack developement
>>
>> Looking forward to hearing from you.
>>
>> --
>> 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/6d230bca-7841-4cbd-906e-751a3c4b90den%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/CAFfZ%2Bb75W6vpyqUJQPYoRJpBSUd2a-%3DCHxwLta6c%2BRKNXXRFwg%40mail.gmail.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/CAHXDXw41GTJNsBNuehWjKOMGPF1hbaOC86NZ1gjLx6o%2BmPPbsA%40mail.gmail.com.

Re: Integrating migrations with the check framework

[Paveł Tyślacki]

A few thoughts: migration downtime depends from different points:

- changes itself (existence of exclusive locks in migration especially with
other changes in same transaction, luck of backward incompatible migrations
between current and new state)
- amount of user data
- load to application
- number of replicas and application instances runned (you probably cannot
apply migrations and update code on all of instances simultaneously, eg.
this process can be asynchronous)

There also can be different tradeoffs trying to solve different issues on
the way to avoid downtime.

Anyway strong apis to detect potential bad cases and replace current
migrations sounds like a good idea.

Paveł

чт, 24 дек. 2020 г. в 19:06, David Wobrock :

> Hi everyone,
>
> I agree that there is room for improvement around migrations in Django
> with respect to the expected downtime/table locking. But I don’t know
> whether this should in Django itself or handled by a 3rd party library.
>
> I’m maintaining the django-migration-linter (the very idea was to have an
> automated tool since reviewing migrations is not something new Django devs
> can do easily), which currently tackles another issue than the one you
> mention. It tries, in a best effort manner as you’ve seen through the SQL
> checks, to understand if the migration is introducing a backward
> incompatible change to your schema, which will desynchronize your code and
> database schema (so you’ll get errors when you deploy one without the other
> – and you’ll have a hard time doing a rollback).
>
> It’s a different aspect, compared to checking that the forward migration
> will be instant and non-locking. However, it is planned to add this to the
> linter too (https://github.com/3YOURMIND/django-migration-linter/issues/99
> ).
>
> You’ve noticed that it’s based on the SQL strings, which has advantages
> and drawbacks. The checks are easy to implement (just a set of rules
> basically), it could be completely Django-agnostic and it can lint RunSQL
> operations. But it’s a bit harder to represent a state when multiple SQL
> statements are executed, to check if they cancel each other out for
> instance.
>
>
>
> An idea about something that could be in Django would be, somehow like the
> “database features”, marking for each migration operation (AlterField,
> AddField, …) on each database backend, if they can potentially mean
> downtime. It would be a hint about the risk of the migration, and display a
> warning if necessary.
> Going one step further, for some operations, Django could query the number
> of rows of the corresponding table and have some risk heuristics.
> Basically: “you’re adding a column to a table with less than 100 rows, this
> should not be risky” or “you’re adding a column to a table with millions of
> rows, be careful!”.
> However, as these heuristics would be rather arbitrary, I’m not sure that
> the Django project would want to make this kind of choices – so it might be
> a better fit for a library. (what I’m describing is more or less the
> ultimate goal the django-migration-linter)
>
> Hope this gives some insights about the project and how it could help on
> this topic :)
>
> Cheers,
> David
>
>
> On 23/12/2020 19:02, Tom Forbes wrote:
>
> Thanks for all the input here!
>
> I didn’t know about django-migration-linter, and it does seem quite
> interesting. It works by looking at the complete set of SQL statements that
> would be run, and running regular expressions/string comparisons on it (
> https://github.com/3YOURMIND/django-migration-linter/blob/master/django_migration_linter/sql_analyser/base.py#L59-L62).
> I don’t hate this idea, but I think that having direct access to the
> migration objects themselves could greatly simplify the implementation.
>
> Django-pg-zero-downtime-migrations also looks interesting and is more
> in-line with what I was imagining (
> https://github.com/tbicr/django-pg-zero-downtime-migrations/blob/master/django_zero_downtime_migrations/backends/postgres/schema.py)
> - it overrides the schema editor to detect unsafe migrations, and provides
> a nice way to abort migrations that take locks for too long. However I feel
> that the implementation could be greatly simplified with some support for
> Django - you shouldn’t really need to override the schema editor, Django
> should pass you a list of operations and ask “is this safe?”. The results
> can be reported via the checks framework which allows application owners
> can decide to treat these warnings as errors or silence them as needed. It
> also brings those warnings front-and-centre while developing, rather than
> having it fail when running “migrate” later on in the deployment process.
>
> Django-safemigrate is very related and something I wanted to cover in a
> later message. I feel that some of this functionality could (or even
> should) be integrated with Django, as migrations in “real” apps are usually
> a two step process: you run the schema migrations, which might add

Participation in GSoC 2021.

[Kelyn Paul]

Hey guys, I'm new to the whole Google Summer of Code program. I would like
to be able to contribute to Django for GSoC 2021. If possible, please offer
me some guidance on what steps I need to take to accomplish this. Any
help would be greatly appreciated.

-- 
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/CAObrU5SN4rkONF49G_0jwB%3DbySWeqvt-nTF2nxG3%3DaTPs%2BFrtA%40mail.gmail.com.