Other ideas can be found in the DEPS repo 
too: https://github.com/django/deps/pulls

The only one of those 3 that would be GSOC doable (IMO) would be the query 
expression language one.

On Friday, 25 January 2019 01:43:13 UTC+11, Carlton Gibson wrote:
>
> Perhaps it's partly the GSoC doesn't cross the radar until just a few 
> weeks before the deadline... 🙃
>
> I'm happy to help mentor but also Django Core Mentorship is there...
> https://groups.google.com/forum/#!forum/django-core-mentorship
>
>
> One idea for a good project might be adding a cross DB JSONField as per 
> this thread
>
>    
> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>
> * All the supported DBs have native JSON support. 
> * SQLite is the only one where we don't have a Django model field already 
> to work on. 
>    * That would be first step as PoC I'd guess. 
> * Then, how can we unify? 
> * And, a migration path (from contrib.postgres) 
>
> I don't know if that's perfect but it strikes me as eminently do-able. 
>

-- 
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/5f9a5198-fd0d-470d-a6a9-81be3c8de87f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to