Re: Sounding out for GSoC 2020.

[vineeth sagar]

Hi Carlton,

I don't know if this is appropriate here or not. I will be starting
Master's this spring 2020(Jan)


I love the idea of 2FA. For first iteration I have an idea. While creating
a user we can ask for a 6 digit pin and whenever someone tries to login we
can make them input this pin. I have seen this implemented by a few
companies like Zerodha, UPI in India, these have a big customer base as
well. We can move towards more complicated ones with this as a starting
point.

Moreover is there a reading list on what's expected of the 2FA, So I can
start drafting a proposal for this. I'll look at the rfc mentioned in the
thread for motivation and how it can be integrated to django. If there are
other latest sources it will be helpful.


Best,
Vineeth


On Thu, 19 Dec, 2019, 1:39 PM Asif Saif Uddin,  wrote:

> As a long term user of django, I would love to see the DB/ORM + HTTP
> related improvements more in django and the schema migration improvements
> as I use django mostly for ORM and API/CMS based projects.
>
> I like the proposals of Adams related to ORM and inclusion of
> django-cors-headers to core.
>
> Beside the Idea of supporting 2FA, I think django should think about
> providing oauth2 support out of the box based on oauthlib and
> django-oauth-toolkit :)
>
> Definitely there could be better packages :)
>
> Just my thoughts as an long term user of django framework.
>
> Thanks,
> Asif
>
> On Thursday, December 19, 2019 at 4:51:06 AM UTC+6, Adam Johnson wrote:
>>
>> This year was interesting. Sage in particular did well putting together a
>>> cross-db JSONField, but he was probably under-mentored,
>>> since Mariusz has spent quite a bit of time reworking the PR, and still
>>> has a bit to go, before we can pull it in, hopefully for 3.1
>>>
>>> So, one consideration we need to think about seriously is our capacity
>>> for mentoring. (This isn't just about the candidate's ability — Sage was
>>> able to implement all suggestions — we just didn't have as much capacity as
>>> we might have liked to think about the requirement implementation — and
>>> there were four of us actively giving some time each... — Anyhow, to think
>>> about.)
>>>
>>
>> I think your analysis is pretty accurate Carlton. Sage was a pretty
>> self-motivated candidate, writing some great blog posts about his code, and
>> we still didn't manage to merge his PR. Perhaps the project was larger than
>> we can reasonably expect?
>>
>> Nice work on the descriptions there Andrew.
>>
>> Django Service Hooks
>>>
>>
>> I think a key use case of this is background task processing. Nearly all
>> the Django integrated libraries need to remember to "connection.close()" /
>> "close_old_connections" at the end of requests. I've seen a couple in-house
>> ones that needed this.
>>
>> That said I can't think of much else to go inside the "service hook"?
>> There's not much else to "the end of a Django context" at the moment is
>> there?
>>
>> Evented Datastores
>>>
>>
>> I'm not sure if other databases have it but MariaDB recently implemented
>> "temporal tables" which are an SQL standard way of doing historical views
>> on data:  https://mariadb.com/kb/en/library/temporal-data-tables/
>>
>> Admittedly not quite the same as event sourcing but perhaps easier to
>> implement given it would be limited to the ORM layer.
>>
>> Django Benchmarking
>>>
>>
>> I love djangobench, and do wish it was maintained and expanded. Running
>> on CI would be amazing.
>>
>>
>> 2FA also sounds like a great idea.
>>
>> Other ideas:
>>
>>- Support MySQL/MariaDB storage engines. I think other databases tend
>>to support some table-level customizations to.
>>- Official CORS middleware/view decorator. I took over maintenance of
>>https://github.com/adamchainz/django-cors-headers and its design is a
>>bit pants.
>>
>>
>> On Sat, 14 Dec 2019 at 17:30, Andrew Godwin  wrote:
>>
>>> Here's my take on each of these, leaving out async as that'd be more
>>> dependent on where we were:
>>>
>>> Secrets Manager
>>> Many environments Django is deployed in use a separate secrets manager
>>> to store and provide secrets per environment - either as environment
>>> variables, files, or via a direct HTTP API. The project would be to design
>>> and add an abstraction interface over secrets managers that allows users to
>>> easily map to an external secret in a settings file. There's also room for
>>> giving Django a better, built-in per-environments settings option too,
>>> pulling from popular third-party patterns.
>>>
>>> Django Service Hooks
>>> Django has a lot tied to the HTTP lifecycle, and if you run it outside
>>> of this, you miss out on some key things - like database connections being
>>> closed properly, or logging, or some middleware. The project would be to
>>> design and implement a separate way of calling Django from a service
>>> framework - even if that framework was itself HTTP based (basically, don't
>>> rely on Django having to run through WSGI/ASGI)

Re: Google Summer of Code 2019

[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: GSoC Proposal

[vineeth sagar]

You need to be a student at a uni to be eligible for Gsoc. Hope you know
that as you say you're a Software developer.

On Mon, 18 Mar, 2019, 21:20 Marcio Bernardes, 
wrote:

> Hi! My name is Márcio, I am 22 years old from Brazil. I know this is the
> first time I am posting here, but I hope it's the first of many. So
> attached with this message there is a proposal for the GSoC. This is based
> on the suggestions one, any thoughts? Oh yeah, I am a software developer, I
> worked some time in Europe with Python/Django now I think it's time to help
> here too. :)
>
> --
> 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/a1bce525-e6f7-48be-a573-5a27b194ea49%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/CAMMZq8MU3yuKdECJ5N_EFbWTgiiZvF7emWwned-vcxUh6nM-Lg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.