Re: Google Summer of Code 2018

[Sidhant Bendre]

Hey Cartlton, you're a life saver! Thank you so much and have nice day!

On Thursday, January 24, 2019 at 3:36:33 PM UTC+1, Carlton Gibson wrote:
>
> Hi Sidhant. 
>
> See Tim's thread from the other day: 
> https://groups.google.com/d/topic/django-developers/PcXfiDNwPxg/discussion
>
> Looking at the Wiki page from 2018 he linked, two points jump out: 
>
> * Don't feel limited to the ideas [on the page] -- if you've got a cool 
> project you want to work on, we'll probably be able to find you a mentor. 
> * Post to 
> https://groups.google.com/forum/#!forum/django-core-mentorship if you 
> need to discuss, I'm sure we can help. 
> * Any proposals for GSOC should be submitted [to this list] — plus get 
> them in soon I guess. 
>
> On Thursday, 24 January 2019 15:21:34 UTC+1, Sidhant Bendre wrote:
>>
>> Dear Django developers, I want to ask why there were no django projects 
>> for GSoC 2018? Furthermore, are there any potential mentors for this year's 
>> Google Summer of Code that I can have a conversation with as I want to get 
>> more clarity on the application process for Django and talk to them about 
>> the guidelines specific to Django regarding Google Summer of Code
>>
>

-- 
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/65a74c59-af57-4076-9ee2-01d585229baa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Carlton Gibson]

Hi Sidhant. 

See Tim's thread from the other 
day: https://groups.google.com/d/topic/django-developers/PcXfiDNwPxg/discussion

Looking at the Wiki page from 2018 he linked, two points jump out: 

* Don't feel limited to the ideas [on the page] -- if you've got a cool 
project you want to work on, we'll probably be able to find you a mentor. 
* Post to 
https://groups.google.com/forum/#!forum/django-core-mentorship if you need 
to discuss, I'm sure we can help. 
* Any proposals for GSOC should be submitted [to this list] — plus get them 
in soon I guess. 

On Thursday, 24 January 2019 15:21:34 UTC+1, Sidhant Bendre wrote:
>
> Dear Django developers, I want to ask why there were no django projects 
> for GSoC 2018? Furthermore, are there any potential mentors for this year's 
> Google Summer of Code that I can have a conversation with as I want to get 
> more clarity on the application process for Django and talk to them about 
> the guidelines specific to Django regarding Google Summer of Code
>

-- 
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/bc84953a-a0c0-4db1-8435-34638b76e9c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Google Summer of Code 2018

[Sidhant Bendre]

Dear Django developers, I want to ask why there were no django projects for 
GSoC 2018? Furthermore, are there any potential mentors for this year's 
Google Summer of Code that I can have a conversation with as I want to get 
more clarity on the application process for Django and talk to them about 
the guidelines specific to Django regarding Google Summer of Code

-- 
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/bb6a50df-ffdd-41b6-a95a-16f9ac8e341e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Adam Johnson]

I'm afraid this doesn't fit into one of the three Django GSoC categories as
listed at https://code.djangoproject.com/wiki/SummerOfCode2018 :


>- Work on Django itself - such as the ORM, forms, etc. This is what
>we've traditionally accepted GSoC entries in.
>
>
>- Work on tools to support Django - the dashboard (​
>https://dashboard.djangoproject.com/) is a good example of an existing
>tool that would have fit into this category.
>
>
>- Work on libraries that supplement or add new features to Django to
>ease development - South and Django Debug Toolbar are good examples of
>existing projects that would have fit here.
>
>
On 27 March 2018 at 15:15, Emanuel Covaci  wrote:

> Hey everyone,
>
> Here is my idea for GSoC 2018 https://docs.google.com/document/d/1_
> 9fXzb4gceQX0CZplzlf8lRKWyB9sjX1OKNBqs9IpZg/edit?usp=sharing
>
>
> --
> 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/e3175165-d384-43f2-8347-
> 1cefe717db98%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Adam

-- 
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/CAMyDDM1wGzO55Zzfyde9MdqoiE%3D8hZWDqvNTt2tojVFn2Dp%2B1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

The deadline for proposal is past, but I agree the plan isn't detailed 
enough as of now. I'll try to add concrete details to the proposal within 
this week to try convincing the community.

Best
Priyansh

On Monday, March 26, 2018 at 10:51:41 PM UTC+5:30, Tim Graham wrote:
>
> Hi, I'm not sure that the plan is fleshed out in enough detail (compare it 
> to https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 and 
> https://github.com/django/deps). That level of detail is needed to give 
> us confidence that you might be able to deliver what you promise.
>
> On Monday, March 26, 2018 at 11:28:30 AM UTC-4, askpr...@gmail.com wrote:
>>
>> Hello !
>>
>> I have submitted a draft proposal on the GSoC Portal. I look forward to 
>> the community-feedback on this.
>>
>> Regards
>> Priyansh
>>
>> On Saturday, March 24, 2018 at 11:10:43 PM UTC+5:30, askpr...@gmail.com 
>> wrote:
>>>
>>> Hello !
>>>
>>> Here's the updated version of my proposal: 
>>> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. 
>>> A request to the community to spare some time and review this before I put 
>>> it up on the GSoC portal.
>>>
>>> I am working on solving some feature-requests, and I've got working 
>>> solutions put as PRs. I have tried to give details of the problem and 
>>> examples of how the project will be useful in the proposal, but I am not 
>>> quite sure on how to demonstrate the understanding of Django. Please do 
>>> give me pointers on this.
>>>
>>> Best
>>> Priyansh
>>>
>>> On Wednesday, February 21, 2018 at 12:12:44 AM UTC+5:30, Tim Graham 
>>> wrote:

 Hi Priyansh,

 Your proposal isn't really detailed enough for me to understand what 
 the outcome of your project would be (I haven't watched Russell's talk 
 that 
 you linked). What are the "big wins"? There are projects like 
 https://github.com/potatolondon/djangae, which allows using Django 
 with Google App Engine. Would your project make something like that much 
 simpler? You'll have to demonstrate a fairly sophisticated level of 
 understanding of Django to convince us that you understand the problems 
 well enough to have a reasonable chance of success.

 Regarding your proposed schedule, I'm a bit concerned that you'll have 
 exams for five weeks of the coding period. Students are expected to 
 average 
 30+ hours/week on their projects. Is that feasible while you're studying 
 for exams?

 On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com 
 wrote:
>
> Hello !
>
> I have drafted a project-proposal for the idea that Russell laid out 
> in his talk at DjangoCon '15. Here's the link to the draft:
>
> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460
>
> Looking forward to your suggestions on how best to improve this for a 
> concrete GSoC '18 project-proposal.
>
> Regards
> Priyansh
>
> On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
> Keith-Magee wrote:
>>
>>
>> Another approach would be to do what I laid out in this talk at 
>> DjangoCon US 2015, following the last Summer of Code student who tackled 
>> (tangentially) this problem. 
>>
>> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>>
>> That is - finish the modifications needed to Django’s core such that 
>> an arbitrary model can register in a way compatible with the Admin and 
>> Forms library. This was one of the reasons given for standardising the 
>> meta-model framework, but didn’t make it into Daniel’s GSoC project, 
>> although he *did* get a proof of concept working that exposed your Gmail 
>> inbox in Django’s admin. 
>>
>> This would allow *any* data backend to expose an interface that is 
>> fundamentally compatible with Django - which, really, just means “I want 
>> to 
>> browse my data in the admin” and “I want to display a form for my 
>> model”. 
>>
>> It won’t allow an arbitrary ORM query to run against an arbitrary 
>> “NoSQL” backend - but that’s idea was never going to work anyway. But I 
>> don’t think anyone is serious about wanting that, either. All they want 
>> is 
>> the ability to integrate a non-SQL data source into their basic Django 
>> visualisations. 
>>
>> Yours, 
>> Russ Magee %-) 
>>
>> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
>> wrote: 
>> > 
>> > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
>> >> Hello ! 
>> >> What is the policy regarding NoSQL datastores being used as 
>> backends ? I think adding support for something like MongoDB might be 
>> good 
>> idea. 
>> > 
>> > Could you elaborate on why you think it would be a good idea? 
>> > 
>> > I believe every other time the discussion has come up the following 
>> 

Google Summer of Code 2018

[Emanuel Covaci]

Hey everyone,

Here is my idea for GSoC 2018 
https://docs.google.com/document/d/1_9fXzb4gceQX0CZplzlf8lRKWyB9sjX1OKNBqs9IpZg/edit?usp=sharing


-- 
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/e3175165-d384-43f2-8347-1cefe717db98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Tim Graham]

Hi, I'm not sure that the plan is fleshed out in enough detail (compare it 
to https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 and 
https://github.com/django/deps). That level of detail is needed to give us 
confidence that you might be able to deliver what you promise.

On Monday, March 26, 2018 at 11:28:30 AM UTC-4, askpr...@gmail.com wrote:
>
> Hello !
>
> I have submitted a draft proposal on the GSoC Portal. I look forward to 
> the community-feedback on this.
>
> Regards
> Priyansh
>
> On Saturday, March 24, 2018 at 11:10:43 PM UTC+5:30, askpr...@gmail.com 
> wrote:
>>
>> Hello !
>>
>> Here's the updated version of my proposal: 
>> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. 
>> A request to the community to spare some time and review this before I put 
>> it up on the GSoC portal.
>>
>> I am working on solving some feature-requests, and I've got working 
>> solutions put as PRs. I have tried to give details of the problem and 
>> examples of how the project will be useful in the proposal, but I am not 
>> quite sure on how to demonstrate the understanding of Django. Please do 
>> give me pointers on this.
>>
>> Best
>> Priyansh
>>
>> On Wednesday, February 21, 2018 at 12:12:44 AM UTC+5:30, Tim Graham wrote:
>>>
>>> Hi Priyansh,
>>>
>>> Your proposal isn't really detailed enough for me to understand what the 
>>> outcome of your project would be (I haven't watched Russell's talk that you 
>>> linked). What are the "big wins"? There are projects like 
>>> https://github.com/potatolondon/djangae, which allows using Django with 
>>> Google App Engine. Would your project make something like that much 
>>> simpler? You'll have to demonstrate a fairly sophisticated level of 
>>> understanding of Django to convince us that you understand the problems 
>>> well enough to have a reasonable chance of success.
>>>
>>> Regarding your proposed schedule, I'm a bit concerned that you'll have 
>>> exams for five weeks of the coding period. Students are expected to average 
>>> 30+ hours/week on their projects. Is that feasible while you're studying 
>>> for exams?
>>>
>>> On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com 
>>> wrote:

 Hello !

 I have drafted a project-proposal for the idea that Russell laid out in 
 his talk at DjangoCon '15. Here's the link to the draft:

 https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460

 Looking forward to your suggestions on how best to improve this for a 
 concrete GSoC '18 project-proposal.

 Regards
 Priyansh

 On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
 Keith-Magee wrote:
>
>
> Another approach would be to do what I laid out in this talk at 
> DjangoCon US 2015, following the last Summer of Code student who tackled 
> (tangentially) this problem. 
>
> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>
> That is - finish the modifications needed to Django’s core such that 
> an arbitrary model can register in a way compatible with the Admin and 
> Forms library. This was one of the reasons given for standardising the 
> meta-model framework, but didn’t make it into Daniel’s GSoC project, 
> although he *did* get a proof of concept working that exposed your Gmail 
> inbox in Django’s admin. 
>
> This would allow *any* data backend to expose an interface that is 
> fundamentally compatible with Django - which, really, just means “I want 
> to 
> browse my data in the admin” and “I want to display a form for my model”. 
>
> It won’t allow an arbitrary ORM query to run against an arbitrary 
> “NoSQL” backend - but that’s idea was never going to work anyway. But I 
> don’t think anyone is serious about wanting that, either. All they want 
> is 
> the ability to integrate a non-SQL data source into their basic Django 
> visualisations. 
>
> Yours, 
> Russ Magee %-) 
>
> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
> wrote: 
> > 
> > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
> >> Hello ! 
> >> What is the policy regarding NoSQL datastores being used as 
> backends ? I think adding support for something like MongoDB might be 
> good 
> idea. 
> > 
> > Could you elaborate on why you think it would be a good idea? 
> > 
> > I believe every other time the discussion has come up the following 
> points have been made. 
> > 
> > 1. "NoSQL" is not a DB category, it is an anti-category 
> > 2. Because of there there is no common data model, or query 
> languages. 
> > 3. If you limit yourself to just document stores, there is still no 
> common query language [but this can be hidden by code] 
> > 4. Document stores are a really really bad fit for the ORM, as it's 
> designed for the relational 

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I have submitted a draft proposal on the GSoC Portal. I look forward to the 
community-feedback on this.

Regards
Priyansh

On Saturday, March 24, 2018 at 11:10:43 PM UTC+5:30, askpr...@gmail.com 
wrote:
>
> Hello !
>
> Here's the updated version of my proposal: 
> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. 
> A request to the community to spare some time and review this before I put 
> it up on the GSoC portal.
>
> I am working on solving some feature-requests, and I've got working 
> solutions put as PRs. I have tried to give details of the problem and 
> examples of how the project will be useful in the proposal, but I am not 
> quite sure on how to demonstrate the understanding of Django. Please do 
> give me pointers on this.
>
> Best
> Priyansh
>
> On Wednesday, February 21, 2018 at 12:12:44 AM UTC+5:30, Tim Graham wrote:
>>
>> Hi Priyansh,
>>
>> Your proposal isn't really detailed enough for me to understand what the 
>> outcome of your project would be (I haven't watched Russell's talk that you 
>> linked). What are the "big wins"? There are projects like 
>> https://github.com/potatolondon/djangae, which allows using Django with 
>> Google App Engine. Would your project make something like that much 
>> simpler? You'll have to demonstrate a fairly sophisticated level of 
>> understanding of Django to convince us that you understand the problems 
>> well enough to have a reasonable chance of success.
>>
>> Regarding your proposed schedule, I'm a bit concerned that you'll have 
>> exams for five weeks of the coding period. Students are expected to average 
>> 30+ hours/week on their projects. Is that feasible while you're studying 
>> for exams?
>>
>> On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com 
>> wrote:
>>>
>>> Hello !
>>>
>>> I have drafted a project-proposal for the idea that Russell laid out in 
>>> his talk at DjangoCon '15. Here's the link to the draft:
>>>
>>> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460
>>>
>>> Looking forward to your suggestions on how best to improve this for a 
>>> concrete GSoC '18 project-proposal.
>>>
>>> Regards
>>> Priyansh
>>>
>>> On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
>>> Keith-Magee wrote:


 Another approach would be to do what I laid out in this talk at 
 DjangoCon US 2015, following the last Summer of Code student who tackled 
 (tangentially) this problem. 

 https://www.youtube.com/watch?v=VgM0qmpHDiE 

 That is - finish the modifications needed to Django’s core such that an 
 arbitrary model can register in a way compatible with the Admin and Forms 
 library. This was one of the reasons given for standardising the 
 meta-model 
 framework, but didn’t make it into Daniel’s GSoC project, although he 
 *did* 
 get a proof of concept working that exposed your Gmail inbox in Django’s 
 admin. 

 This would allow *any* data backend to expose an interface that is 
 fundamentally compatible with Django - which, really, just means “I want 
 to 
 browse my data in the admin” and “I want to display a form for my model”. 

 It won’t allow an arbitrary ORM query to run against an arbitrary 
 “NoSQL” backend - but that’s idea was never going to work anyway. But I 
 don’t think anyone is serious about wanting that, either. All they want is 
 the ability to integrate a non-SQL data source into their basic Django 
 visualisations. 

 Yours, 
 Russ Magee %-) 

 > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
 wrote: 
 > 
 > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
 >> Hello ! 
 >> What is the policy regarding NoSQL datastores being used as backends 
 ? I think adding support for something like MongoDB might be good idea. 
 > 
 > Could you elaborate on why you think it would be a good idea? 
 > 
 > I believe every other time the discussion has come up the following 
 points have been made. 
 > 
 > 1. "NoSQL" is not a DB category, it is an anti-category 
 > 2. Because of there there is no common data model, or query 
 languages. 
 > 3. If you limit yourself to just document stores, there is still no 
 common query language [but this can be hidden by code] 
 > 4. Document stores are a really really bad fit for the ORM, as it's 
 designed for the relational model, not document model. 
 > 5. A better approach would be to develop an ODM, which is 
 sufficiently compatible with the ORM you can provide similar tools like 
 ModelForms and ModelAdmin, as well as GCBV. 
 > 
 > If I missed anything, I'm sure someone else will remind me. 
 > 
 > [Also... why is it always MongoDB, instead of something with a solid 
 reputation of reliability and performance?] 
 > 
 > -- 
 > Curtis 
 > 
 > 

Re: Google Summer of Code 2018

[Mberebe Guidona]

On Saturday, 24 March 2018 13:42:29 UTC+1, Mberebe Guidona wrote:
>
> Hello everyone,
>
> *Project idea*
>
> I'm new in the google summer of code and as a Python-Django developer, I 
> was interested in participating with your organisation for this year.
> The project idea I have is the implementation of a CLI for Django projects 
> (an example is the Angular CLI) for:
>
>- generating *views;*
>- generating *urls *as we implement the corresponding *view;*
>- generating models for the database;
>- etc.
>
> *Why this project?*
>
> I had this idea when developing some apps with Django and I had 
> difficulties moving over the different files when ever I did some changes 
> and this was really hard for me.
> This is why I had this Idea in order to ease development.
>
> *About me*
>
> My name is Guy Mberebe Guidona, and I'm from Cameroon and a student of the 
> National Advanced School of Engineering of Maroua.
> As I said, this is my really first participation to the Google Summer of 
> Code, and I really want to take part to this adventure. 
>
> 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/da3a8dc0-b377-4e00-8c85-495177f7c429%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Mberebe Guidona]

Why do you consider is as not a good idea ? I'm really, I say really 
interested in working with this organisation during this GSoC.
How can we have a prior experience contributing from django if we don't 
start someday ?

On Sunday, 25 March 2018 02:57:57 UTC+1, Tim Graham wrote:
>
> Hi, I don't think this idea is suitable and as the proposal deadline is 
> two days away, I don't think you'll be able to develop a successful 
> proposal so late in the process. As 
> https://code.djangoproject.com/wiki/SummerOfCode2018 says, you should 
> have some prior experience contributing to Django.
>
> On Saturday, March 24, 2018 at 8:42:29 AM UTC-4, Mberebe Guidona wrote:
>>
>> Hello everyone,
>>
>> *Project idea*
>>
>> I'm new in the google summer of code and as a Python-Django developer, I 
>> was interested in participating with your organisation for this year.
>> The project idea I have is the implementation of a CLI for Django 
>> projects (an example is the Angular CLI) for:
>>
>>- generating *views;*
>>- generating *urls *as we implement the corresponding *view;*
>>- generating models for the database;
>>- etc.
>>
>> *Why this project?*
>>
>> I had this idea when developing some apps with Django and I had 
>> difficulties moving over the different files when ever I did some changes 
>> and this was really hard for me.
>> This is why I had this Idea in order to ease development.
>>
>> *About me*
>>
>> My name is Guy Mberebe Guidona, and I'm from Cameroon and a student of 
>> the National Advanced School of Engineering of Maroua.
>> As I said, this is my really first participation to the Google Summer of 
>> Code, and I really want to take part to this adventure. 
>>
>> 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/852cae63-c9dc-4c59-85ab-decec05b881f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Tim Graham]

Hi, I don't think this idea is suitable and as the proposal deadline is two 
days away, I don't think you'll be able to develop a successful proposal so 
late in the process. As 
https://code.djangoproject.com/wiki/SummerOfCode2018 says, you should have 
some prior experience contributing to Django.

On Saturday, March 24, 2018 at 8:42:29 AM UTC-4, Mberebe Guidona wrote:
>
> Hello everyone,
>
> *Project idea*
>
> I'm new in the google summer of code and as a Python-Django developer, I 
> was interested in participating with your organisation for this year.
> The project idea I have is the implementation of a CLI for Django projects 
> (an example is the Angular CLI) for:
>
>- generating *views;*
>- generating *urls *as we implement the corresponding *view;*
>- generating models for the database;
>- etc.
>
> *Why this project?*
>
> I had this idea when developing some apps with Django and I had 
> difficulties moving over the different files when ever I did some changes 
> and this was really hard for me.
> This is why I had this Idea in order to ease development.
>
> *About me*
>
> My name is Guy Mberebe Guidona, and I'm from Cameroon and a student of the 
> National Advanced School of Engineering of Maroua.
> As I said, this is my really first participation to the Google Summer of 
> Code, and I really want to take part to this adventure. 
>
> 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/d8605901-b908-43cf-84df-773a6c300a84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

Here's the updated version of my proposal: 
https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. A 
request to the community to spare some time and review this before I put it 
up on the GSoC portal.

I am working on solving some feature-requests, and I've got working 
solutions put as PRs. I have tried to give details of the problem and 
examples of how the project will be useful in the proposal, but I am not 
quite sure on how to demonstrate the understanding of Django. Please do 
give me pointers on this.

Best
Priyansh

On Wednesday, February 21, 2018 at 12:12:44 AM UTC+5:30, Tim Graham wrote:
>
> Hi Priyansh,
>
> Your proposal isn't really detailed enough for me to understand what the 
> outcome of your project would be (I haven't watched Russell's talk that you 
> linked). What are the "big wins"? There are projects like 
> https://github.com/potatolondon/djangae, which allows using Django with 
> Google App Engine. Would your project make something like that much 
> simpler? You'll have to demonstrate a fairly sophisticated level of 
> understanding of Django to convince us that you understand the problems 
> well enough to have a reasonable chance of success.
>
> Regarding your proposed schedule, I'm a bit concerned that you'll have 
> exams for five weeks of the coding period. Students are expected to average 
> 30+ hours/week on their projects. Is that feasible while you're studying 
> for exams?
>
> On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com 
> wrote:
>>
>> Hello !
>>
>> I have drafted a project-proposal for the idea that Russell laid out in 
>> his talk at DjangoCon '15. Here's the link to the draft:
>>
>> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460
>>
>> Looking forward to your suggestions on how best to improve this for a 
>> concrete GSoC '18 project-proposal.
>>
>> Regards
>> Priyansh
>>
>> On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
>> Keith-Magee wrote:
>>>
>>>
>>> Another approach would be to do what I laid out in this talk at 
>>> DjangoCon US 2015, following the last Summer of Code student who tackled 
>>> (tangentially) this problem. 
>>>
>>> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>>>
>>> That is - finish the modifications needed to Django’s core such that an 
>>> arbitrary model can register in a way compatible with the Admin and Forms 
>>> library. This was one of the reasons given for standardising the meta-model 
>>> framework, but didn’t make it into Daniel’s GSoC project, although he *did* 
>>> get a proof of concept working that exposed your Gmail inbox in Django’s 
>>> admin. 
>>>
>>> This would allow *any* data backend to expose an interface that is 
>>> fundamentally compatible with Django - which, really, just means “I want to 
>>> browse my data in the admin” and “I want to display a form for my model”. 
>>>
>>> It won’t allow an arbitrary ORM query to run against an arbitrary 
>>> “NoSQL” backend - but that’s idea was never going to work anyway. But I 
>>> don’t think anyone is serious about wanting that, either. All they want is 
>>> the ability to integrate a non-SQL data source into their basic Django 
>>> visualisations. 
>>>
>>> Yours, 
>>> Russ Magee %-) 
>>>
>>> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
>>> wrote: 
>>> > 
>>> > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
>>> >> Hello ! 
>>> >> What is the policy regarding NoSQL datastores being used as backends 
>>> ? I think adding support for something like MongoDB might be good idea. 
>>> > 
>>> > Could you elaborate on why you think it would be a good idea? 
>>> > 
>>> > I believe every other time the discussion has come up the following 
>>> points have been made. 
>>> > 
>>> > 1. "NoSQL" is not a DB category, it is an anti-category 
>>> > 2. Because of there there is no common data model, or query languages. 
>>> > 3. If you limit yourself to just document stores, there is still no 
>>> common query language [but this can be hidden by code] 
>>> > 4. Document stores are a really really bad fit for the ORM, as it's 
>>> designed for the relational model, not document model. 
>>> > 5. A better approach would be to develop an ODM, which is sufficiently 
>>> compatible with the ORM you can provide similar tools like ModelForms and 
>>> ModelAdmin, as well as GCBV. 
>>> > 
>>> > If I missed anything, I'm sure someone else will remind me. 
>>> > 
>>> > [Also... why is it always MongoDB, instead of something with a solid 
>>> reputation of reliability and performance?] 
>>> > 
>>> > -- 
>>> > Curtis 
>>> > 
>>> > 
>>> > -- 
>>> > 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. 
>>> > 

Google Summer of Code 2018

[Mberebe Guidona]

Hello everyone,

*Project idea*

I'm new in the google summer of code and as a Python-Django developer, I 
was interested in participating with your organisation for this year.
The project idea I have is the implementation of a CLI for Django projects 
(an example is the Angular CLI) for:

   - generating *views;*
   - generating *urls *as we implement the corresponding *view;*
   - generating models for the database;
   - etc.

*Why this project?*

I had this idea when developing some apps with Django and I had 
difficulties moving over the different files when ever I did some changes 
and this was really hard for me.
This is why I had this Idea in order to ease development.

*About me*

My name is Guy Mberebe Guidona, and I'm from Cameroon and a student of the 
National Advanced School of Engineering of Maroua.
As I said, this is my really first participation to the Google Summer of 
Code, and I really want to take part to this adventure. 

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/5930321b-0f10-41ce-acdd-22bd7c29b7cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I am still looking for Track tickets and other references (including 
third-party solutions) to formalise the idea. The work I propose should ideally 
make the process of using any arbitrary backend (like Google App Engine) much 
easier and uniform for every datastore.

The exams will take up no more than ten days (should have clarified this, 
apologies), it's just that they will take place at the start of the period I 
mentioned them in.

I'll do more research and get back to you in this. Meanwhile, ideas from the 
community will be of great help.

Thanks !
Priyansh

-- 
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/475b6c86-d5c8-4bb3-b994-4faae686edbf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Tim Graham]

Hi Priyansh,

Your proposal isn't really detailed enough for me to understand what the 
outcome of your project would be (I haven't watched Russell's talk that you 
linked). What are the "big wins"? There are projects like 
https://github.com/potatolondon/djangae, which allows using Django with 
Google App Engine. Would your project make something like that much 
simpler? You'll have to demonstrate a fairly sophisticated level of 
understanding of Django to convince us that you understand the problems 
well enough to have a reasonable chance of success.

Regarding your proposed schedule, I'm a bit concerned that you'll have 
exams for five weeks of the coding period. Students are expected to average 
30+ hours/week on their projects. Is that feasible while you're studying 
for exams?

On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com wrote:
>
> Hello !
>
> I have drafted a project-proposal for the idea that Russell laid out in 
> his talk at DjangoCon '15. Here's the link to the draft:
>
> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460
>
> Looking forward to your suggestions on how best to improve this for a 
> concrete GSoC '18 project-proposal.
>
> Regards
> Priyansh
>
> On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
> Keith-Magee wrote:
>>
>>
>> Another approach would be to do what I laid out in this talk at DjangoCon 
>> US 2015, following the last Summer of Code student who tackled 
>> (tangentially) this problem. 
>>
>> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>>
>> That is - finish the modifications needed to Django’s core such that an 
>> arbitrary model can register in a way compatible with the Admin and Forms 
>> library. This was one of the reasons given for standardising the meta-model 
>> framework, but didn’t make it into Daniel’s GSoC project, although he *did* 
>> get a proof of concept working that exposed your Gmail inbox in Django’s 
>> admin. 
>>
>> This would allow *any* data backend to expose an interface that is 
>> fundamentally compatible with Django - which, really, just means “I want to 
>> browse my data in the admin” and “I want to display a form for my model”. 
>>
>> It won’t allow an arbitrary ORM query to run against an arbitrary “NoSQL” 
>> backend - but that’s idea was never going to work anyway. But I don’t think 
>> anyone is serious about wanting that, either. All they want is the ability 
>> to integrate a non-SQL data source into their basic Django visualisations. 
>>
>> Yours, 
>> Russ Magee %-) 
>>
>> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
>> wrote: 
>> > 
>> > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
>> >> Hello ! 
>> >> What is the policy regarding NoSQL datastores being used as backends ? 
>> I think adding support for something like MongoDB might be good idea. 
>> > 
>> > Could you elaborate on why you think it would be a good idea? 
>> > 
>> > I believe every other time the discussion has come up the following 
>> points have been made. 
>> > 
>> > 1. "NoSQL" is not a DB category, it is an anti-category 
>> > 2. Because of there there is no common data model, or query languages. 
>> > 3. If you limit yourself to just document stores, there is still no 
>> common query language [but this can be hidden by code] 
>> > 4. Document stores are a really really bad fit for the ORM, as it's 
>> designed for the relational model, not document model. 
>> > 5. A better approach would be to develop an ODM, which is sufficiently 
>> compatible with the ORM you can provide similar tools like ModelForms and 
>> ModelAdmin, as well as GCBV. 
>> > 
>> > If I missed anything, I'm sure someone else will remind me. 
>> > 
>> > [Also... why is it always MongoDB, instead of something with a solid 
>> reputation of reliability and performance?] 
>> > 
>> > -- 
>> > Curtis 
>> > 
>> > 
>> > -- 
>> > 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/d9e38eeb-eab1-e0db-8d50-54abe6fb1afd%40tinbrain.net.
>>  
>>
>> > 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 

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I have drafted a project-proposal for the idea that Russell laid out in his 
talk at DjangoCon '15. Here's the link to the draft:

https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460

Looking forward to your suggestions on how best to improve this for a 
concrete GSoC '18 project-proposal.

Regards
Priyansh

On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell Keith-Magee 
wrote:
>
>
> Another approach would be to do what I laid out in this talk at DjangoCon 
> US 2015, following the last Summer of Code student who tackled 
> (tangentially) this problem. 
>
> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>
> That is - finish the modifications needed to Django’s core such that an 
> arbitrary model can register in a way compatible with the Admin and Forms 
> library. This was one of the reasons given for standardising the meta-model 
> framework, but didn’t make it into Daniel’s GSoC project, although he *did* 
> get a proof of concept working that exposed your Gmail inbox in Django’s 
> admin. 
>
> This would allow *any* data backend to expose an interface that is 
> fundamentally compatible with Django - which, really, just means “I want to 
> browse my data in the admin” and “I want to display a form for my model”. 
>
> It won’t allow an arbitrary ORM query to run against an arbitrary “NoSQL” 
> backend - but that’s idea was never going to work anyway. But I don’t think 
> anyone is serious about wanting that, either. All they want is the ability 
> to integrate a non-SQL data source into their basic Django visualisations. 
>
> Yours, 
> Russ Magee %-) 
>
> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  > wrote: 
> > 
> > On 02/13/2018 09:23 PM, askpr...@gmail.com  wrote: 
> >> Hello ! 
> >> What is the policy regarding NoSQL datastores being used as backends ? 
> I think adding support for something like MongoDB might be good idea. 
> > 
> > Could you elaborate on why you think it would be a good idea? 
> > 
> > I believe every other time the discussion has come up the following 
> points have been made. 
> > 
> > 1. "NoSQL" is not a DB category, it is an anti-category 
> > 2. Because of there there is no common data model, or query languages. 
> > 3. If you limit yourself to just document stores, there is still no 
> common query language [but this can be hidden by code] 
> > 4. Document stores are a really really bad fit for the ORM, as it's 
> designed for the relational model, not document model. 
> > 5. A better approach would be to develop an ODM, which is sufficiently 
> compatible with the ORM you can provide similar tools like ModelForms and 
> ModelAdmin, as well as GCBV. 
> > 
> > If I missed anything, I'm sure someone else will remind me. 
> > 
> > [Also... why is it always MongoDB, instead of something with a solid 
> reputation of reliability and performance?] 
> > 
> > -- 
> > Curtis 
> > 
> > 
> > -- 
> > 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/d9e38eeb-eab1-e0db-8d50-54abe6fb1afd%40tinbrain.net.
>  
>
> > 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/63d87409-3a23-4b95-920b-33dfc13bed6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

That sounds wonderful. I have got some experience with Cassandra and HBase. 
If that seems to be a good candidate for a GSoC project, I'll start 
drafting a proposal. Thanks for the advice !

Regards
Priyansh

On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell Keith-Magee 
wrote:
>
>
> Another approach would be to do what I laid out in this talk at DjangoCon 
> US 2015, following the last Summer of Code student who tackled 
> (tangentially) this problem. 
>
> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>
> That is - finish the modifications needed to Django’s core such that an 
> arbitrary model can register in a way compatible with the Admin and Forms 
> library. This was one of the reasons given for standardising the meta-model 
> framework, but didn’t make it into Daniel’s GSoC project, although he *did* 
> get a proof of concept working that exposed your Gmail inbox in Django’s 
> admin. 
>
> This would allow *any* data backend to expose an interface that is 
> fundamentally compatible with Django - which, really, just means “I want to 
> browse my data in the admin” and “I want to display a form for my model”. 
>
> It won’t allow an arbitrary ORM query to run against an arbitrary “NoSQL” 
> backend - but that’s idea was never going to work anyway. But I don’t think 
> anyone is serious about wanting that, either. All they want is the ability 
> to integrate a non-SQL data source into their basic Django visualisations. 
>
> Yours, 
> Russ Magee %-) 
>
> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  > wrote: 
> > 
> > On 02/13/2018 09:23 PM, askpr...@gmail.com  wrote: 
> >> Hello ! 
> >> What is the policy regarding NoSQL datastores being used as backends ? 
> I think adding support for something like MongoDB might be good idea. 
> > 
> > Could you elaborate on why you think it would be a good idea? 
> > 
> > I believe every other time the discussion has come up the following 
> points have been made. 
> > 
> > 1. "NoSQL" is not a DB category, it is an anti-category 
> > 2. Because of there there is no common data model, or query languages. 
> > 3. If you limit yourself to just document stores, there is still no 
> common query language [but this can be hidden by code] 
> > 4. Document stores are a really really bad fit for the ORM, as it's 
> designed for the relational model, not document model. 
> > 5. A better approach would be to develop an ODM, which is sufficiently 
> compatible with the ORM you can provide similar tools like ModelForms and 
> ModelAdmin, as well as GCBV. 
> > 
> > If I missed anything, I'm sure someone else will remind me. 
> > 
> > [Also... why is it always MongoDB, instead of something with a solid 
> reputation of reliability and performance?] 
> > 
> > -- 
> > Curtis 
> > 
> > 
> > -- 
> > 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/d9e38eeb-eab1-e0db-8d50-54abe6fb1afd%40tinbrain.net.
>  
>
> > 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/47cb28c3-a41c-45ca-9548-5a60e38aae01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Russell Keith-Magee]

Another approach would be to do what I laid out in this talk at DjangoCon US 
2015, following the last Summer of Code student who tackled (tangentially) this 
problem.

https://www.youtube.com/watch?v=VgM0qmpHDiE

That is - finish the modifications needed to Django’s core such that an 
arbitrary model can register in a way compatible with the Admin and Forms 
library. This was one of the reasons given for standardising the meta-model 
framework, but didn’t make it into Daniel’s GSoC project, although he *did* get 
a proof of concept working that exposed your Gmail inbox in Django’s admin.

This would allow *any* data backend to expose an interface that is 
fundamentally compatible with Django - which, really, just means “I want to 
browse my data in the admin” and “I want to display a form for my model”. 

It won’t allow an arbitrary ORM query to run against an arbitrary “NoSQL” 
backend - but that’s idea was never going to work anyway. But I don’t think 
anyone is serious about wanting that, either. All they want is the ability to 
integrate a non-SQL data source into their basic Django visualisations.

Yours,
Russ Magee %-)

> On 13 Feb 2018, at 6:48 pm, Curtis Maloney  wrote:
> 
> On 02/13/2018 09:23 PM, askpriya...@gmail.com wrote:
>> Hello !
>> What is the policy regarding NoSQL datastores being used as backends ? I 
>> think adding support for something like MongoDB might be good idea.
> 
> Could you elaborate on why you think it would be a good idea?
> 
> I believe every other time the discussion has come up the following points 
> have been made.
> 
> 1. "NoSQL" is not a DB category, it is an anti-category
> 2. Because of there there is no common data model, or query languages.
> 3. If you limit yourself to just document stores, there is still no common 
> query language [but this can be hidden by code]
> 4. Document stores are a really really bad fit for the ORM, as it's designed 
> for the relational model, not document model.
> 5. A better approach would be to develop an ODM, which is sufficiently 
> compatible with the ORM you can provide similar tools like ModelForms and 
> ModelAdmin, as well as GCBV.
> 
> If I missed anything, I'm sure someone else will remind me.
> 
> [Also... why is it always MongoDB, instead of something with a solid 
> reputation of reliability and performance?]
> 
> --
> Curtis
> 
> 
> -- 
> 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/d9e38eeb-eab1-e0db-8d50-54abe6fb1afd%40tinbrain.net.
> 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/4767F19D-7CC5-4A17-A843-5E787757A392%40keith-magee.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I thought it would be a good idea as it extends the functionality for 
developers who want to use NoSQL datastores (and possibly, distributed 
datastores like Hive and HBase). 


Would an ODM be a useful feature for Django ? Is there some work in progress 
that aims to develop an ODM ?

Regards
Priyansh

-- 
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/4861087e-3c5e-4fb9-8667-56142ac00f58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Curtis Maloney]

On 02/13/2018 09:23 PM, askpriya...@gmail.com wrote:

Hello !

What is the policy regarding NoSQL datastores being used as backends ? I think 
adding support for something like MongoDB might be good idea.


Could you elaborate on why you think it would be a good idea?

I believe every other time the discussion has come up the following 
points have been made.


1. "NoSQL" is not a DB category, it is an anti-category
2. Because of there there is no common data model, or query languages.
3. If you limit yourself to just document stores, there is still no 
common query language [but this can be hidden by code]
4. Document stores are a really really bad fit for the ORM, as it's 
designed for the relational model, not document model.
5. A better approach would be to develop an ODM, which is sufficiently 
compatible with the ORM you can provide similar tools like ModelForms 
and ModelAdmin, as well as GCBV.


If I missed anything, I'm sure someone else will remind me.

[Also... why is it always MongoDB, instead of something with a solid 
reputation of reliability and performance?]


--
Curtis


--
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/d9e38eeb-eab1-e0db-8d50-54abe6fb1afd%40tinbrain.net.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

What is the policy regarding NoSQL datastores being used as backends ? I think 
adding support for something like MongoDB might be good idea.

Regards
Priyansh

-- 
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/7bc40967-81f2-4c2c-9e3d-5231b6ae6889%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Tim Graham]

The Django Software Foundation has been selected as a Google Summer of Code 
2018 mentor organization. If you're interested in mentoring, being a 
student, or if you have a project idea (even if you aren't a student), you 
can use this thread for discussion. Please read the wiki page before 
posting: https://code.djangoproject.com/wiki/SummerOfCode2018

On Friday, December 15, 2017 at 10:34:25 AM UTC-5, perfectf...@gmail.com 
wrote:
>
> Hi all
>
> I am starting to learn how to contribute to django and would like to ask 
> if django is participating in GSoc 2018. I wish to spend my summer 
> contributing to django.
>
> Thanks in advance!
>

-- 
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/3f3100c3-9974-4b32-956b-4400fff66860%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Google Summer of Code 2018

[perfectformiskey]

Hi all

I am learning how to contribute to django and wonder if django is joining 
GSoc 2018. I wish to contribute to django in the upcoming summer.

Thank you!

-- 
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/fc134df3-2007-473b-b2a7-da32458f26ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Google Summer of Code 2018

[perfectformiskey]

Hi all

I am starting to learn how to contribute to django and would like to ask if 
django is participating in GSoc 2018. I wish to spend my summer 
contributing to django.

Thanks in advance!

-- 
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/37c1b7da-72cc-4be1-b4a4-cf360787a318%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.