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 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.)
Then it's projects. There are three that I have on my list that would
require a "competent candidate":
1. Work on the migrations. Markus mentioned a particular ticket here but...
2. Make the parallel test runner work on Windows. ("fork" vs "spawn")
And 3, and this is the big one:
3. Add 2FA to Django.
This has been raised a few times:
* https://groups.google.com/d/topic/django-developers/T-kBSvry6z0/discussion
*
https://groups.google.com/d/topic/django-developers/d92P2V0YrbI/discussion
* ... others...
If I'm honest, in 2020, it's the one "battery" I feel a little bit
embarrassed we haven't got a story for. Maybe it's not possible in a GSoC
type scope but...
— What would it look like? What can we leverage? Is it worth a go?
I'm looking at James, Florian, Joe, ... — who else has been keen here?
I'm also looking at the Technical Board, which I'm thinking has (will have)
a new guiding role to come up with suggestions for the direction of Django.
Other Projects: Are there other ideas? (Do you have one?) Are there easier
things that we could take "weaker" candidates for? But with that is there a
commitment for the mentoring help they'd need?
Anyhow, we have until January, so I'm just starting the discussion here.
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/af075d59-ece3-4044-9204-b690c746b9e0%40googlegroups.com.
