Project status - Is this project maintained?

[johnthagen]

The last commit for this project is from over a year and a half ago and a PR for adding support for new versions of Python, DRF, and Django has not been commented on for months (#57).

We are trying to evaluate whether this project is a safe bet to use for a new project, or whether we should instead only consider a more maintained package, like django-guardian and django-rest-framework-guardian.

Is this project still maintained? If not, at a minimum the README should be updated to reflect this.

[dbinetti]

The question answers itself.

[auvipy]

I am going to vendor this project on my drf-exensions package.

[jberends]

no commits on @dbkaplan 's repo for over 2 years. time to take this up outside this repo. Is there a way to fork and ask PyPI for a new submission. I am willing to help here

[RignonNoel]

@johnthagen @auvipy @jberends

Hey everyone! Just to let you know that we took in charge a fork of this project and that we put it available on Pypi! :tada: :tada:

Our github repository -> https://github.com/FJNR-inc/dry-rest-permissions

Do not panic, even if the PyPi is now named django-dry-rest-permissions and that you will need to update your requirements the usage of the package is 100% compatible without change of code. :smiley:

Better than that you can now use it with Django 2.2 and Django 3.0 to be up-to-date!

Let us know in the Issues and PR of our fork if you have some requests, idea or contribution to merge! We will be happy to welcome anyone that want to help to make this package great again!

[johnthagen]

@RignonNoel Very cool. You should also consider opening a PR to change the reference in the DRF docs that point to this repo to your new project, since it will be maintained now.

[RignonNoel]

@johnthagen Excellent idea! Thanks for the tips, really appreciate.

I just did it: https://github.com/encode/django-rest-framework/pull/7374