Re: Google Summer of Code 2019

2019-03-03 Thread Carlton Gibson
Hi. 

In general, for GSoC, I want to look at the project ideas, the org profile, 
and such over the next couple of weeks.
I try and make the Org page the starting point. 

Kind Regards,
Carlton

On Sunday, 3 March 2019 15:01:12 UTC+1, Gaurav Agarwal wrote:
>
> Hi, I am a student from IIT Guwahati. I am familiar with Python and 
> Django. I want to contribute. How should I start?
>
>
> On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:
>>
>> Org applications for Google's Summer of Code are now open (deadline 
>> February 6). Do you think the Django Software Foundation should participate?
>>
>> We haven't had any high quality student applications that we could accept 
>> for the past two years.
>>
>> Perhaps it's partly a function of a poor ideas page (
>> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't 
>> do a great job of publicizing our involvement and attracting high quality 
>> students. Perhaps it's because the student payment isn't all that much 
>> (+/-$6000 USD, depending on student's country)* for the amount of work 
>> involved (also, students have to put in a lot of work up front in their 
>> application, with no guarantee of being accepted into the program).
>>
>> If you have any ideas about mentoring or suggesting a project, or if 
>> you're serious about being a student (you should start contributing to 
>> Django now if you don't already), please share.
>>
>> * https://developers.google.com/open-source/gsoc/help/student-stipends
>>
>

-- 
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/819dd1bf-4d62-47b7-93f7-fed20192ed37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-03-03 Thread Gaurav Agarwal
Hi, I am a student from IIT Guwahati. I am familiar with Python and Django. 
I want to contribute. How should I start?


On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:
>
> Org applications for Google's Summer of Code are now open (deadline 
> February 6). Do you think the Django Software Foundation should participate?
>
> We haven't had any high quality student applications that we could accept 
> for the past two years.
>
> Perhaps it's partly a function of a poor ideas page (
> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't 
> do a great job of publicizing our involvement and attracting high quality 
> students. Perhaps it's because the student payment isn't all that much 
> (+/-$6000 USD, depending on student's country)* for the amount of work 
> involved (also, students have to put in a lot of work up front in their 
> application, with no guarantee of being accepted into the program).
>
> If you have any ideas about mentoring or suggesting a project, or if 
> you're serious about being a student (you should start contributing to 
> Django now if you don't already), please share.
>
> * https://developers.google.com/open-source/gsoc/help/student-stipends
>

-- 
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/112e5823-538b-4628-ac0b-7fe5bffc26ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-03-02 Thread PARTH PATIL
Hey its been quite a while, I have posted my idea for gsoc here 
. 
Can someone please review it so that i can decide whether to move with this 
or think of something else.

-- 
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/ba977bab-0c54-4fcf-a4be-39b1918a79b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-16 Thread Aleksi Häkli
Just my 2 cents or ramblings on the topic of GSoC and deployment:

Most Django deployments we do are executed by running containers from 
custom built Docker images from private repositories.

They are mostly run with either

- Docker Compose on small scale, or
- Heroku, Kubernetes or other container orchestrator on larger scale.

The Docker images and their packaging are starting to look quite similar 
these days with their 12-factor setups and service oriented approaches.

The baseline package is usually just a Python template that runs Django 
installation with all the checks, static file compilation, and whatnot at 
the end of the image build. 

Then there is, usually, a shell startup script, that is run as an 
entrypoint, which runs migrate and other state related commands on 
container startup and execs the Django application as configured.

The Docker images we build ideally support running multimode with the 

- web server container running Gunicorn, uwsgi, or a similar HTTP 
application server, and 
- the background worker container running a task executor like Celery or 
Django Q

and the container orchestrator just supplying the command (one can think of 
this as the "mode") to run in.

This is all and good, and Django supports a runner setup like this 
beautifully without any gimmicks with Docker images and containers. 

Well, you have to figure out the necessary build and startup commands and 
so forth, but there are good online resources for figuring out those things 
nowadays.

Progressing to the point I am trying to bring up, I think that 
containerization instructions with some good examples including stuff like 

- Docker image packaging for a basic Django web server using FOSS 
components,
- configuration and settings examples in a Docker build and deployment 
setup for Django,
- multimode container examples for running in web server or web worker role,
- sane defaults for security hardening and checkups, and
- defining startup scripts for running tasks like migrations before 
application execution

could be quite invaluable in the Django deployment documentation at e.g. 
https://docs.djangoproject.com/en/dev/howto/deployment/

The deployments are starting to look so similar these days that supplying 
good stock examples for packaging a basic web server and web worker image 
and running it as a container could be a good idea that could save 
tremendous amounts of time for people building their first or second 
deployments. Best practices never hurt anybody either.

Of course e.g. many of the Cookiecutter templates available have examples 
for Docker packaging, but none of the ones I have seen discuss the process 
in an easily accessible format that ties in well with Django development 
and documentation. They are usually more expert oriented and just supply 
some opinionated configuration examples that might or might not work or be 
secure or up-to-date. 

I imagine at least including some Docker packaging and workload 
containerization components in the GSoC proposition could be helpful. 
Packaging could align with the GSoC motives as e.g. Kubernetes enablement 
is well in line with modern IaaS hosting interests.

Regards,
A DevOps guy

On Friday, 15 February 2019 13:22:22 UTC+2, Josh Smeaton wrote:
>
> If you really think you want to work on a deployment project, you should 
> get the requirements together very quickly, so someone on this list can 
> sanity check that it's something both feasible and useful.
>
> I have done a **lot** of different deployments, and other than deploying 
> to heroku, they have never been the same. I'm rather skeptical that some 
> tool can be built for deploying a Django application that didn't already 
> mimic an existing tool like Ansible or Salt (or Heroku CLI).
>
> Examples: what application server (gunicorn, uwsgi, mod_wsgi)? What web 
> server (nginx, apache, caddy)? What database server, and is it remote or 
> local? How are environment variables securely provisioned and deployed? 
> Where is static content served from, and do you need S3 keys? How are you 
> managing TLS certificates?
>
> Start a new thread on this list when you have an outline for what you want 
> to do. At that stage we should be able to tell you if you should proceed 
> with a detailed project scope or not. I don't want you to work on a 
> detailed project scope and then get knocked back for the idea being 
> infeasible. Remember, the project would need to be very useful for Django 
> users.
>
> I'd also just like to call out that projects like Django Channels would 
> likely be in scope too, provided the current maintainers felt comfortable 
> mentoring a student. A quick note about Channels specifically - the current 
> maintainers have **just** taken up that mantle, so you should have a 
> specific idea in mind if that's what you're interested in, not ask the team 
> for ideas.
>
>
>
>
> On Friday, 15 February 2019 20:53:34 UTC+11, Shashank shet wrote:
>>
>> That's a good 

Re: Google Summer of Code 2019

2019-02-15 Thread Shashank shet
I was looking into how ansible is used to automate the deployment procedure 
for django, and it does indeed seem to cover a lot of ground. It seems 
unlikely that I can add anything particularly new to the automation 
process. 

On Friday, February 15, 2019 at 5:19:24 PM UTC+5:30, Adam Johnson wrote:
>
> Yes in my experience Heroku/Divio/Elastic Beanstalk/other PaaS platforms 
> already fit the space of a "simple Django deployment". I am also skeptical, 
> I'd need to see how it fit in the space, what it does differently, and how 
> it will be maintained long term. I think it's a bit outside the remit of 
> DSF as it stands.
>
> On Fri, 15 Feb 2019 at 12:22, Josh Smeaton  > wrote:
>
>> If you really think you want to work on a deployment project, you should 
>> get the requirements together very quickly, so someone on this list can 
>> sanity check that it's something both feasible and useful.
>>
>> I have done a **lot** of different deployments, and other than deploying 
>> to heroku, they have never been the same. I'm rather skeptical that some 
>> tool can be built for deploying a Django application that didn't already 
>> mimic an existing tool like Ansible or Salt (or Heroku CLI).
>>
>> Examples: what application server (gunicorn, uwsgi, mod_wsgi)? What web 
>> server (nginx, apache, caddy)? What database server, and is it remote or 
>> local? How are environment variables securely provisioned and deployed? 
>> Where is static content served from, and do you need S3 keys? How are you 
>> managing TLS certificates?
>>
>> Start a new thread on this list when you have an outline for what you 
>> want to do. At that stage we should be able to tell you if you should 
>> proceed with a detailed project scope or not. I don't want you to work on a 
>> detailed project scope and then get knocked back for the idea being 
>> infeasible. Remember, the project would need to be very useful for Django 
>> users.
>>
>> I'd also just like to call out that projects like Django Channels would 
>> likely be in scope too, provided the current maintainers felt comfortable 
>> mentoring a student. A quick note about Channels specifically - the current 
>> maintainers have **just** taken up that mantle, so you should have a 
>> specific idea in mind if that's what you're interested in, not ask the team 
>> for ideas.
>>
>>
>>
>>
>> On Friday, 15 February 2019 20:53:34 UTC+11, Shashank shet wrote:
>>>
>>> That's a good idea. I'll start working on a draft for the deployment 
>>> support project.
>>>
>>> On Friday, February 15, 2019 at 2:58:45 PM UTC+5:30, Carlton Gibson 
>>> wrote:

 The timeline for GSoC is here: 
 https://summerofcode.withgoogle.com/how-it-works/#timeline

 Applications are ≈ a month away. 

 Here's an example from a previous year: 
 https://gist.github.com/chrismedrela/82cbda8d2a78a280a129

 I'd suggest drafting things in more detail and starting a new thread to 
 invite discussion. 

 I don't know what'll be suitable: it depends on the proposal: 

 - something not in core? Yeah, maybe. 
 - Something for deployment? Well, seems a bit ambitious, but again 
 maybe... 
 - Bringing the two(?) community Redis cache backends into one in core? 
 Reasonable idea perhaps, yes. 
 - A cross-db JSONField etc. Yep, great... 

 ...and so on. What do you want to work on? 


 -- 
>> 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/350d7430-5644-4faa-8019-6e0968e554f1%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/7c9c8c10-f8f3-4a5a-a9d9-37e0b8e10cc4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-15 Thread Adam Johnson
Yes in my experience Heroku/Divio/Elastic Beanstalk/other PaaS platforms
already fit the space of a "simple Django deployment". I am also skeptical,
I'd need to see how it fit in the space, what it does differently, and how
it will be maintained long term. I think it's a bit outside the remit of
DSF as it stands.

On Fri, 15 Feb 2019 at 12:22, Josh Smeaton  wrote:

> If you really think you want to work on a deployment project, you should
> get the requirements together very quickly, so someone on this list can
> sanity check that it's something both feasible and useful.
>
> I have done a **lot** of different deployments, and other than deploying
> to heroku, they have never been the same. I'm rather skeptical that some
> tool can be built for deploying a Django application that didn't already
> mimic an existing tool like Ansible or Salt (or Heroku CLI).
>
> Examples: what application server (gunicorn, uwsgi, mod_wsgi)? What web
> server (nginx, apache, caddy)? What database server, and is it remote or
> local? How are environment variables securely provisioned and deployed?
> Where is static content served from, and do you need S3 keys? How are you
> managing TLS certificates?
>
> Start a new thread on this list when you have an outline for what you want
> to do. At that stage we should be able to tell you if you should proceed
> with a detailed project scope or not. I don't want you to work on a
> detailed project scope and then get knocked back for the idea being
> infeasible. Remember, the project would need to be very useful for Django
> users.
>
> I'd also just like to call out that projects like Django Channels would
> likely be in scope too, provided the current maintainers felt comfortable
> mentoring a student. A quick note about Channels specifically - the current
> maintainers have **just** taken up that mantle, so you should have a
> specific idea in mind if that's what you're interested in, not ask the team
> for ideas.
>
>
>
>
> On Friday, 15 February 2019 20:53:34 UTC+11, Shashank shet wrote:
>>
>> That's a good idea. I'll start working on a draft for the deployment
>> support project.
>>
>> On Friday, February 15, 2019 at 2:58:45 PM UTC+5:30, Carlton Gibson wrote:
>>>
>>> The timeline for GSoC is here:
>>> https://summerofcode.withgoogle.com/how-it-works/#timeline
>>>
>>> Applications are ≈ a month away.
>>>
>>> Here's an example from a previous year:
>>> https://gist.github.com/chrismedrela/82cbda8d2a78a280a129
>>>
>>> I'd suggest drafting things in more detail and starting a new thread to
>>> invite discussion.
>>>
>>> I don't know what'll be suitable: it depends on the proposal:
>>>
>>> - something not in core? Yeah, maybe.
>>> - Something for deployment? Well, seems a bit ambitious, but again
>>> maybe...
>>> - Bringing the two(?) community Redis cache backends into one in core?
>>> Reasonable idea perhaps, yes.
>>> - A cross-db JSONField etc. Yep, great...
>>>
>>> ...and so on. What do you want to work on?
>>>
>>>
>>> --
> 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/350d7430-5644-4faa-8019-6e0968e554f1%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/CAMyDDM32XngBPjV8-VDKZK6O2pW-nRrJeRiK4-peh1XU2u9gKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-15 Thread Josh Smeaton
If you really think you want to work on a deployment project, you should 
get the requirements together very quickly, so someone on this list can 
sanity check that it's something both feasible and useful.

I have done a **lot** of different deployments, and other than deploying to 
heroku, they have never been the same. I'm rather skeptical that some tool 
can be built for deploying a Django application that didn't already mimic 
an existing tool like Ansible or Salt (or Heroku CLI).

Examples: what application server (gunicorn, uwsgi, mod_wsgi)? What web 
server (nginx, apache, caddy)? What database server, and is it remote or 
local? How are environment variables securely provisioned and deployed? 
Where is static content served from, and do you need S3 keys? How are you 
managing TLS certificates?

Start a new thread on this list when you have an outline for what you want 
to do. At that stage we should be able to tell you if you should proceed 
with a detailed project scope or not. I don't want you to work on a 
detailed project scope and then get knocked back for the idea being 
infeasible. Remember, the project would need to be very useful for Django 
users.

I'd also just like to call out that projects like Django Channels would 
likely be in scope too, provided the current maintainers felt comfortable 
mentoring a student. A quick note about Channels specifically - the current 
maintainers have **just** taken up that mantle, so you should have a 
specific idea in mind if that's what you're interested in, not ask the team 
for ideas.




On Friday, 15 February 2019 20:53:34 UTC+11, Shashank shet wrote:
>
> That's a good idea. I'll start working on a draft for the deployment 
> support project.
>
> On Friday, February 15, 2019 at 2:58:45 PM UTC+5:30, Carlton Gibson wrote:
>>
>> The timeline for GSoC is here: 
>> https://summerofcode.withgoogle.com/how-it-works/#timeline
>>
>> Applications are ≈ a month away. 
>>
>> Here's an example from a previous year: 
>> https://gist.github.com/chrismedrela/82cbda8d2a78a280a129
>>
>> I'd suggest drafting things in more detail and starting a new thread to 
>> invite discussion. 
>>
>> I don't know what'll be suitable: it depends on the proposal: 
>>
>> - something not in core? Yeah, maybe. 
>> - Something for deployment? Well, seems a bit ambitious, but again 
>> maybe... 
>> - Bringing the two(?) community Redis cache backends into one in core? 
>> Reasonable idea perhaps, yes. 
>> - A cross-db JSONField etc. Yep, great... 
>>
>> ...and so on. What do you want to work on? 
>>
>>
>>

-- 
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/350d7430-5644-4faa-8019-6e0968e554f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-15 Thread Shashank shet
That's a good idea. I'll start working on a draft for the deployment 
support project.

On Friday, February 15, 2019 at 2:58:45 PM UTC+5:30, Carlton Gibson wrote:
>
> The timeline for GSoC is here: 
> https://summerofcode.withgoogle.com/how-it-works/#timeline
>
> Applications are ≈ a month away. 
>
> Here's an example from a previous year: 
> https://gist.github.com/chrismedrela/82cbda8d2a78a280a129
>
> I'd suggest drafting things in more detail and starting a new thread to 
> invite discussion. 
>
> I don't know what'll be suitable: it depends on the proposal: 
>
> - something not in core? Yeah, maybe. 
> - Something for deployment? Well, seems a bit ambitious, but again 
> maybe... 
> - Bringing the two(?) community Redis cache backends into one in core? 
> Reasonable idea perhaps, yes. 
> - A cross-db JSONField etc. Yep, great... 
>
> ...and so on. What do you want to work on? 
>
>
>

-- 
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/e9f01e8c-285e-44e8-99af-e5b323b4bd28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-15 Thread Carlton Gibson
The timeline for GSoC is 
here: https://summerofcode.withgoogle.com/how-it-works/#timeline

Applications are ≈ a month away. 

Here's an example from a previous 
year: https://gist.github.com/chrismedrela/82cbda8d2a78a280a129

I'd suggest drafting things in more detail and starting a new thread to 
invite discussion. 

I don't know what'll be suitable: it depends on the proposal: 

- something not in core? Yeah, maybe. 
- Something for deployment? Well, seems a bit ambitious, but again maybe... 
- Bringing the two(?) community Redis cache backends into one in core? 
Reasonable idea perhaps, yes. 
- A cross-db JSONField etc. Yep, great... 

...and so on. What do you want to work on? 


-- 
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/e1e1aed4-ef58-498d-b03e-e29e0246f9c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-14 Thread vineeth sagar
One good thing we can add is redis support for caching, it's good that
there are libraries out there, it's about time redis is included, because
it's well documented and does all the things memcached does and even more.

Or maybe some async support.

regards
Vineeth

On Thu, 14 Feb, 2019, 23:30 Tom Forbes  Out of interest, do the projects for GSOC have to fall within the Django
> repository themselves? Could they be an associated project under the Django
> umbrella?
>
> I think something that helps with deployment in general could be
> interesting, but it definitely does not live inside Django core. However
> some form of 3rd party package exploring this is another matter entirely.
>
> On 14 February 2019 at 17:56:04, Carlton Gibson (carlton.gib...@gmail.com)
> wrote:
>
> Hmmm. I think that would be out for scope for Django. More suited to tools
> such as Ansible (and similar). I don't think adding a one step deployment
> story would really be feasible within a GSoC project. (As you say, it's
> very complex.)
>
> On Thursday, 14 February 2019 18:46:52 UTC+1, Shashank shet wrote:
>>
>> Thank you Carlton. I had in mind an idea for providing out-of-the-box
>> webserver deployment capability. In the projects I've done, one of the most
>> time consuming tasks for us was deployment on a server, mainly due to a
>> lack of experience. That's why I figured that an automated system for
>> deployment would be helpful. It would work similar to the runserver
>> command, taking essential configurations from a designated file and not
>> having to actually make changes to files in different parts of the
>> filesystem, or following a long list of instructions manually. Any
>> suggestion would be very helpful.
>>
>>
>> On Thursday, February 14, 2019 at 6:32:17 PM UTC+5:30, Carlton Gibson
>> wrote:
>>>
>>> Hi Shashank.
>>>
>>> "Sir"? That's my father, surely.  (Not "sir" )
>>>
>>> We've applied as an Org. Haven't heard yet whether we'll be accepted.
>>>
>>> If so, proposals would be welcome. We'd then need to think about
>>> mentors. Good proposals will draw out people there.
>>>
>>> If we can get all that lined up then, yes, in principle we're accepting
>>> applications.
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>> On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote:

 Hello Carlton sir,
 I have worked on Django as a part of a project and wished to ask if the
 organization is still accepting proposals for GSoC 2019.

 On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson
 wrote:
>
> And thank you Tim, yes, exactly what I need.
>
> To all:
>
> I will put in the org application today. We'll then see about the
> proposals.
>
> The main thing is that we need to know who you are, and have
> confidence in you in order to commit to the project with you.
> For people to mentor you is a big commitment of time and energy. You
> need to demonstrate that will be well invested.
>
> The way to do that is to get involved and show us who you are over the
> next few months.
> Help reproduce bugs, review patches, create patches etc.
> It doesn't take much before you're visible. (Really!)
>
> The best way (also) to come up with project ideas is to see where
> there are issues already.
> (Much better than us providing a list.) So again, be involved.
>
> If you start now, there's still lots of time, so I'm hoping.
>
> Kind Regards,
>
> Carlton
>
>
>
>
>
> On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:
>>
>> It's a private wiki that only Django team members like Carlton can
>> access. It contains the information for Django to apply for GSoC.
>>
>> On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco
>> wrote:
>>>
>>> Hi Tim,
>>>
>>> It returns 404 to me
>>>
>>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>>
>>> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham <
>>> timog...@gmail.com> ha scritto:
>>>
 All answers are at
 https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info

>>> --
> 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/87bb632d-360c-486d-92e1-431ddcb05bb2%40googlegroups.com
> 

Re: Google Summer of Code 2019

2019-02-14 Thread kamalesh palanisamy
I have also been working on Django for two projects when will the 
applications be available Sir?

On Thursday, February 14, 2019 at 6:32:17 PM UTC+5:30, Carlton Gibson wrote:
>
> Hi Shashank. 
>
> "Sir"? That's my father, surely.  (Not "sir" ) 
>
> We've applied as an Org. Haven't heard yet whether we'll be accepted. 
>
> If so, proposals would be welcome. We'd then need to think about mentors. 
> Good proposals will draw out people there. 
>
> If we can get all that lined up then, yes, in principle we're accepting 
> applications. 
>
> Kind Regards,
>
> Carlton
>
>
> On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote:
>>
>> Hello Carlton sir,
>> I have worked on Django as a part of a project and wished to ask if the 
>> organization is still accepting proposals for GSoC 2019. 
>>
>> On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson wrote:
>>>
>>> And thank you Tim, yes, exactly what I need. 
>>>
>>> To all: 
>>>
>>> I will put in the org application today. We'll then see about the 
>>> proposals. 
>>>
>>> The main thing is that we need to know who you are, and have confidence 
>>> in you in order to commit to the project with you. 
>>> For people to mentor you is a big commitment of time and energy. You 
>>> need to demonstrate that will be well invested. 
>>>
>>> The way to do that is to get involved and show us who you are over the 
>>> next few months. 
>>> Help reproduce bugs, review patches, create patches etc. 
>>> It doesn't take much before you're visible. (Really!) 
>>>
>>> The best way (also) to come up with project ideas is to see where there 
>>> are issues already. 
>>> (Much better than us providing a list.) So again, be involved. 
>>>
>>> If you start now, there's still lots of time, so I'm hoping. 
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>>
>>>
>>>
>>> On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:

 It's a private wiki that only Django team members like Carlton can 
 access. It contains the information for Django to apply for GSoC.

 On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco 
 wrote:
>
> Hi Tim,
>
> It returns 404 to me
>
> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>
> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham  
> ha scritto:
>
>> All answers are at 
>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>
>

-- 
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/33db7ed5-8786-429b-a342-03dd4a84f7ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-14 Thread Shashank shet
That seems accurate.
In your opinion, would it still be infeasible to provide support for one 
stack to begin with? For example: gunicorn + nginx? And that can ultimately 
lead to support for other configurations.

On Thursday, February 14, 2019 at 11:25:57 PM UTC+5:30, Carlton Gibson 
wrote:
>
> Hmmm. I think that would be out for scope for Django. More suited to tools 
> such as Ansible (and similar). I don't think adding a one step deployment 
> story would really be feasible within a GSoC project. (As you say, it's 
> very complex.) 
>
> On Thursday, 14 February 2019 18:46:52 UTC+1, Shashank shet wrote:
>>
>> Thank you Carlton. I had in mind an idea for providing out-of-the-box 
>> webserver deployment capability. In the projects I've done, one of the most 
>> time consuming tasks for us was deployment on a server, mainly due to a 
>> lack of experience. That's why I figured that an automated system for 
>> deployment would be helpful. It would work similar to the runserver 
>> command, taking essential configurations from a designated file and not 
>> having to actually make changes to files in different parts of the 
>> filesystem, or following a long list of instructions manually. Any 
>> suggestion would be very helpful.
>>
>>
>> On Thursday, February 14, 2019 at 6:32:17 PM UTC+5:30, Carlton Gibson 
>> wrote:
>>>
>>> Hi Shashank. 
>>>
>>> "Sir"? That's my father, surely.  (Not "sir" ) 
>>>
>>> We've applied as an Org. Haven't heard yet whether we'll be accepted. 
>>>
>>> If so, proposals would be welcome. We'd then need to think about 
>>> mentors. Good proposals will draw out people there. 
>>>
>>> If we can get all that lined up then, yes, in principle we're accepting 
>>> applications. 
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>> On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote:

 Hello Carlton sir,
 I have worked on Django as a part of a project and wished to ask if the 
 organization is still accepting proposals for GSoC 2019. 

 On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson 
 wrote:
>
> And thank you Tim, yes, exactly what I need. 
>
> To all: 
>
> I will put in the org application today. We'll then see about the 
> proposals. 
>
> The main thing is that we need to know who you are, and have 
> confidence in you in order to commit to the project with you. 
> For people to mentor you is a big commitment of time and energy. You 
> need to demonstrate that will be well invested. 
>
> The way to do that is to get involved and show us who you are over the 
> next few months. 
> Help reproduce bugs, review patches, create patches etc. 
> It doesn't take much before you're visible. (Really!) 
>
> The best way (also) to come up with project ideas is to see where 
> there are issues already. 
> (Much better than us providing a list.) So again, be involved. 
>
> If you start now, there's still lots of time, so I'm hoping. 
>
> Kind Regards,
>
> Carlton
>
>
>
>
>
> On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:
>>
>> It's a private wiki that only Django team members like Carlton can 
>> access. It contains the information for Django to apply for GSoC.
>>
>> On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco 
>> wrote:
>>>
>>> Hi Tim,
>>>
>>> It returns 404 to me
>>>
>>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>>
>>> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham <
>>> timog...@gmail.com> ha scritto:
>>>
 All answers are at 
 https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info

>>>

-- 
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/3524c6a5-0b6f-4fae-ad92-c007b51cc4cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-14 Thread Tom Forbes
Out of interest, do the projects for GSOC have to fall within the Django 
repository themselves? Could they be an associated project under the Django 
umbrella?

I think something that helps with deployment in general could be interesting, 
but it definitely does not live inside Django core. However some form of 3rd 
party package exploring this is another matter entirely.

On 14 February 2019 at 17:56:04, Carlton Gibson (carlton.gib...@gmail.com) 
wrote:

Hmmm. I think that would be out for scope for Django. More suited to tools such 
as Ansible (and similar). I don't think adding a one step deployment story 
would really be feasible within a GSoC project. (As you say, it's very 
complex.) 

On Thursday, 14 February 2019 18:46:52 UTC+1, Shashank shet wrote:
Thank you Carlton. I had in mind an idea for providing out-of-the-box webserver 
deployment capability. In the projects I've done, one of the most time 
consuming tasks for us was deployment on a server, mainly due to a lack of 
experience. That's why I figured that an automated system for deployment would 
be helpful. It would work similar to the runserver command, taking essential 
configurations from a designated file and not having to actually make changes 
to files in different parts of the filesystem, or following a long list of 
instructions manually. Any suggestion would be very helpful.


On Thursday, February 14, 2019 at 6:32:17 PM UTC+5:30, Carlton Gibson wrote:
Hi Shashank. 

"Sir"? That's my father, surely.  (Not "sir" ) 

We've applied as an Org. Haven't heard yet whether we'll be accepted. 

If so, proposals would be welcome. We'd then need to think about mentors. Good 
proposals will draw out people there. 

If we can get all that lined up then, yes, in principle we're accepting 
applications. 

Kind Regards,

Carlton


On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote:
Hello Carlton sir,
I have worked on Django as a part of a project and wished to ask if the 
organization is still accepting proposals for GSoC 2019.

On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson wrote:
And thank you Tim, yes, exactly what I need. 

To all: 

I will put in the org application today. We'll then see about the proposals. 

The main thing is that we need to know who you are, and have confidence in you 
in order to commit to the project with you. 
For people to mentor you is a big commitment of time and energy. You need to 
demonstrate that will be well invested. 

The way to do that is to get involved and show us who you are over the next few 
months. 
Help reproduce bugs, review patches, create patches etc. 
It doesn't take much before you're visible. (Really!) 

The best way (also) to come up with project ideas is to see where there are 
issues already. 
(Much better than us providing a list.) So again, be involved. 

If you start now, there's still lots of time, so I'm hoping. 

Kind Regards,

Carlton





On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:
It's a private wiki that only Django team members like Carlton can access. It 
contains the information for Django to apply for GSoC.

On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco wrote:
Hi Tim,

It returns 404 to me
https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info

Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham  ha 
scritto:
All answers are at 
https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
--
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/87bb632d-360c-486d-92e1-431ddcb05bb2%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/etPan.5c65ac70.3059ef5e.2b4%40tomforb.es.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-14 Thread Carlton Gibson
Hmmm. I think that would be out for scope for Django. More suited to tools 
such as Ansible (and similar). I don't think adding a one step deployment 
story would really be feasible within a GSoC project. (As you say, it's 
very complex.) 

On Thursday, 14 February 2019 18:46:52 UTC+1, Shashank shet wrote:
>
> Thank you Carlton. I had in mind an idea for providing out-of-the-box 
> webserver deployment capability. In the projects I've done, one of the most 
> time consuming tasks for us was deployment on a server, mainly due to a 
> lack of experience. That's why I figured that an automated system for 
> deployment would be helpful. It would work similar to the runserver 
> command, taking essential configurations from a designated file and not 
> having to actually make changes to files in different parts of the 
> filesystem, or following a long list of instructions manually. Any 
> suggestion would be very helpful.
>
>
> On Thursday, February 14, 2019 at 6:32:17 PM UTC+5:30, Carlton Gibson 
> wrote:
>>
>> Hi Shashank. 
>>
>> "Sir"? That's my father, surely.  (Not "sir" ) 
>>
>> We've applied as an Org. Haven't heard yet whether we'll be accepted. 
>>
>> If so, proposals would be welcome. We'd then need to think about mentors. 
>> Good proposals will draw out people there. 
>>
>> If we can get all that lined up then, yes, in principle we're accepting 
>> applications. 
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>> On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote:
>>>
>>> Hello Carlton sir,
>>> I have worked on Django as a part of a project and wished to ask if the 
>>> organization is still accepting proposals for GSoC 2019. 
>>>
>>> On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson wrote:

 And thank you Tim, yes, exactly what I need. 

 To all: 

 I will put in the org application today. We'll then see about the 
 proposals. 

 The main thing is that we need to know who you are, and have confidence 
 in you in order to commit to the project with you. 
 For people to mentor you is a big commitment of time and energy. You 
 need to demonstrate that will be well invested. 

 The way to do that is to get involved and show us who you are over the 
 next few months. 
 Help reproduce bugs, review patches, create patches etc. 
 It doesn't take much before you're visible. (Really!) 

 The best way (also) to come up with project ideas is to see where there 
 are issues already. 
 (Much better than us providing a list.) So again, be involved. 

 If you start now, there's still lots of time, so I'm hoping. 

 Kind Regards,

 Carlton





 On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:
>
> It's a private wiki that only Django team members like Carlton can 
> access. It contains the information for Django to apply for GSoC.
>
> On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco 
> wrote:
>>
>> Hi Tim,
>>
>> It returns 404 to me
>>
>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>
>> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham <
>> timog...@gmail.com> ha scritto:
>>
>>> All answers are at 
>>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>>
>>

-- 
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/87bb632d-360c-486d-92e1-431ddcb05bb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-14 Thread Shashank shet
Thank you Carlton. I had in mind an idea for providing out-of-the-box 
webserver deployment capability. In the projects I've done, one of the most 
time consuming tasks for us was deployment on a server, mainly due to a 
lack of experience. That's why I figured that an automated system for 
deployment would be helpful. It would work similar to the runserver 
command, taking essential configurations from a designated file and not 
having to actually make changes to files in different parts of the 
filesystem, or following a long list of instructions manually. Any 
suggestion would be very helpful.


On Thursday, February 14, 2019 at 6:32:17 PM UTC+5:30, Carlton Gibson wrote:
>
> Hi Shashank. 
>
> "Sir"? That's my father, surely.  (Not "sir" ) 
>
> We've applied as an Org. Haven't heard yet whether we'll be accepted. 
>
> If so, proposals would be welcome. We'd then need to think about mentors. 
> Good proposals will draw out people there. 
>
> If we can get all that lined up then, yes, in principle we're accepting 
> applications. 
>
> Kind Regards,
>
> Carlton
>
>
> On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote:
>>
>> Hello Carlton sir,
>> I have worked on Django as a part of a project and wished to ask if the 
>> organization is still accepting proposals for GSoC 2019. 
>>
>> On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson wrote:
>>>
>>> And thank you Tim, yes, exactly what I need. 
>>>
>>> To all: 
>>>
>>> I will put in the org application today. We'll then see about the 
>>> proposals. 
>>>
>>> The main thing is that we need to know who you are, and have confidence 
>>> in you in order to commit to the project with you. 
>>> For people to mentor you is a big commitment of time and energy. You 
>>> need to demonstrate that will be well invested. 
>>>
>>> The way to do that is to get involved and show us who you are over the 
>>> next few months. 
>>> Help reproduce bugs, review patches, create patches etc. 
>>> It doesn't take much before you're visible. (Really!) 
>>>
>>> The best way (also) to come up with project ideas is to see where there 
>>> are issues already. 
>>> (Much better than us providing a list.) So again, be involved. 
>>>
>>> If you start now, there's still lots of time, so I'm hoping. 
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>>
>>>
>>>
>>> On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:

 It's a private wiki that only Django team members like Carlton can 
 access. It contains the information for Django to apply for GSoC.

 On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco 
 wrote:
>
> Hi Tim,
>
> It returns 404 to me
>
> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>
> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham  
> ha scritto:
>
>> All answers are at 
>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>
>

-- 
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/768cd93b-5910-4f1c-84ed-cdfc6bf27da1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-14 Thread Carlton Gibson
Hi Shashank. 

"Sir"? That's my father, surely.  (Not "sir" ) 

We've applied as an Org. Haven't heard yet whether we'll be accepted. 

If so, proposals would be welcome. We'd then need to think about mentors. 
Good proposals will draw out people there. 

If we can get all that lined up then, yes, in principle we're accepting 
applications. 

Kind Regards,

Carlton


On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote:
>
> Hello Carlton sir,
> I have worked on Django as a part of a project and wished to ask if the 
> organization is still accepting proposals for GSoC 2019. 
>
> On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson wrote:
>>
>> And thank you Tim, yes, exactly what I need. 
>>
>> To all: 
>>
>> I will put in the org application today. We'll then see about the 
>> proposals. 
>>
>> The main thing is that we need to know who you are, and have confidence 
>> in you in order to commit to the project with you. 
>> For people to mentor you is a big commitment of time and energy. You need 
>> to demonstrate that will be well invested. 
>>
>> The way to do that is to get involved and show us who you are over the 
>> next few months. 
>> Help reproduce bugs, review patches, create patches etc. 
>> It doesn't take much before you're visible. (Really!) 
>>
>> The best way (also) to come up with project ideas is to see where there 
>> are issues already. 
>> (Much better than us providing a list.) So again, be involved. 
>>
>> If you start now, there's still lots of time, so I'm hoping. 
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>>
>>
>>
>> On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:
>>>
>>> It's a private wiki that only Django team members like Carlton can 
>>> access. It contains the information for Django to apply for GSoC.
>>>
>>> On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco wrote:

 Hi Tim,

 It returns 404 to me

 https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info

 Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham  
 ha scritto:

> All answers are at 
> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>


-- 
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/96816957-08b6-4896-9bcf-f138e1dc06bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-14 Thread Shashank shet
Hello Carlton sir,
I have worked on Django as a part of a project and wished to ask if the 
organization is still accepting proposals for GSoC 2019. 

On Monday, February 4, 2019 at 8:25:42 PM UTC+5:30, Carlton Gibson wrote:
>
> And thank you Tim, yes, exactly what I need. 
>
> To all: 
>
> I will put in the org application today. We'll then see about the 
> proposals. 
>
> The main thing is that we need to know who you are, and have confidence in 
> you in order to commit to the project with you. 
> For people to mentor you is a big commitment of time and energy. You need 
> to demonstrate that will be well invested. 
>
> The way to do that is to get involved and show us who you are over the 
> next few months. 
> Help reproduce bugs, review patches, create patches etc. 
> It doesn't take much before you're visible. (Really!) 
>
> The best way (also) to come up with project ideas is to see where there 
> are issues already. 
> (Much better than us providing a list.) So again, be involved. 
>
> If you start now, there's still lots of time, so I'm hoping. 
>
> Kind Regards,
>
> Carlton
>
>
>
>
>
> On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:
>>
>> It's a private wiki that only Django team members like Carlton can 
>> access. It contains the information for Django to apply for GSoC.
>>
>> On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco wrote:
>>>
>>> Hi Tim,
>>>
>>> It returns 404 to me
>>>
>>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>>
>>> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham  
>>> ha scritto:
>>>
 All answers are at 
 https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info

>>>

-- 
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/77cab753-bf3e-4d15-b47c-039c2be5423b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-04 Thread Carlton Gibson
And thank you Tim, yes, exactly what I need. 

To all: 

I will put in the org application today. We'll then see about the 
proposals. 

The main thing is that we need to know who you are, and have confidence in 
you in order to commit to the project with you. 
For people to mentor you is a big commitment of time and energy. You need 
to demonstrate that will be well invested. 

The way to do that is to get involved and show us who you are over the next 
few months. 
Help reproduce bugs, review patches, create patches etc. 
It doesn't take much before you're visible. (Really!) 

The best way (also) to come up with project ideas is to see where there are 
issues already. 
(Much better than us providing a list.) So again, be involved. 

If you start now, there's still lots of time, so I'm hoping. 

Kind Regards,

Carlton





On Monday, 4 February 2019 15:43:39 UTC+1, Tim Graham wrote:
>
> It's a private wiki that only Django team members like Carlton can access. 
> It contains the information for Django to apply for GSoC.
>
> On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco wrote:
>>
>> Hi Tim,
>>
>> It returns 404 to me
>>
>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>
>> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham  
>> ha scritto:
>>
>>> All answers are at 
>>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>>
>>

-- 
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/5e410c5e-deb7-4dfe-9f61-0599a1bf80e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-04 Thread Tim Graham
It's a private wiki that only Django team members like Carlton can access. 
It contains the information for Django to apply for GSoC.

On Monday, February 4, 2019 at 9:07:40 AM UTC-5, Giuseppe De Marco wrote:
>
> Hi Tim,
>
> It returns 404 to me
>
> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>
> Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham  > ha scritto:
>
>> All answers are at 
>> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>>
>

-- 
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/2e76e237-d0ce-4236-825c-33d58a0d145a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-04 Thread Giuseppe De Marco
Hi Tim,

It returns 404 to me
https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info

Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham 
ha scritto:

> All answers are at
> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info
>

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


Re: Google Summer of Code 2019

2019-02-04 Thread Tim Graham
All answers are at 
https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info

On Monday, February 4, 2019 at 4:19:06 AM UTC-5, Carlton Gibson wrote:
>
> Hey Tim. 
>
> > For each year your organization has participated, provide the counts of 
> successful and total students. (e.g. 2016: 3/4)
>
> I have no idea about this, could you advise? 
>
> 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/1d12a3c5-a7be-4df1-bc12-6fb7292d5517%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-04 Thread Carlton Gibson
Hey Tim. 

> For each year your organization has participated, provide the counts of 
successful and total students. (e.g. 2016: 3/4)

I have no idea about this, could you advise? 

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/e1bb1cc8-8628-435c-a5c6-8466ed4e8d4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-04 Thread Carlton Gibson
Hey Parth, 

Yes, you're right: 

> Students can register and submit their applications to mentor 
organizations. All proposals must be submitted by April 9, 2019 20:00 
(CEST).

There's time. I was thinking tomorrow was the full proposal deadline. 
(That's my lack of familiarity with it.) 

I will fill do the the Organisation application today. The programme seems 
a good opportunity. 

Kind Regards,

Carlton



On Monday, 4 February 2019 09:40:32 UTC+1, PARTH PATIL wrote:
>
>
>
> Hey, I am really enthusiastic for doing GSoC with Django, I had been 
> working for a few months to get myself familiar with the code base. I have 
> quite a few unpolished ideas in my mind for projects like the one posted 
> here 
> 
> .
>
> Though I'm unable to understand why Django is not ready to participate in 
> GSoC this year?
>
> Also, I would like to point out what *Carlton* said in his post 
> 
> .
>
>- I don't think it is justified to expect mind-blowing project 
>proposal this early. As per the GSoC's timeline, the application deadline 
>is April 9 which is like two months for now.
>- Even the discussions of ideas according to Google begins from 20 
>days from now.
>- There is also no ideas page for Django for 2019, to which students 
>can refer.
>- More importantly, as a student, I think many students will be 
>genuinely interested to take up a few good projects with Django.
>
>
>
> On Monday, February 4, 2019 at 2:41:11 AM UTC+5:30, Carlton Gibson wrote:
>>
>> Yes. GSoC wasn't at all on my radar before your post here Tim. 
>>
>> We've had a few "hello" posts but no even semi-concrete proposals from 
>> students. (Equally we don't have a list ready to go.) 
>>
>> I had a look at the process. It seems a moderate commitment, so, for me, 
>> I think I'd want to be familiar with applicants before we took that on. 
>> i.e. We need say to students to get involved months before. 
>> I'll think about messaging for that for next year because GSoC seems good 
>> overall. 
>>
>> SO unless someone is going to blow us away with an outline of a proposal 
>> TOMORROW, we'll have to pass this year. (Deadline being Tuesday.)
>>
>> On Friday, 1 February 2019 22:32:43 UTC+1, Tim Graham wrote:
>>>
>>> As of now, I haven't seen any existing Django contributors who are 
>>> planning to propose a project, therefore I don't think it's worthwhile for 
>>> the DSF to apply for this summer. The decision to apply on behalf of the 
>>> DSF is up to Carlton, Mariusz, or another potential mentor.
>>>
>>> On Thursday, January 31, 2019 at 6:24:36 AM UTC-5, gaurav jain wrote:

 One Idea i have a one command django project maker to instead having 
 1+n commands(n number of apps) and linking them in setting we can have 
 command take the number of apps and app_names in ine do and then later we 
 can add functionality for heroku ,docker etc

 On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:
>
> Org applications for Google's Summer of Code are now open (deadline 
> February 6). Do you think the Django Software Foundation should 
> participate?
>
> We haven't had any high quality student applications that we could 
> accept for the past two years.
>
> Perhaps it's partly a function of a poor ideas page (
> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we 
> don't do a great job of publicizing our involvement and attracting high 
> quality students. Perhaps it's because the student payment isn't all that 
> much (+/-$6000 USD, depending on student's country)* for the amount of 
> work 
> involved (also, students have to put in a lot of work up front in their 
> application, with no guarantee of being accepted into the program).
>
> If you have any ideas about mentoring or suggesting a project, or if 
> you're serious about being a student (you should start contributing to 
> Django now if you don't already), please share.
>
> * https://developers.google.com/open-source/gsoc/help/student-stipends
>


-- 
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/f8a1ff9d-c5d6-48b6-b181-20ee4b68bb5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-04 Thread PARTH PATIL



Hey, I am really enthusiastic for doing GSoC with Django, I had been 
working for a few months to get myself familiar with the code base. I have 
quite a few unpolished ideas in my mind for projects like the one posted 
here 

.

Though I'm unable to understand why Django is not ready to participate in 
GSoC this year?

Also, I would like to point out what *Carlton* said in his post 

.

   - I don't think it is justified to expect mind-blowing project proposal 
   this early. As per the GSoC's timeline, the application deadline is April 9 
   which is like two months for now.
   - Even the discussions of ideas according to Google begins from 20 days 
   from now.
   - There is also no ideas page for Django for 2019, to which students can 
   refer.
   - More importantly, as a student, I think many students will be 
   genuinely interested to take up a few good projects with Django.



On Monday, February 4, 2019 at 2:41:11 AM UTC+5:30, Carlton Gibson wrote:
>
> Yes. GSoC wasn't at all on my radar before your post here Tim. 
>
> We've had a few "hello" posts but no even semi-concrete proposals from 
> students. (Equally we don't have a list ready to go.) 
>
> I had a look at the process. It seems a moderate commitment, so, for me, I 
> think I'd want to be familiar with applicants before we took that on. i.e. 
> We need say to students to get involved months before. 
> I'll think about messaging for that for next year because GSoC seems good 
> overall. 
>
> SO unless someone is going to blow us away with an outline of a proposal 
> TOMORROW, we'll have to pass this year. (Deadline being Tuesday.)
>
> On Friday, 1 February 2019 22:32:43 UTC+1, Tim Graham wrote:
>>
>> As of now, I haven't seen any existing Django contributors who are 
>> planning to propose a project, therefore I don't think it's worthwhile for 
>> the DSF to apply for this summer. The decision to apply on behalf of the 
>> DSF is up to Carlton, Mariusz, or another potential mentor.
>>
>> On Thursday, January 31, 2019 at 6:24:36 AM UTC-5, gaurav jain wrote:
>>>
>>> One Idea i have a one command django project maker to instead having 1+n 
>>> commands(n number of apps) and linking them in setting we can have command 
>>> take the number of apps and app_names in ine do and then later we can add 
>>> functionality for heroku ,docker etc
>>>
>>> On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:

 Org applications for Google's Summer of Code are now open (deadline 
 February 6). Do you think the Django Software Foundation should 
 participate?

 We haven't had any high quality student applications that we could 
 accept for the past two years.

 Perhaps it's partly a function of a poor ideas page (
 https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we 
 don't do a great job of publicizing our involvement and attracting high 
 quality students. Perhaps it's because the student payment isn't all that 
 much (+/-$6000 USD, depending on student's country)* for the amount of 
 work 
 involved (also, students have to put in a lot of work up front in their 
 application, with no guarantee of being accepted into the program).

 If you have any ideas about mentoring or suggesting a project, or if 
 you're serious about being a student (you should start contributing to 
 Django now if you don't already), please share.

 * https://developers.google.com/open-source/gsoc/help/student-stipends

>>>

-- 
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/65c300ab-16b0-4a4f-8de7-3f86d1dd29d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-03 Thread Carlton Gibson
Yes. GSoC wasn't at all on my radar before your post here Tim. 

We've had a few "hello" posts but no even semi-concrete proposals from 
students. (Equally we don't have a list ready to go.) 

I had a look at the process. It seems a moderate commitment, so, for me, I 
think I'd want to be familiar with applicants before we took that on. i.e. 
We need say to students to get involved months before. 
I'll think about messaging for that for next year because GSoC seems good 
overall. 

SO unless someone is going to blow us away with an outline of a proposal 
TOMORROW, we'll have to pass this year. (Deadline being Tuesday.)

On Friday, 1 February 2019 22:32:43 UTC+1, Tim Graham wrote:
>
> As of now, I haven't seen any existing Django contributors who are 
> planning to propose a project, therefore I don't think it's worthwhile for 
> the DSF to apply for this summer. The decision to apply on behalf of the 
> DSF is up to Carlton, Mariusz, or another potential mentor.
>
> On Thursday, January 31, 2019 at 6:24:36 AM UTC-5, gaurav jain wrote:
>>
>> One Idea i have a one command django project maker to instead having 1+n 
>> commands(n number of apps) and linking them in setting we can have command 
>> take the number of apps and app_names in ine do and then later we can add 
>> functionality for heroku ,docker etc
>>
>> On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:
>>>
>>> Org applications for Google's Summer of Code are now open (deadline 
>>> February 6). Do you think the Django Software Foundation should participate?
>>>
>>> We haven't had any high quality student applications that we could 
>>> accept for the past two years.
>>>
>>> Perhaps it's partly a function of a poor ideas page (
>>> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't 
>>> do a great job of publicizing our involvement and attracting high quality 
>>> students. Perhaps it's because the student payment isn't all that much 
>>> (+/-$6000 USD, depending on student's country)* for the amount of work 
>>> involved (also, students have to put in a lot of work up front in their 
>>> application, with no guarantee of being accepted into the program).
>>>
>>> If you have any ideas about mentoring or suggesting a project, or if 
>>> you're serious about being a student (you should start contributing to 
>>> Django now if you don't already), please share.
>>>
>>> * https://developers.google.com/open-source/gsoc/help/student-stipends
>>>
>>

-- 
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/62853b9c-6201-4d13-b788-b807b5348d2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-02-01 Thread Tim Graham
As of now, I haven't seen any existing Django contributors who are planning 
to propose a project, therefore I don't think it's worthwhile for the DSF 
to apply for this summer. The decision to apply on behalf of the DSF is up 
to Carlton, Mariusz, or another potential mentor.

On Thursday, January 31, 2019 at 6:24:36 AM UTC-5, gaurav jain wrote:
>
> One Idea i have a one command django project maker to instead having 1+n 
> commands(n number of apps) and linking them in setting we can have command 
> take the number of apps and app_names in ine do and then later we can add 
> functionality for heroku ,docker etc
>
> On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:
>>
>> Org applications for Google's Summer of Code are now open (deadline 
>> February 6). Do you think the Django Software Foundation should participate?
>>
>> We haven't had any high quality student applications that we could accept 
>> for the past two years.
>>
>> Perhaps it's partly a function of a poor ideas page (
>> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't 
>> do a great job of publicizing our involvement and attracting high quality 
>> students. Perhaps it's because the student payment isn't all that much 
>> (+/-$6000 USD, depending on student's country)* for the amount of work 
>> involved (also, students have to put in a lot of work up front in their 
>> application, with no guarantee of being accepted into the program).
>>
>> If you have any ideas about mentoring or suggesting a project, or if 
>> you're serious about being a student (you should start contributing to 
>> Django now if you don't already), please share.
>>
>> * https://developers.google.com/open-source/gsoc/help/student-stipends
>>
>

-- 
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/b4e4848b-ba43-4161-93bc-1bdcb9f84c55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-31 Thread gaurav jain
One Idea i have a one command django project maker to instead having 1+n 
commands(n number of apps) and linking them in setting we can have command 
take the number of apps and app_names in ine do and then later we can add 
functionality for heroku ,docker etc

On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:
>
> Org applications for Google's Summer of Code are now open (deadline 
> February 6). Do you think the Django Software Foundation should participate?
>
> We haven't had any high quality student applications that we could accept 
> for the past two years.
>
> Perhaps it's partly a function of a poor ideas page (
> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't 
> do a great job of publicizing our involvement and attracting high quality 
> students. Perhaps it's because the student payment isn't all that much 
> (+/-$6000 USD, depending on student's country)* for the amount of work 
> involved (also, students have to put in a lot of work up front in their 
> application, with no guarantee of being accepted into the program).
>
> If you have any ideas about mentoring or suggesting a project, or if 
> you're serious about being a student (you should start contributing to 
> Django now if you don't already), please share.
>
> * https://developers.google.com/open-source/gsoc/help/student-stipends
>

-- 
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/636bd240-4422-4864-aa96-76d8836fdeab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-29 Thread shrikrishna singh
Thanks for the input Carlton and Adam. I will start working on the POC then.

On Tuesday, January 29, 2019 at 11:41:48 PM UTC+5:30, Adam Johnson wrote:
>
> Small point: a cross-DB JSONField could also serve as a cross-DB 
> ArrayField, since JSON can store arrays. I don't believe MySQL or SQLite 
> have "array" types, so to build a cross-DB ArrayField you'd emulate them 
> with JSON plus a restriction to just storing arrays, which comes back to 
> building a cross-DB JSONField.
>
> On Tue, 29 Jan 2019 at 17:51, Carlton Gibson  > wrote:
>
>> Hi Shrikrishna, 
>>
>> Not so much a ticket… See the thread I linked. There’s a lot of info 
>> there. 
>>
>> The first step (I think) is a proof-of-concept JSONField for SQLite — we 
>> have the other three DBs. 
>>
>> So taking a look at the implementation of the existing fields and 
>> SQLite’s API for the JSON extension, should lead you to be able to put 
>> together the first draft of some thoughts as to how we’d go forward. 
>>
>> Have a rummage in `contrib.postgres` (and the Oracle and MySQL examples). 
>> How do the equivalent lookups look in SQLite? (HasKey, ContainedBy, and so 
>> on.) Any blockers? 
>>
>> A rough breakdown here would be a good starting point. 
>>
>> From there, there are lots of people here who know a lot about this stuff 
>> (more that me). 
>>
>> I’m wondering about Florian’s point about scope. I don’t know much about 
>> GSoC, so I don’t know what they’d require. 
>> (The other wish-list item for me is a cross-DB ArrayField, but I haven’t 
>> even begun to look what the support is like there, if any at all.) 
>>
>> Kind Regards,
>>
>> Carlton
>>
>> -- 
>> 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/ADB006C1-4936-4949-83EC-4138176A27D0%40gmail.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/c8a97dda-deeb-4050-a334-60b605d24ea6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-29 Thread Adam Johnson
Small point: a cross-DB JSONField could also serve as a cross-DB
ArrayField, since JSON can store arrays. I don't believe MySQL or SQLite
have "array" types, so to build a cross-DB ArrayField you'd emulate them
with JSON plus a restriction to just storing arrays, which comes back to
building a cross-DB JSONField.

On Tue, 29 Jan 2019 at 17:51, Carlton Gibson 
wrote:

> Hi Shrikrishna,
>
> Not so much a ticket… See the thread I linked. There’s a lot of info
> there.
>
> The first step (I think) is a proof-of-concept JSONField for SQLite — we
> have the other three DBs.
>
> So taking a look at the implementation of the existing fields and SQLite’s
> API for the JSON extension, should lead you to be able to put together the
> first draft of some thoughts as to how we’d go forward.
>
> Have a rummage in `contrib.postgres` (and the Oracle and MySQL examples).
> How do the equivalent lookups look in SQLite? (HasKey, ContainedBy, and so
> on.) Any blockers?
>
> A rough breakdown here would be a good starting point.
>
> From there, there are lots of people here who know a lot about this stuff
> (more that me).
>
> I’m wondering about Florian’s point about scope. I don’t know much about
> GSoC, so I don’t know what they’d require.
> (The other wish-list item for me is a cross-DB ArrayField, but I haven’t
> even begun to look what the support is like there, if any at all.)
>
> Kind Regards,
>
> Carlton
>
> --
> 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/ADB006C1-4936-4949-83EC-4138176A27D0%40gmail.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/CAMyDDM3jD7Zsr2io8hv2AMez0QxNZcbEscfpCirH2o3K5vCxRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-29 Thread Carlton Gibson
Hi Shrikrishna, 

Not so much a ticket… See the thread I linked. There’s a lot of info there. 

The first step (I think) is a proof-of-concept JSONField for SQLite — we have 
the other three DBs. 

So taking a look at the implementation of the existing fields and SQLite’s API 
for the JSON extension, should lead you to be able to put together the first 
draft of some thoughts as to how we’d go forward. 

Have a rummage in `contrib.postgres` (and the Oracle and MySQL examples). How 
do the equivalent lookups look in SQLite? (HasKey, ContainedBy, and so on.) Any 
blockers? 

A rough breakdown here would be a good starting point. 

>From there, there are lots of people here who know a lot about this stuff 
>(more that me). 

I’m wondering about Florian’s point about scope. I don’t know much about GSoC, 
so I don’t know what they’d require. 
(The other wish-list item for me is a cross-DB ArrayField, but I haven’t even 
begun to look what the support is like there, if any at all.) 

Kind Regards,

Carlton

-- 
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/ADB006C1-4936-4949-83EC-4138176A27D0%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-29 Thread shrikrishna singh
Hello Carlton,

I am interested to do a GSoC project based on this idea and looking forward 
to researching on this topic and drafting a proposal.

In the mean, can you please suggest me any easy picking ticket(related to 
this idea) I should work on?

Thanks,
Shrikrishna

-- 
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/bb02e566-a5bd-4c6e-a5e9-2c38913414d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-29 Thread shrikrishna . s
Maybe, we could append this idea with the 'Improve less popular database 
backend idea' on the wiki 

 page 
as that project is also not that big for a GSoC project but the purpose of 
both projects seems quite similar to me. So I guess we could have a good 
GSoC project by combining both the idea?

On Friday, January 25, 2019 at 3:04:58 PM UTC+5:30, Florian Apolloner wrote:
>
> On Thursday, January 24, 2019 at 4:01:00 PM UTC+1, Adam Johnson wrote:
>>
>> I'd be happy to help mentor a cross-DB JSONField, it's something I'd like 
>> to see done so I can deprecate the one I maintain in Django-MySQL.
>>
>
> Not sure if GSOC changed that much, but it seems like somewhat small for a 
> GSOC project. 
>

-- 
*
**Crediwatch Information Analytics Private Limited*
*Bangalore Office:* 
#22, 13th Main, Jayanagar 4th Block, Bangalore - 560 011
*Mumbai Office:* 
#1902, 19th Floor, Tower B, Peninsula Business Park G K Marg, Lower Parel, 
Mumbai - 400013
*Confidentiality Notice*: The content of this email is 
confidential  and intended only for the Addressee. All other recipients are 
prohibited from disclosing , copying distributing or taking any action in 
reliance to the contents of this email.

*Please consider the environment 
before printing this e-mail.*

-- 
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/876319c9-2e39-449f-bd2d-2245a98b825a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-25 Thread Florian Apolloner
On Thursday, January 24, 2019 at 4:01:00 PM UTC+1, Adam Johnson wrote:
>
> I'd be happy to help mentor a cross-DB JSONField, it's something I'd like 
> to see done so I can deprecate the one I maintain in Django-MySQL.
>

Not sure if GSOC changed that much, but it seems like somewhat small for a 
GSOC project. 

-- 
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/a8156cf1-2c87-4963-add8-13429b44a8a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-25 Thread Josh Smeaton
Other ideas can be found in the DEPS repo 
too: https://github.com/django/deps/pulls

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5f9a5198-fd0d-470d-a6a9-81be3c8de87f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-24 Thread Adam Johnson
I'd be happy to help mentor a cross-DB JSONField, it's something I'd like
to see done so I can deprecate the one I maintain in Django-MySQL.

On Thu, 24 Jan 2019 at 14:43, Carlton Gibson 
wrote:

> Perhaps it's partly the GSoC doesn't cross the radar until just a few
> weeks before the deadline... 
>
> I'm happy to help mentor but also Django Core Mentorship is there...
> https://groups.google.com/forum/#!forum/django-core-mentorship
>
>
> One idea for a good project might be adding a cross DB JSONField as per
> this thread
>
>
> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>
> * All the supported DBs have native JSON support.
> * SQLite is the only one where we don't have a Django model field already
> to work on.
>* That would be first step as PoC I'd guess.
> * Then, how can we unify?
> * And, a migration path (from contrib.postgres)
>
> I don't know if that's perfect but it strikes me as eminently do-able.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/32637936-6241-43f6-bbbf-469f57d3d371%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/CAMyDDM345HrY0m71On3AgGOvvhEDPeXPPtLQk3rJyS4pWn79hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-24 Thread Carlton Gibson
Perhaps it's partly the GSoC doesn't cross the radar until just a few weeks 
before the deadline... 

I'm happy to help mentor but also Django Core Mentorship is there...
https://groups.google.com/forum/#!forum/django-core-mentorship


One idea for a good project might be adding a cross DB JSONField as per 
this thread

  
 https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion

* All the supported DBs have native JSON support. 
* SQLite is the only one where we don't have a Django model field already 
to work on. 
   * That would be first step as PoC I'd guess. 
* Then, how can we unify? 
* And, a migration path (from contrib.postgres) 

I don't know if that's perfect but it strikes me as eminently do-able. 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/32637936-6241-43f6-bbbf-469f57d3d371%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-19 Thread akki
Hi

One of the most difficult things for me while preparing my GSoC proposal 
was getting myself acquainted to Django's humungous code base.
To prepare a proposal one should know what modules they would need to 
modify & what part of the code they will need to work with. To do that one 
should *at least* know what is the role of a particular module/file in the 
big picture of Django's code. For me, even though I had drilled down that I 
had to work just with django/db, I still had the task of figuring out the 
working of *so* many modules. There were *models.options, models.sql.query, 
models.sql.compiler, migrations.autodetector, migrations.loader, 
migrations.optimizer*, *backends.features*, *backends.introspection*, 
*backends.operations*, *backends.schema* and many more which were somehow 
connected to each other & doing something but I had no easy way to know 
what.
I think putting an individual README to places like django/core/ 
, django/db/models 
/, etc. with 
even a 1-2 line description of what purpose each of the folder/file (or at 
least the convoluted ones) in that folder serve might be great help to 
newbie programmers - just not for GSoC but any new contributor.
I understand that the work required to make this happen might be quite big 
and complex (maybe big enough to make it a GSoC project in itself, but 
Google doesn't accept purely documentation projects for GSoC IIRC) but 
might be achievable if merged in parts.


@Parth I am Django's GSoC fellow for 2016. If there is any way I could help 
you, feel free to reach me out 
. For other 
fellows, you can search for Django in the archives of GSoC's website 
.
Also, a quick way to ask questions about contributing to Django from the 
community is the IRC channel #django-dev


On Wednesday, 16 January 2019 21:33:55 UTC+7, Tim Graham wrote:
>
> Org applications for Google's Summer of Code are now open (deadline 
> February 6). Do you think the Django Software Foundation should participate?
>
> We haven't had any high quality student applications that we could accept 
> for the past two years.
>
> Perhaps it's partly a function of a poor ideas page (
> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't 
> do a great job of publicizing our involvement and attracting high quality 
> students. Perhaps it's because the student payment isn't all that much 
> (+/-$6000 USD, depending on student's country)* for the amount of work 
> involved (also, students have to put in a lot of work up front in their 
> application, with no guarantee of being accepted into the program).
>
> If you have any ideas about mentoring or suggesting a project, or if 
> you're serious about being a student (you should start contributing to 
> Django now if you don't already), please share.
>
> * https://developers.google.com/open-source/gsoc/help/student-stipends
>

-- 
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/94246e44-0a18-492e-bae9-5c340c5734a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.