GSoC 2019 Update

[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: 

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

[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).

[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.

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

[Carlton Gibson]

Hey Matthew. Good issue, yes. 🙂 Thanks. 

Hey Tim. Yes, you're probably right...

 I was going to leave GSoC, but people asked and my tick, if I've got one, is "widen the pool of contributors" — so it seemed worth the effort to at least fill in the form. 

Maybe we get an applicant. Maybe we don't. 

Regardless, I'm using it as an opportunity to pull together ideas on how people can get going contributing. 

This was the big take-away from DjangoCon last year for me, so, ever-so-slowly-as-ever-in-oss I'm trying to make moves there. 

In part, I want to keep a Project Idea list going all the time. (I'd also like to keep "Are you a student? We're keen on GSoC" going all year too, since I totally agree that the gap between new-year and now isn't long enough to really get to know anyone...) 

So, if people have project ideas, I still want to hear them. 

I hope that makes sense. 

(I'm quite optimistic about this stuff really.) 

Kind Regards,

Carlton

[Muhammad Faraz]

i am taking part first time in any open source project using summer of code  i was think would the idea of integration of  django with front ends like vuejs will it be acceptable front end support especially  for vuejs is great in laravel due to watch package so i was thinking would proposal of creating module that make the integration of font end frame works with django easy will it be acceptable ? and can you recommend any of your ideas to me i have worked on python especially image steganography 

[Tobias McNulty]

On Thu, Mar 7, 2019 at 6:22 AM Carlton Gibson <carlton...@gmail.com> wrote:

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. 

+1 -- and I'd rather a project be too small than too large (and go unfinished). If it goes that quickly I'm sure we/they can always find more to do, as your open tickets graph suggests. :) Perhaps a good proposal would be to start with the cross-DB JSONField and then move to ORM tickets X, Y, Z if the first is merged in time?

Cheers,

Tobias McNulty
Chief Executive Officer

tob...@caktusgroup.com
www.caktusgroup.com