Re: Fellow Reports - December 2019

[Mariusz Felisiak]

Week ending December 22, 2019.

Released Django 3.0.1, 2.2.9, and 1.11.27.

*Triaged:*
https://code.djangoproject.com/ticket/31090 - Log when DB transactions are 
commited and rollbacked. (accepted)
https://code.djangoproject.com/ticket/31091 - ConnectionResetError: [Errno 
104] Connection reset by peer with a simple GET call. (invalid)
https://code.djangoproject.com/ticket/31093 - Extend permission backend 
with get_queryset(user, model). (wontfix)
https://code.djangoproject.com/ticket/31094 - Subquery uses ungrouped 
column "table.column" from outer query. (accepted)
https://code.djangoproject.com/ticket/31095 - Related Manager set() should 
prepare values before checking for missing elements. (accepted)
https://code.djangoproject.com/ticket/31098 - has_add_permission() takes 2 
positional arguments but 3 were given. (invalid)
https://code.djangoproject.com/ticket/31099 - ValueError: Non-reversible 
reg-exp portion: '(?i'. (invalid)
https://code.djangoproject.com/ticket/31015 - loss of precision of geometry 
coordinates on Oracle 18 (needsinfo)
https://code.djangoproject.com/ticket/31104 - OneToOneField strange 
behavior when saving reference. (duplicate)
https://code.djangoproject.com/ticket/31106 - Adding foreign keys and 
instances in the same migration crashes on PostgreSQL 10+. (accepted)
https://code.djangoproject.com/ticket/31107 - Autocomplete fields in the 
admin do not respect limit_choices_to. (duplicate)
https://code.djangoproject.com/ticket/31110 - Typo in 
docs/ref/models/expressions.txt. (accepted)
https://code.djangoproject.com/ticket/3 - Schema Editor's add_field not 
able to add foreign key field (wontfix)
https://code.djangoproject.com/ticket/31113 - Throw warning when field 
length is greater than max_length in SQLite. (duplicate)
https://code.djangoproject.com/ticket/31112 - Schema Editor's add_field 
does not append "_id" to the foreign key column. (invalid)

*Reviewed/committed:*
https://github.com/django/django/pull/12220 - Fixed #31076 -- Fixed dbshell 
crash on Windows with Python < 3.8.
https://github.com/django/django/pull/12215 - Fixed #31088 -- Added support 
for websearch searching in SearchQuery.
https://github.com/django/django/pull/12225 - Fixed #31086 -- Improved 
error message for admin model inlines with more than one foreign key to the 
same parent.
https://github.com/django/django/pull/11811 - Fixed #30585 -- Added {% 
translate %} and {% blocktranslate %} template tags.
https://github.com/django/django/pull/12227 - Fixed #31094 -- Included 
columns referenced by subqueries in GROUP BY on aggregations.
https://github.com/django/django/pull/12231 - Fixed #31095 -- Made 
RelatedManager.set() preserve existing m2m relations with an invalid type.
https://github.com/django/django/pull/11791 - Documentation updates: Sites 
reference and assertNumQueries().
https://github.com/django/django/pull/11773 - Refs #30767 -- Improved 
deployment documentation.
https://github.com/django/django/pull/12236 - Fixed #31110 -- Fixed typo in 
docs/ref/models/expressions.txt.

*Authored:*
https://github.com/django/django/pull/12232 - Fixed #31106 -- Fixed 
migrations crash on PostgreSQL 10+ when adding FK constraints inline and 
changing data.

Best regards,
Mariusz

-- 
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/287bbccc-8b74-44c2-b32b-94ca0a57c8ae%40googlegroups.com.

United Nations: Expel Maduro from the Human Rights Council!

[franklinitiel]

Hola,

Acabo de firmar la petición de "United Nations: Expel Maduro from the Human
Rights Council!" y me encantaría que me ayudaras sumando tu firma.

Nuestro objetivo es llegar a 150,000 firmas y necesitamos más apoyo. Para
obtener más información y firmar la petición puedes abrir el siguiente link:

http://chng.it/GpgXc5d9WW

¡Gracias!
Franklin

-- 
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/CAMsjBK%2Bg-8khceMy2nwxozKK5BFQLxqW3sjLeE_sViAmvw8ARg%40mail.gmail.com.

Re: Sounding out for GSoC 2020.

[Aaryan Dewan]

Hi Carlton.

As I'm a Freshman in College, I'm totally new to the Open Source community. 
I have been using Python for two years and recently, I learned the Django 
Framework so I thought that it would be a great idea to contribute to it 
during my summer break through GSoC. 

I have read the Django contribution guide 
 and have 
looked at the previous year projects. 

This year (2020) I only seem to *understand* 2 of the proposed projects (in 
this thread) namely:

   - Two Factor authentication
   - Django case studies

Since you said in your post "Are there easier things that we could take 
"weaker" candidates for?...", are there any proposed projects yet that are 
of *low *complexity as I'm unable to judge the complexity of the proposed 
projects here. If so, please let me know so that I could start working on 
them ASAP.

Also, you gave a great presentation at DjangoCon US :-)

Regards,

Aaryan

On Tuesday, December 10, 2019 at 8:55:22 PM UTC+5:30, Carlton Gibson wrote:
>
> Hi all. 
>
> It's time to start thinking about Google Summer of Code (GSoC). If we're 
> going to participate and projects we might propose. 
>
> This year was interesting. Sage in particular did well putting together a 
> cross-db JSONField, but he was probably under-mentored, 
> since Mariusz has spent quite a bit of time reworking the PR, and still 
> has a bit to go, before we can pull it in, hopefully for 3.1
>
> So, one consideration we need to think about seriously is our capacity for 
> mentoring. (This isn't just about the candidate's ability — Sage was able 
> to implement all suggestions — we just didn't have as much capacity as we 
> might have liked to think about the requirement implementation — and there 
> were four of us actively giving some time each... — Anyhow, to think 
> about.) 
>
> Then it's projects. There are three that I have on my list that would 
> require a "competent candidate":
>
> 1. Work on the migrations. Markus mentioned a particular ticket here 
> but... 
> 2. Make the parallel test runner work on Windows. ("fork" vs "spawn")
>
> And 3, and this is the big one: 
>
> 3. Add 2FA to Django. 
>
> This has been raised a few times: 
>
> * 
> https://groups.google.com/d/topic/django-developers/T-kBSvry6z0/discussion
> * 
> https://groups.google.com/d/topic/django-developers/d92P2V0YrbI/discussion
>  
> * ... others... 
>
> If I'm honest, in 2020, it's the one "battery" I feel a little bit 
> embarrassed we haven't got a story for. Maybe it's not possible in a GSoC 
> type scope but... 
> — What would it look like? What can we leverage? Is it worth a go? 
>
> I'm looking at James, Florian, Joe, ... — who else has been keen here?
> I'm also looking at the Technical Board, which I'm thinking has (will 
> have) a new guiding role to come up with suggestions for the direction of 
> Django. 
>
>
> Other Projects: Are there other ideas? (Do you have one?) Are there easier 
> things that we could take "weaker" candidates for? But with that is there a 
> commitment for the mentoring help they'd need? 
>
> Anyhow, we have until January, so I'm just starting the discussion here. 
>
> 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/35a62cfd-77c8-4a23-91af-5c4422472849%40googlegroups.com.

GSoC 2020

[Nishchal Gupta]

Hello everyone,
  
This is Nishchal Gupta and I am current studying in KCNIT under (AKTU). I 
have just completed my third semester. 

I want to participate in Google Summer of Code 2020. I am familiar with 
Django framework and don't know the steps to be taken.

Also I don't have any idea whether the Organisation Django will participate 
in 2020 or not.  Also I am not familiar with ticketing and unit testing.

Can anybody guide me the step by step process in order to get selected in 
for GSoC 2020?

-- 
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/d61bcd25-daa5-4116-96e8-82c0a9ef8849%40googlegroups.com.

Re: GSoC 2020

[Abhijeet Viswa]

Hey,

Checkout Django's contribution guidelines here:
https://docs.djangoproject.com/en/dev/internals/contributing/
It details everything you need to know, from triaging of tickets to
unit testing.

On Mon, 23 Dec 2019 at 20:28, Nishchal Gupta  wrote:
>
> Hello everyone,
>
> This is Nishchal Gupta and I am current studying in KCNIT under (AKTU). I 
> have just completed my third semester.
>
> I want to participate in Google Summer of Code 2020. I am familiar with 
> Django framework and don't know the steps to be taken.
>
> Also I don't have any idea whether the Organisation Django will participate 
> in 2020 or not.  Also I am not familiar with ticketing and unit testing.
>
> Can anybody guide me the step by step process in order to get selected in for 
> GSoC 2020?
>
> --
> 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/d61bcd25-daa5-4116-96e8-82c0a9ef8849%40googlegroups.com.



-- 
Abhijeet

-- 
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/CAP1-YrodAGjU1ViB4Xacn%3DPiCwRRx_7sN4YdQRzVxr0i_WaC%2BQ%40mail.gmail.com.