Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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.

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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.

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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,

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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,

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Re: Google Summer of Code 2019

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

Google Summer of Code 2019

Hey Parth here. I am genuinely interested in doing a project with django as student in gsoc 2019. I have been working hard since past few months to get myself familiar with the famework. I had few project ideas in mind, but I'm confused about the intricacies and needed some help. Also i haven't

Google Summer of Code 2019

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