Hello everyone, I would like to thank everyone in here and everyone involved in Django's GSoC participation. This project has been accepted and I will try my best to deliver.
On a side note, do we have any communication channel other than this mailing list and IRC? I don't mind using them, but I guess a faster and easier-to-access channel would be very helpful in the development of this project. I lost context every time I disconnect from IRC, so it's not very desirable. Or, is django-core-mentorship <https://groups.google.com/forum/#!forum/django-core-mentorship> more appropriate? There hasn't been much going on there, so I'm not really sure. On Monday, 22 April 2019 00:05:27 UTC+7, Sage M.A. wrote: > > Hi Asif, > > I don't mind at all, but I'm still a bit busy with college stuff now, so > I'm not sure when I'll be able to do it. > > On Sunday, 21 April 2019 14:39:25 UTC+7, Asif Saif Uddin wrote: >> >> Hi Sage, >> >> Would you mind opening a draft proposal at django/dep repo? If you can >> implement the POC cross db JSON field, I as a maintainer of >> django-activity-stream would like to try this with that package. >> >> Looking forward to try your POC. >> >> Thanks, >> Asif >> >> On Tuesday, April 16, 2019 at 5:36:04 PM UTC+6, Sage M.A. wrote: >>> >>> Hi, Raphael. >>> Ah, yes, I have seen your project, but I guess I forgot to link it in my >>> proposal. >>> It *is* very interesting, and I believe it will be helpful for anyone >>> who wants to implement >>> this. Let's hope we can make this happen. Thanks for the feedback! >>> >>> Regards, >>> Sage >>> >>> On Tuesday, 16 April 2019 16:44:18 UTC+7, Raphael Michel wrote: >>>> >>>> Hi Sage, Hi everyone, >>>> >>>> I lacked the time to read this mailing list in the past months, and >>>> someone at DjangoCon Europe just pointed me to this thread, so just for >>>> reference, I want to add some prior work that I did to the list: >>>> >>>> At DjangoCon US and thereafter, I developed a third-party >>>> implementation that does a little more than the ones that are more >>>> well-known and mentioned in the proposal: >>>> >>>> https://github.com/raphaelm/django-jsonfallback >>>> >>>> django-jsonfallback supports native JSON fields on PostgreSQL, MariaDB >>>> *and* MySQL (which are quite different in that regard). On all other >>>> databases, it falls back to the behaviour of just storing strings in >>>> text fields. Therefore, it's still different from what is being >>>> proposed here, and also the implementation is quite unclean in the >>>> sense that it needs to check for database backends on the level of >>>> database fields. When implemented in core, this could be done much more >>>> nicely. >>>> >>>> Still, it might be an interesting thing to look at when doing this, if >>>> only for the test cases and the weird MySQL/MariaDB things. I'd love to >>>> see this in core and are happy to help wherever I can with my >>>> expertise. >>>> >>>> Best >>>> Raphael >>>> >>>> Am Tue, 2 Apr 2019 04:41:36 -0700 (PDT) >>>> schrieb "Sage M.A." <laym...@gmail.com>: >>>> >>>> > 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 >>>> > <https://gist.github.com/laymonage/b53a1acbbab36b77776cd526b48fd2a5>. >>>> >>>> > 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/56d64b7b-d803-4260-81f8-33959f3aa263%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
