django-oidc-provider
django-oidc-provider copied to clipboard
juanifioren
Project status?
Hello Given last commit was 2 years ago, is this project still being maintained? If not, what is the alternative?
I don't know how actively this project is maintained, but the presumption in the question is wrong. There are newer commits than two years on the develop branch, latest from Dec 2020 currently: https://github.com/juanifioren/django-oidc-provider/commits/develop
@juanifioren Would you care to share any update regarding the maintenance status of the project? There seems to be some good looking PRs in the queue, any plans to merge any of them and release a new version? (at least #361 seems trivial to review, but pretty important)
Does anyone want to volunteer as a maintainer? If we can identify a person then we can reach out to @juanifioren with a potential replacement. This is used by a number of folks and it would be nice to get upstream support. Alternatively are there any active forks that people use instead.
For me the number of DjangoWarnings is getting heavy - I'll gladly do a PR but we need someone to merge this stuff.
I believe maintaining this project is important. I noticed quite heavy feature/documentation changes on the various branches of https://github.com/catalyst/django-oidc-provider last year (like this large commit: https://github.com/catalyst/django-oidc-provider/commit/d1f32933dad792c9490544e4c8b8e5fe7493be07), but that has stopped for now.
There doesn't seem to be any one upstream where someone is keeping track of things and managing pulls/etc. @juanifioren has accepted a few here in the last year, but also ignored security fixes, so I think it is clear that things are not happening.
If @juanifioren will accept maintainers, I would be willing to put in some time long-term with administrative aspects of maintenance (adding some basic CI, providing input on issues & PRs, working on docs, etc), but I'm not an expert in security by any means, so things like approving PRs which affect core functionality should fall to someone more knowledgeable in that area.
Hello there, so nice to hear there's people interested on helping here. Who would like to be a contributor? I can give access to merge stuff and we can discuss on what to approve.
I'll be reviewing current PR's and try to merge some of them. So far we can start with:
- Review test pipeline and current version support for Py/Django.
- Go through all PR's and diff bugs/features/must have.
I agree with your priority list. Looking at this there is some #385 seems like the first good step.
~~Hi @juanifioren. How would you feel about handing this project over to the jazzband for future maintenance by the community?~~
This was a drive-by comment and probably not massively helpful so I'll retract it.
As an aside for others coming here, I have noticed that jazzband/django-oauth-toolkit supports OpenID Connect from v1.5.0.
@juanifioren You can add me too! :) I have a few things that are already in develop that would be nice to get released..
Latest version v0.8.0 supporting Django 4 and Python 3.11. Please keep contributing guys.