GSoC Proposal

[Marcio Bernardes]

Hi! My name is Márcio, I am 22 years old from Brazil. I know this is the first time I am posting here, but I hope it's the first of many. So attached with this message there is a proposal for the GSoC. This is based on the suggestions one, any thoughts? Oh yeah, I am a software developer, I worked some time in Europe with Python/Django now I think it's time to help here too. :)

[vineeth sagar]

You need to be a student at a uni to be eligible for Gsoc. Hope you know that as you say you're a Software developer.

On Mon, 18 Mar, 2019, 21:20 Marcio Bernardes, <marciobe...@gmail.com> wrote:

Hi! My name is Márcio, I am 22 years old from Brazil. I know this is the first time I am posting here, but I hope it's the first of many. So attached with this message there is a proposal for the GSoC. This is based on the suggestions one, any thoughts? Oh yeah, I am a software developer, I worked some time in Europe with Python/Django now I think it's time to help here too. :)

--
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/a1bce525-e6f7-48be-a573-5a27b194ea49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marcio Bernardes]

Yes I know, and I am a student... It's all in the file.

[Adam Johnson]

Hey Marcio,

A cross-DB JSONField is something I'd like to see too, nice proposal. I maintain the MySQL compatible field in Django-MySQL.

You wrote in the proposal that SQLite doesn't support JSON, but it does with the json1 extension: https://www.sqlite.org/json1.html

Also I don't think it's necessarily feasible to replace the contrib.postgres field with the unified one; it's likely that some features won't be able to map to the "unified" model exactly. Probably easier to leave the contrib.postgres one in there and provide migration advice to users in the documentation.

Anyway, nice to see this as a proposal!

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/57592323-4af3-460b-8274-71b70bda0730%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Adam

[Tim Graham]

Your proposal should be quite a bit more detailed. See https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 for a past example. I'm not sure if it'll be feasible to write a successful application without having some experience contributing to Django -- I think most if not all past students have had experience contributing to Django.

[Marcio Bernardes]

Hey Adam, nice to hear from you! I know this module, good work! About the SQLite pretty cool that they implemented this, I was not updated about it, this is better since they already have a certain way to do the job. About the documentation, this is probably the right approach, thanks for the feedback.

Tim, thanks for the advice, will work on that. I was afraid of this, but it makes total sense. I will start getting more engaged in the project from now on, but I'm still new in the open-source world, there's a lot of information, but thanks for the response anyway.

Cheers!

[Carlton Gibson]

Hey Marcio. 

If you can demonstrate that your abilities are sufficient in your proposal, I'm sure we can mentor you through the pull request bit. (It's just "contributor" implies knowledge of the internals, and the ORM **is** the scariest bit, so... it's a bit 😬 this close to starting.) 

You've read the contributing guide right, and had a mooch around? Jump in! https://docs.djangoproject.com/en/dev/internals/contributing/

On the Timeline applications go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, we do need that effort. 

Standout areas for me:

1. So we ship a JSONField. With SQLite in mind, most people can't use it, so we need a How-To of some kind on compiling SQLite   with the json1 extension and putting it in the right place so Python can find it. 

2. For the SQLite PoC, I'd like to see a more aggressive timeline right at the beginning. The base field with save and load shouldn't be Too Hard™ (c.f. jsonb.py)

The issue is (3) the lookups and how to handle integrating those with the existing postgres ones, the MySQL package and, the Oracle example. 

A decent sketch of an answer there and we have a proposal I think.  (Maybe it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the existing functions implementations, but...) 

Kind Regards,

Carlton

[Carlton Gibson]

Also, sorry, this was the key thread here, plus links therein https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion

[Sage M.A.]

Hi everyone,

Sorry to ask this, but can I also take a shot in this one? I've been interested in this issue since early February.

[Carlton Gibson]

Hi Sage. 

Yes. It never hurts to apply. If we get two good proposals for the same project, we can find a way to share or another project. 

We can cross that bridge as and when we come to it. 

("Scale later" 🙂)

Kind Regards,

Carlton

[Sage M.A.]

Thank you! I'll share my proposal here when I'm done with my first draft.