RE: GSoC 2019 Update

2019-03-07 Thread Matthew Pava 
This is more for the ORM side of things. Something I would like to see is the 
Subquery object morphed into the equivalent of common table expressions and the 
possibility of having recursive common table expressions.  See 
https://code.djangoproject.com/ticket/28919.
The patches that I’ve seen simply add yet another object to the library. I once 
looked at the ORM internals to try to understand it, and I even found a video 
from James Bennett that discussed contributions to Django. Unfortunately, he 
quickly glossed over the ORM internals that I was really interested in learning 
more about, but it’s just because it’s so complex. Maybe simplifying that code 
is a project in and of itself, but I imagine that you would need expert 
understanding of Django.

From: django-developers@googlegroups.com 
[mailto:django-developers@googlegroups.com] On Behalf Of Tim Graham
Sent: Thursday, March 7, 2019 9:01 AM
To: Django developers (Contributions to Django itself)
Subject: Re: GSoC 2019 Update

I agree that a cross-database JSONField probably wouldn't take 3 months to 
implement -- but it would be up to the student to write a proposal and timeline 
that demonstrates there's 12 weeks of work. Students are supposed to be working 
full time.

GSoC requires writing code so an acceptable project can't be exclusively 
documentation.

The problem is that we need students to contribute to Django beforehand so we 
have some assurance they do good work. Also, students need significant 
familiarity with Django to write their proposal. It's unlikely a student can do 
all this in the next 3 weeks (alongside a normal course load).

On Thursday, March 7, 2019 at 6:22:02 AM UTC-5, Carlton Gibson wrote:
Hi all.

We were accepted as an Org to GSoC, so we can accept applications from the end 
of the month.

I've updated the Wiki page...

https://code.djangoproject.com/wiki/SummerOfCode2019

... but if you have project ideas it would be good if you could add them!


I keep hearing, "Django's Mature", "There are no suitable projects" but I look 
at the >1300 accepted tickets and, well... I just don't believe that really. 

Taking Aymeric's advice, I broke down the accepted tickets by component:



[Django-Accepted-tickets-by-component.png]



The top 4 there are:



* ORM

* Admin

* Documentation

* Migrations.



For the ORM, I think the cross-DB JSONField would be a great project. Florian 
worried it was too small in scope, but if it existed by the end of the summer, 
I would call that a success.



ORM experts: what else though? (Anything?)



For the Admin, there are a whole load of "filters" tickets. (Including the 
search issue from the thread here the other day). I've added working on that as 
an idea. But anything else?



  *   What we could really do with is someone becoming an expert in a component 
and taking on a bunch of issues — Would that count as an acceptable project?
  *   Could we do that for Documentation? (Would require strong written 
English. Focus on Clarity. But...)

Other ideas around the docker-box project and CI? Could we take input there?
Translations tooling and flow?
And so on...?

Last chance to speak up. 

I'm hopeful we can get a decent application (or a few…) Let's see.

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 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/6b9c2356-1878-4e45-9026-2a9ac6b9f193%40googlegroups.com.
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/0667d821cab943eda763d5a1bb041668%40iss2.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC 2019 Update

2019-03-07 Thread Tim Graham 
I agree that a cross-database JSONField probably wouldn't take 3 months to 
implement -- but it would be up to the student to write a proposal and 
timeline that demonstrates there's 12 weeks of work. Students are supposed 
to be working full time.

GSoC requires writing code so an acceptable project can't be exclusively 
documentation. 

The problem is that we need students to contribute to Django beforehand so 
we have some assurance they do good work. Also, students need significant 
familiarity with Django to write their proposal. It's unlikely a student 
can do all this in the next 3 weeks (alongside a normal course load).

On Thursday, March 7, 2019 at 6:22:02 AM UTC-5, Carlton Gibson wrote:
>
> Hi all.
>
> We were accepted as an Org to GSoC, so we can accept applications from the 
> end of the month. 
>
> I've updated the Wiki page...
>
> https://code.djangoproject.com/wiki/SummerOfCode2019
>
> ... but *if you have project ideas *it would be good if you could add 
> them!
>
>
> I keep hearing, "Django's Mature", "There are no suitable projects" but I 
> look at the >1300 accepted tickets and, well... I just don't believe that 
> really. 
>
> Taking Aymeric's advice, I broke down the accepted tickets by component: 
>
>
> [image: Django-Accepted-tickets-by-component.png]
>
>
> The top 4 there are: 
>
>
> * ORM
>
> * Admin
>
> * Documentation
>
> * Migrations. 
>
>
> For the *ORM*, I think the cross-DB JSONField would be a great project. 
> Florian worried it was too small in scope, but if it existed by the end of 
> the summer, I would call that a success. 
>
>
> ORM experts: what else though? (Anything?) 
>
>
> For the *Admin*, there are a whole load of "filters" tickets. (Including 
> the search issue from the thread here the other day). I've added working on 
> that as an idea. But anything else? 
>
>
>
>- What we could really do with is someone becoming an expert in a 
>component and taking on a bunch of issues — Would that count as an 
>acceptable project? 
>- Could we do that for *Documentation*? (Would require strong written 
>English. Focus on Clarity. But...) 
>
>
> Other ideas around the *docker-box* project and *CI*? Could we take input 
> there? 
> Translations tooling and flow? 
> And so on...? 
>
> Last chance to speak up. 
>
> I'm hopeful we can get a decent application (or a few…) Let's see. 
>
> 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 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/6b9c2356-1878-4e45-9026-2a9ac6b9f193%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GSoC 2019 Update

2019-03-07 Thread Carlton Gibson 
Hi all.

We were accepted as an Org to GSoC, so we can accept applications from the 
end of the month. 

I've updated the Wiki page...

https://code.djangoproject.com/wiki/SummerOfCode2019

... but *if you have project ideas *it would be good if you could add them!


I keep hearing, "Django's Mature", "There are no suitable projects" but I 
look at the >1300 accepted tickets and, well... I just don't believe that 
really. 

Taking Aymeric's advice, I broke down the accepted tickets by component: 


[image: Django-Accepted-tickets-by-component.png]


The top 4 there are: 


* ORM

* Admin

* Documentation

* Migrations. 


For the *ORM*, I think the cross-DB JSONField would be a great project. 
Florian worried it was too small in scope, but if it existed by the end of 
the summer, I would call that a success. 


ORM experts: what else though? (Anything?) 


For the *Admin*, there are a whole load of "filters" tickets. (Including 
the search issue from the thread here the other day). I've added working on 
that as an idea. But anything else? 



   - What we could really do with is someone becoming an expert in a 
   component and taking on a bunch of issues — Would that count as an 
   acceptable project? 
   - Could we do that for *Documentation*? (Would require strong written 
   English. Focus on Clarity. But...) 
   

Other ideas around the *docker-box* project and *CI*? Could we take input 
there? 
Translations tooling and flow? 
And so on...? 

Last chance to speak up. 

I'm hopeful we can get a decent application (or a few…) Let's see. 

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 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/aaa941a3-3ea7-4219-b558-b7ba89400772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.