Re: Sounding out for GSoC 2020.

2019-12-10 Thread Carlton Gibson
Hey Andrew. Yes, Async, of course. It's not until *next July* so I'd still think we should list this. Worst case is there's exactly zero progress between now and decision day, in which case you could say that we could only accept a clearly capable candidate. (Jannis was once our GSoC person,

Re: Sounding out for GSoC 2020.

2019-12-10 Thread Andrew Godwin
I agree that 2FA could be a good choice - some of the async support work would also have been good, had I made more progress in the latter half of this year. A couple of other ideas for big projects: * A secrets manager abstraction and built-in support for Vault, KMS, and other common ones * A

Re: Sounding out for GSoC 2020.

2019-12-10 Thread Carlton Gibson
This thread was good on 2FA: linked to some prior art. https://groups.google.com/d/topic/django-developers/zzjTvgTbg5U/discussion (But was 3 years ago... ) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)"

Sounding out for GSoC 2020.

2019-12-10 Thread Carlton Gibson
Hi all. It's time to start thinking about Google Summer of Code (GSoC). If we're going to participate and projects we might propose. 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