Hi Aaryan,
Happy New Year! Thanks for your interest, and your comment on my
presentation :)
I will write up the project ideas shortly, and try to give some guidance,
but I imaging the "secrets abstraction" idea wouldn't be too hard: look at,
say, Vault, and the AWS offering, what are the
Hi Carlton.
As I'm a Freshman in College, I'm totally new to the Open Source community.
I have been using Python for two years and recently, I learned the Django
Framework so I thought that it would be a great idea to contribute to it
during my summer break through GSoC.
I have read the
Hi Vineeth.
There are a few third-party options in the space already. (Some linked from
the thread I mentioned above. Others easily found via Google, "django
2fa".) I'd begin looking at those.
I will write up a proper page for GSoC with the ideas here over the holiday
period, but if you
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
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.
Thank you for the kind comments!
I see some very interesting ideas here. I haven't been able to come up with
a good idea, but I can give a hand as a mentor next year, so I thought I'd
join on this conversation :)
Andrew, I think the Django Case Studies will be a great idea for Season of
Docs
>
> 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
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.
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,
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
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)"
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
12 matches
Mail list logo
