GSOC Proposal (Bundler for Django)

[Ashik Meerankutty]

Please review and comment my draft proposal for GSOC 2019
Draft 


-- 
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/f843803b-3b14-4798-bd31-5948c0fe820a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[Asif Saif Uddin]

Regarding the declarative syntax, I might share some insights later with 
you.

On Tuesday, April 2, 2019 at 1:29:33 AM UTC+6, PARTH PATIL wrote:
>
> Here is a link to my GSoC proposal
> Its a first draft so you are open to comment and suggest changes
>
>
> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>
>
> Best Regards,
>
> PARTH PATIL
>
> SOFTWARE DEVELOPER, AUV-IITB
>
> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>
> [image: Image result for FACEBOOK ROUND ICON] 
>  [image: Image result for 
> instagram ROUND ICON]  [image: 
> Image result for linkedin ROUND ICON] 
> 
>
>

-- 
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/543b829a-1912-4d4a-8d70-5b1980b1afcb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

[Asif Saif Uddin]

Sage, regarding MariaDB, I have a little suggestion with you. If you could 
setup a latest version of mariadb locally and try to run Django test suits 
with that, you might have some ideas of remaining issues analyzing the test 
failures initially.

On Thursday, April 4, 2019 at 11:30:48 AM UTC+6, Sage M.A. wrote:
>
> Hi, Carlton.
>
> Thanks a lot for the feedback!
> Ah, yes, looks like I missed that Oracle implementation. I've updated my 
> proposal accordingly.
> To summarize:
>
>- Added info about Oracle implementation (see 1.1)
>- Replaced 1 week of research with 1 week of writing tests and docs 
>for POC SQLite JSONField (see 3.1.1 and 3.1.2)
>- Replaced the idea of implementing HStoreField with writing 
>documentation for ArrayField, migration path, and SQLite+JSON1 (see 3.3.2)
>- Took half a week from the merging process into writing the 
>aforementioned docs.
>- Wrote about the possibility of merging the first and second 
>milestones so the final milestone would not be so big to merge. (see 3.1.2 
>and 3.2.2)
>- Wrote about the possibility of finishing the project early (see 3.4)
>
> About #29548 , it seems 
> interesting to me but I'm not quite sure what's left to be done.
>
> Regards,
> Sage
>
> On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:
>>
>> Hi Sage. 
>>
>> Thanks for the proposal. It's looking OK. Couple of points: 
>>
>>
>>- There IS an Oracle implementation. See the ticket here: 
>>https://code.djangoproject.com/ticket/29821
>>- Something that looks like an ArrayField, yes. HStore... not so sure 
>>it's worth mimicking. 
>>- On the timeline: I think you've spread the coding bit too thin and 
>>not allocated enough for Documenting.
>>   - I think you if you want full-guns at the SQLite PoC in week 1 
>>   and 2 you'd have something in place quite quickly. 
>>  - The base field should be simple enough™
>>  - The SQLite only lookups shouldn't be too complicated. 
>>   - As I commented on the other thread on this topic, we'll need to 
>>   advise on getting people set up with SQLite with the JSON extension. 
>>   - There's more in this that you think I'd guess. No harm in 
>>  putting time in the schedule for it. 
>>   - Allow for the possibility you complete early and have time to 
>>   work on other things...
>>   - This stuff is difficult to get right. It's more balance that 
>>   exact times: 
>>  - The actual timeline won't match the plan ever. 
>>  - you don't need to worry about two days off for holiday 🙂
>>   
>> Your contributions so far have been super. Thank you. 
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>> On Tuesday, 2 April 2019 13:41:37 UTC+2, Sage M.A. wrote:
>>>
>>> Hello, everyone! My name is Sage. I'm a 19-year-old computer science 
>>> student from Indonesia. I'm planning to join the Google Summer of Code 
>>> (GSoC) this year, and I want to contribute to Django. I have written a 
>>> draft for my proposal in this gist 
>>> . I 
>>> have submitted two small patches for Django, and I hope to contribute more 
>>> in the future. Feedbacks are much appreciated, thanks!
>>>
>>

-- 
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/7b4ec564-82ef-4c38-a5b8-8b2ba1e1a938%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

Sure that would be nice, as I even mentioned in my abstract I definitely 
need help for that one.

On Saturday, April 6, 2019 at 8:59:01 PM UTC+5:30, Asif Saif Uddin wrote:
>
> Regarding the declarative syntax, I might share some insights later with 
> you.
>
> On Tuesday, April 2, 2019 at 1:29:33 AM UTC+6, PARTH PATIL wrote:
>>
>> Here is a link to my GSoC proposal
>> Its a first draft so you are open to comment and suggest changes
>>
>>
>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>
>>
>> Best Regards,
>>
>> PARTH PATIL
>>
>> SOFTWARE DEVELOPER, AUV-IITB
>>
>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>
>> [image: Image result for FACEBOOK ROUND ICON] 
>>  [image: Image result for 
>> instagram ROUND ICON]  [image: 
>> Image result for linkedin ROUND ICON] 
>> 
>>
>>

-- 
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/5951644c-fe20-4c12-beff-462451681455%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Should we backport adding support for psycopg2 2.8 to the 1.11.x and 2.1.x?

[אורי]

Don't forget 2.0.

I updated my project to use psycopg2==2.7.7 until we upgrade to Django 2.2.

אורי
u...@speedy.net


On Fri, Apr 5, 2019 at 12:35 PM Mariusz Felisiak 
wrote:

> Agreed. I will document that 1.11 and 2.1 require psycopg2 *2.5.4* through
> *2.7.7* versions.
>
> We can re-open this discussion in the future if e.g. psycopg2 2.8.x will
> contain some important security patch.
>
> --
> 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/bae59229-dd3b-4690-9c06-52e322ea1f9b%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/CABD5YeHW3Ac4Mn3aGfbjFmuTvD%2BXZk0-RyhMmPSmbqUkg_%2B_kg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[Asif Saif Uddin]

I will try to come up with an initial step for that hopefully by tomorrow. 
In the meantime, I hope you will keep trying to improve your proposal by 
analyzing open form/formset related issues, some of whom you could try to 
fix to get more insight.

On Saturday, April 6, 2019 at 10:30:02 PM UTC+6, PARTH PATIL wrote:
>
> Sure that would be nice, as I even mentioned in my abstract I definitely 
> need help for that one.
>
> On Saturday, April 6, 2019 at 8:59:01 PM UTC+5:30, Asif Saif Uddin wrote:
>>
>> Regarding the declarative syntax, I might share some insights later with 
>> you.
>>
>> On Tuesday, April 2, 2019 at 1:29:33 AM UTC+6, PARTH PATIL wrote:
>>>
>>> Here is a link to my GSoC proposal
>>> Its a first draft so you are open to comment and suggest changes
>>>
>>>
>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>
>>>
>>> Best Regards,
>>>
>>> PARTH PATIL
>>>
>>> SOFTWARE DEVELOPER, AUV-IITB
>>>
>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>
>>> [image: Image result for FACEBOOK ROUND ICON] 
>>>  [image: Image result for 
>>> instagram ROUND ICON]  [image: 
>>> Image result for linkedin ROUND ICON] 
>>> 
>>>
>>>

-- 
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/eba76e1d-f601-4f36-bfc5-ee808ea5cdf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSOC Proposal (Bundler for Django)

[Kiran Capoor]

Hi,

This has already been implemented via multiple Third party Projects -

1. Django Webpack Loader by owais-
https://github.com/owais/django-webpack-loader

2. Cookie-cutter Django Webpack by myself(not production ready though) -
https://github.com/kiran-capoor94/cookiecutter-django-webpack

Many more are there.

Also, forcing users to use a bundler like webpack is not really preferred
 by many. Some might want to use gulp, or maybe nothing at all.



Regards,

Kiran Capoor


On Sat, 6 Apr 2019 at 18:33, Ashik Meerankutty  wrote:

> Please review and comment my draft proposal for GSOC 2019
> Draft
> 
>
> --
> 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/f843803b-3b14-4798-bd31-5948c0fe820a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from iPhone

-- 
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/CAANvM2muqw%3D54GWcpUvGTS%2B%2Bgd9nZ1WA0wvaDQRz%3Do3SmXePhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSOC Proposal (Bundler for Django)

[Ashik Meerankutty]

Thank you for your feed back.

On Sun, 7 Apr 2019 at 12:03 AM, Kiran Capoor 
wrote:

> Hi,
>
> This has already been implemented via multiple Third party Projects -
>
> 1. Django Webpack Loader by owais-
> https://github.com/owais/django-webpack-loader
>
> 2. Cookie-cutter Django Webpack by myself(not production ready though) -
> https://github.com/kiran-capoor94/cookiecutter-django-webpack
>
> Many more are there.
>
> Also, forcing users to use a bundler like webpack is not really preferred
>  by many. Some might want to use gulp, or maybe nothing at all.
>
>
>
> Regards,
>
> Kiran Capoor
>
>
> On Sat, 6 Apr 2019 at 18:33, Ashik Meerankutty 
> wrote:
>
>> Please review and comment my draft proposal for GSOC 2019
>> Draft
>> 
>>
>> --
>> 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/f843803b-3b14-4798-bd31-5948c0fe820a%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Sent from iPhone
>
> --
> 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/CAANvM2muqw%3D54GWcpUvGTS%2B%2Bgd9nZ1WA0wvaDQRz%3Do3SmXePhw%40mail.gmail.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/CALaZoZdWOhYATP%2BKTwTrN-Pmr3r6OYf%2BoCu0XN83pMAq7HgY_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSOC Proposal (Bundler for Django)

[Ashik Meerankutty]

Can we write our own bundler only for django. Is that good

On Sun, 7 Apr 2019 at 8:04 AM, Ashik Meerankutty 
wrote:

> Thank you for your feed back.
>
> On Sun, 7 Apr 2019 at 12:03 AM, Kiran Capoor 
> wrote:
>
>> Hi,
>>
>> This has already been implemented via multiple Third party Projects -
>>
>> 1. Django Webpack Loader by owais-
>> https://github.com/owais/django-webpack-loader
>>
>> 2. Cookie-cutter Django Webpack by myself(not production ready though) -
>> https://github.com/kiran-capoor94/cookiecutter-django-webpack
>>
>> Many more are there.
>>
>> Also, forcing users to use a bundler like webpack is not really preferred
>>  by many. Some might want to use gulp, or maybe nothing at all.
>>
>>
>>
>> Regards,
>>
>> Kiran Capoor
>>
>>
>> On Sat, 6 Apr 2019 at 18:33, Ashik Meerankutty 
>> wrote:
>>
>>> Please review and comment my draft proposal for GSOC 2019
>>> Draft
>>> 
>>>
>>> --
>>> 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/f843803b-3b14-4798-bd31-5948c0fe820a%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Sent from iPhone
>>
>> --
>> 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/CAANvM2muqw%3D54GWcpUvGTS%2B%2Bgd9nZ1WA0wvaDQRz%3Do3SmXePhw%40mail.gmail.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/CALaZoZc6U0TOwYmKL5nKeFVwhQ%2BuMiHSPHX050U%2BdEXWqhwUfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Specifying model relationship as string vs concrete model class

[Mohit Solanki]

Since Django allows specifying relationship between models by both as a
string or by a model class
"models.Foreignkey('User') vs "models.Foreignkey(User)". Which one is
preferred and recommend and what are the downsides of choosing one over the
other? In documentation all the examples are of the second form but i have
seen ppl specifying relationships in string. Can someone please elaborate
more on this?

Regards,
Mohit Solanki

-- 
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/CAKB6Ln-4rU2c%3DZL%3DTCbYfFZWG8fSDq4KP9DYhUc4TDFLNFdQtw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSOC Proposal (Bundler for Django)

[Scot Hacker]

On Saturday, April 6, 2019 at 6:03:29 AM UTC-7, Ashik Meerankutty wrote:
>
> Please review and comment my draft proposal for GSOC 2019
> Draft 
> 
>

Ashik's proposal is more along the lines of a general asset pipeline, a la 
django-compressor or django-pipeline, rather than a webpack builder. 
Regardless, I count 30+ asset pipeline systems at 
https://djangopackages.org/grids/g/asset-managers/ . 

./s

-- 
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/cf64fba5-120b-4aae-8b9e-4409783bfe99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

[Sage M.A.]

Hi Asif,
That's a good idea! I've installed the latest stable release of MariaDB 
(10.3.14) on my machine and ran Django test suits with it.
The results 
 (I've 
truncated them to only contain the failures and errors) show 19 failures 
and 15 errors, all of which seem to be
related to datetime functions. I suppose that'll be enough for me to work 
on if my GSoC project finishes early. I'll also need to
write docs about the new support for MariaDB.

On a side note, setting up and destroying the database for the test took 
hours on my machine. Is that normal? I had to use
verbosity=2 to find out that it was not freezing, just really slow.

On Saturday, 6 April 2019 22:32:53 UTC+7, Asif Saif Uddin wrote:
>
> Sage, regarding MariaDB, I have a little suggestion with you. If you could 
> setup a latest version of mariadb locally and try to run Django test suits 
> with that, you might have some ideas of remaining issues analyzing the test 
> failures initially.
>
> On Thursday, April 4, 2019 at 11:30:48 AM UTC+6, Sage M.A. wrote:
>>
>> Hi, Carlton.
>>
>> Thanks a lot for the feedback!
>> Ah, yes, looks like I missed that Oracle implementation. I've updated my 
>> proposal accordingly.
>> To summarize:
>>
>>- Added info about Oracle implementation (see 1.1)
>>- Replaced 1 week of research with 1 week of writing tests and docs 
>>for POC SQLite JSONField (see 3.1.1 and 3.1.2)
>>- Replaced the idea of implementing HStoreField with writing 
>>documentation for ArrayField, migration path, and SQLite+JSON1 (see 3.3.2)
>>- Took half a week from the merging process into writing the 
>>aforementioned docs.
>>- Wrote about the possibility of merging the first and second 
>>milestones so the final milestone would not be so big to merge. (see 
>> 3.1.2 
>>and 3.2.2)
>>- Wrote about the possibility of finishing the project early (see 3.4)
>>
>> About #29548 , it seems 
>> interesting to me but I'm not quite sure what's left to be done.
>>
>> Regards,
>> Sage
>>
>> On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:
>>>
>>> Hi Sage. 
>>>
>>> Thanks for the proposal. It's looking OK. Couple of points: 
>>>
>>>
>>>- There IS an Oracle implementation. See the ticket here: 
>>>https://code.djangoproject.com/ticket/29821
>>>- Something that looks like an ArrayField, yes. HStore... not so 
>>>sure it's worth mimicking. 
>>>- On the timeline: I think you've spread the coding bit too thin and 
>>>not allocated enough for Documenting.
>>>   - I think you if you want full-guns at the SQLite PoC in week 1 
>>>   and 2 you'd have something in place quite quickly. 
>>>  - The base field should be simple enough™
>>>  - The SQLite only lookups shouldn't be too complicated. 
>>>   - As I commented on the other thread on this topic, we'll need to 
>>>   advise on getting people set up with SQLite with the JSON extension. 
>>>   - There's more in this that you think I'd guess. No harm in 
>>>  putting time in the schedule for it. 
>>>   - Allow for the possibility you complete early and have time to 
>>>   work on other things...
>>>   - This stuff is difficult to get right. It's more balance that 
>>>   exact times: 
>>>  - The actual timeline won't match the plan ever. 
>>>  - you don't need to worry about two days off for holiday 🙂
>>>   
>>> Your contributions so far have been super. Thank you. 
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>> On Tuesday, 2 April 2019 13:41:37 UTC+2, Sage M.A. wrote:

 Hello, everyone! My name is Sage. I'm a 19-year-old computer science 
 student from Indonesia. I'm planning to join the Google Summer of Code 
 (GSoC) this year, and I want to contribute to Django. I have written a 
 draft for my proposal in this gist 
 . 
 I have submitted two small patches for Django, and I hope to contribute 
 more in the future. Feedbacks are much appreciated, thanks!

>>>

-- 
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/f8467086-201f-4cab-b844-b06ca303660d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

[Sage M.A.]

Oh, I forgot, one of them is not related to datetime functions: 
test_unsupported_backend.

On Sunday, 7 April 2019 13:26:10 UTC+7, Sage M.A. wrote:
>
> Hi Asif,
> That's a good idea! I've installed the latest stable release of MariaDB 
> (10.3.14) on my machine and ran Django test suits with it.
> The results 
>  (I've 
> truncated them to only contain the failures and errors) show 19 failures 
> and 15 errors, all of which seem to be
> related to datetime functions. I suppose that'll be enough for me to work 
> on if my GSoC project finishes early. I'll also need to
> write docs about the new support for MariaDB.
>
> On a side note, setting up and destroying the database for the test took 
> hours on my machine. Is that normal? I had to use
> verbosity=2 to find out that it was not freezing, just really slow.
>
> On Saturday, 6 April 2019 22:32:53 UTC+7, Asif Saif Uddin wrote:
>>
>> Sage, regarding MariaDB, I have a little suggestion with you. If you 
>> could setup a latest version of mariadb locally and try to run Django test 
>> suits with that, you might have some ideas of remaining issues analyzing 
>> the test failures initially.
>>
>> On Thursday, April 4, 2019 at 11:30:48 AM UTC+6, Sage M.A. wrote:
>>>
>>> Hi, Carlton.
>>>
>>> Thanks a lot for the feedback!
>>> Ah, yes, looks like I missed that Oracle implementation. I've updated my 
>>> proposal accordingly.
>>> To summarize:
>>>
>>>- Added info about Oracle implementation (see 1.1)
>>>- Replaced 1 week of research with 1 week of writing tests and docs 
>>>for POC SQLite JSONField (see 3.1.1 and 3.1.2)
>>>- Replaced the idea of implementing HStoreField with writing 
>>>documentation for ArrayField, migration path, and SQLite+JSON1 (see 
>>> 3.3.2)
>>>- Took half a week from the merging process into writing the 
>>>aforementioned docs.
>>>- Wrote about the possibility of merging the first and second 
>>>milestones so the final milestone would not be so big to merge. (see 
>>> 3.1.2 
>>>and 3.2.2)
>>>- Wrote about the possibility of finishing the project early (see 
>>>3.4)
>>>
>>> About #29548 , it seems 
>>> interesting to me but I'm not quite sure what's left to be done.
>>>
>>> Regards,
>>> Sage
>>>
>>> On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:

 Hi Sage. 

 Thanks for the proposal. It's looking OK. Couple of points: 


- There IS an Oracle implementation. See the ticket here: 
https://code.djangoproject.com/ticket/29821
- Something that looks like an ArrayField, yes. HStore... not so 
sure it's worth mimicking. 
- On the timeline: I think you've spread the coding bit too thin 
and not allocated enough for Documenting.
   - I think you if you want full-guns at the SQLite PoC in week 1 
   and 2 you'd have something in place quite quickly. 
  - The base field should be simple enough™
  - The SQLite only lookups shouldn't be too complicated. 
   - As I commented on the other thread on this topic, we'll need 
   to advise on getting people set up with SQLite with the JSON 
 extension. 
   - There's more in this that you think I'd guess. No harm in 
  putting time in the schedule for it. 
   - Allow for the possibility you complete early and have time to 
   work on other things...
   - This stuff is difficult to get right. It's more balance that 
   exact times: 
  - The actual timeline won't match the plan ever. 
  - you don't need to worry about two days off for holiday 🙂
   
 Your contributions so far have been super. Thank you. 

 Kind Regards,

 Carlton


 On Tuesday, 2 April 2019 13:41:37 UTC+2, Sage M.A. wrote:
>
> Hello, everyone! My name is Sage. I'm a 19-year-old computer science 
> student from Indonesia. I'm planning to join the Google Summer of Code 
> (GSoC) this year, and I want to contribute to Django. I have written a 
> draft for my proposal in this gist 
> . 
> I have submitted two small patches for Django, and I hope to contribute 
> more in the future. Feedbacks are much appreciated, thanks!
>


-- 
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/